Remote Desktop Port Forwarding

Discussion in 'Cisco/Linksys Wireless Routers' started by bchard, Apr 8, 2005.

  1. bchard

    bchard Network Guru Member

    I have a very simple network set up on a WRT54G w/ Firmware Version: v3.03.6. First, there is a static IP from the ISP. Then I have 3 PC's on the LAN with static IP's. I'm trying to connect to the 3 different computers via Remote Desktop. I should qualify this by saying I'm a Sys Admin and I thought I would have no problem w/ this. I have troubleshot this thing to death, so I'm sure I have it set up right but I am at a loss. I even scanned for open ports and found only 2; 3389 and 8080.

    The computer to which I'm forwarding 3389 works fine. I then tried forwarding 3390 and 3391; changed their ports in the registry as MS says to. It doesn't work but I don't think the port forwarding is the issue b/c I then tried to ping from the router to the workstations. No luck. I asked my client, who was onsite, to ping from the workstations to the router and then also to each other. No problem. They also all have access to the internet. Everything seems to be working except the router cannot see the 2 additional workstations. I assume the ports won't appear to be open because the router cannot see the IP's to which it needs to forward.

    Any ideas why I might be having this problem?
  2. willgill

    willgill Network Guru Member

    Sorry this won't really answer your post. It sounds like you're trying to do remote repair. I've found Remote Desktop a bear to work with for that.

    I suggest using UltraVNC SC. It stands for Ultra Virtual Network Computing Single Click.

    What you do is create a preconfigured mini server (168k in size) that's an .exe the client downloads and runs (doesn't install). The .exe is preconfigured to "call you" where you take remote control.

    The .exe plows through firewalls, NATs and they don't have to know their IP. If they can double click, you can take control.

    Now on your side you have to do the usual of forwarding port 5900 and have a static or a full qualified domain name setup, like through
  3. Guyfromhe

    Guyfromhe Network Guru Member

    almost sounds like a firewall (on the PC) issue to me if you can't ping the system from the router...
  4. bchard

    bchard Network Guru Member firewall. To my defense, I've been overseas for a year!:) I've forgotten the simple stuff like firewalls. Turned off the firewalls and the port forwarding is working.

    BTW, love the idea of the VNC software. Will check that out for my company.
  5. Guyfromhe

    Guyfromhe Network Guru Member

    I used ultravnc to manage my home network, works great...
    I was pretty sure it was a software firewall from what you described glad that fixed it.
  6. cromrell

    cromrell Network Guru Member

    I am also netadmin for small/mid company.

    For remote I am using Terminal Server (server 2000) and PCAnywhere v11.
    Both are working fine through my WRT54G using port forwarding.

    Terminal Server works great for connecting to servers (mod ports), but I use PCAnywhere to access my machine directly. PCAnywhere is a little anoying (latency, multiple PCAnywhere hosts) esp since they did away with the gateway in v9...

    Should I consider Remote Desktop?

  7. bchard

    bchard Network Guru Member

    We use Remote Desktop and PC Anywhere currently. RD is annoying because it locks the screen of the PC you're in. You can't have users duplicate the error for you. We're switching to VNC soon because of cost, although I've had problems with that in the past. PC Anywhere was always the best choice.

    Many of our problems are related to Terminal Server, so that's the only way we can see what the user is doing. We connect to their TS session and watch them.
  8. Guyfromhe

    Guyfromhe Network Guru Member

    i've never had trouble with VNC and I use it quite a bit...ultravnc seems to be the best release so far, and it doesn't lock the screen/kbd/mouse (unless you want it to)..
  9. cromrell

    cromrell Network Guru Member

    I am using Terminal Server & PC Anywhere for remote administration & remote access (I just bought a WRV54G VPN router to test as well).

    We are using VNC for remote assistance/troubleshooting, and for general QA for our call center agents.

  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