Microsoft MN-700 v Linksys WRT54GS?

Discussion in 'Cisco/Linksys Wireless Routers' started by -Draino-, Apr 17, 2007.

  1. -Draino-

    -Draino- LI Guru Member

    Not sure if I am missing something here but with my MN-700 I was able to
    "TRULY" forward ports. It was called "Persistent Port Fowarding" and I could forward port XXXX to port 3389.

    This way when I did a Remote Desktop to my home machine the IP would look something like this: - NOT 3389.

    I really miss that feature and I can't seem to find a way to make that happen with my new Linksys. I tried the Port Trigger menu but no luck there, am I not seeing something?

  2. ifican

    ifican Network Guru Member

    Port trigger is a little different. All of the WRT series routers i have seen/used all have port forwarding, worst case scenario you load a 3rd party firmware but i believe in the original firmware its under application or gaming. I could be wrong as it has been awhile but it should be there.
  3. -Draino-

    -Draino- LI Guru Member

    Nope this router seems to ONLY forward a specific port to a specific computer, instead of forwarding a specific port to another port.
  4. SoonerAl

    SoonerAl LI Guru Member

    If the router will not do port redirection (or Persistent Port Forwarding in MN-700 parlance) then an option may be to use a Secure Shell (SSH) tunnel. You can use an alternate high number TCP port and forward that through the router to the SSH server PC, then access any PC via Remote Desktop.

    Here is one method using PuTTY (free) as the SSH client...

    You can reconfigure the SSH server to listen on an alternate port in the sshd_config file. Change the default Port 22 statement to the new port number, ie. Port 41526 for example, then forward that port through your router.

    If you want to use the Tunnelier SSH client (also free) see these pages for help. Tunnelier is nice since you can configure it to automatically connect to one PC via Remote Desktop when the SSH link is successfully connected. Others are addressed using the localhost:portNumber syntax.

    FWIW, Tunnelier is my SSH client of choice...

    In all cases I recommend using a private/public key pair, protected by a strong password, for authentication...

    Also, note that you need to restart the SSH server service anytime you make a change to the sshd_config file...

    As a last resort I presume you know you can change the Remote Desktop listening port in the hosts registry to a random high number port if your comfortable with that?


    Good luck...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice