D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: DNR on August 11, 2010, 05:55:48 AM
-
In my old router(DLink DI-614+), I have two virtual servers setup
port 80 -> forward to port 80 on pc1
port 90 -> forward to port 80 on pc1
worked great, but if I try the same setup in my DIR-655, I get an error since I have two rules ending in the same port/pc. Is there a more proper way to set this up?
-
Not sure as I don't use any Virtual Servers ,but have you tried one rule with "80,90" in the Public Port section?
-
it appears it only allows 1 port per definition, since is says [Port] unlike port forwarding which says [Ports].
-
Simple. Just configure one of the servers to run on port 90, the other on port 80. Why set them both to 80 internally, while you already use different outside ports...
-
Ok apparently i am missing something, there is only one server.... So if you hit the router via port 80 or 90 it goes to the same server but on 80.
port 80 -> forward to port 80 on pc1
port 90 -> forward to port 80 on pc1
-
Why would you have a setup like this ???
-
::) Because where I work(a hosting company) restricts ports >:( . There is no way for me to rdp into my server using 3389 because it is blocked... So i use one of the other ports they allow to rdp into my server, but I would also like to be able to hit the normal rdp port when I am rdping from elsewhere...
so from work rdp to mysite:1234 -> router magically forwards to myserver:3389
When i rdp to mysite(no port windows default is 3389) -> router magically forwards to myserver:3389
My old router let me do this without issue, the new router won't....
-
Try combining virtual server and portforwarding. Perhaps they allow overlap, both mechanisms are virtually the same.
-
why do you forward port 80 to port 80? what happens if you don't?