Networks Remote Desktop - Wireless Router - Config

Discussion in 'Hardware' started by wtw1ster, 11 Nov 2006.

  1. wtw1ster

    wtw1ster What's a Dremel?

    Joined:
    11 Nov 2006
    Posts:
    7
    Likes Received:
    0
    I am doing a job for a friend, but have never set up Remote Desktop this way. My friend has DSL that is connected to a ZyXEL wireless router. I need to set up remote desktop on one of the wireless computers (host) that is running Win XP Pro. The computer has a third party firewall installed (PC-cillin) and also has MAC filtering enabled on his wi-fi router.
    I have set a static IP on the host and that is about it. We also have the static IP of the WAN from the ISP.
    1) What ports do I need to forward? 2) When he goes to connect from a remote location, does he need to enter in the static IP I assigned the host, or the IP that the ISP gave him? Also, if there is anything else you can help me with that I did not bring up, please do. Thank you all for the help!
     
    Last edited: 11 Nov 2006
  2. CaseyBlackburn

    CaseyBlackburn Network Techie

    Joined:
    27 Jul 2004
    Posts:
    1,846
    Likes Received:
    0
    1) Follow the guide here to forward the ports: Portforward.com

    2) He will connect by typing in the static IP his ISP gave him.
     
  3. BKONComps

    BKONComps What's a Dremel?

    Joined:
    13 Nov 2006
    Posts:
    6
    Likes Received:
    0
    As long as you forward ports 3389 UDP and TCP, you should be ok. the personal firewall shouldn't have any issues, since the request is technically coming from the router. Also the MAC filtering will only affect computers trying to use the router as an access point, it won't affect the WAN/LAN interface (the NAT will do that).
     
  4. Glider

    Glider /dev/null

    Joined:
    2 Aug 2005
    Posts:
    4,173
    Likes Received:
    21
    But have in mind, Remote Desktop uses plain text connections...

    But you do have to set up the PC to allow incoming connections
     
  5. wtw1ster

    wtw1ster What's a Dremel?

    Joined:
    11 Nov 2006
    Posts:
    7
    Likes Received:
    0
    Updated info:
    He has Win XP Pro SP2 fully updated. I have already installed all the "Internet Information Services" and have allowed "Remote Desktop." It is connected to a DLS line through a ZyXEL wireless b router. I set him up with a static IP (192.168.1.33) and his WAN IP is 216.67.60.126. I forwarded TCP/UDP port 3389 to his machine (host) and also port TCP/UDP port 80 (for IIS) to the host.
    When I open a browser and type "http://192.168.1.33:80/tsweb" from a Win XP Home computer on the wireless network it times out. It will not connect from my house either. I have also tried "http://192.168.1.33:3389/tsweb" & "http://216.67.60.126:80/tsweb" & "http://216.67.60.126:3389/tsweb." When I went to add users allowed to connect to this computer remotely it said he was already accepted by default. Any ideas?
     
  6. Krikkit

    Krikkit All glory to the hypnotoad! Super Moderator

    Joined:
    21 Jan 2003
    Posts:
    23,613
    Likes Received:
    452
    If you're outside his LAN then you need to use your friend's static WAN address.
     
  7. CaseyBlackburn

    CaseyBlackburn Network Techie

    Joined:
    27 Jul 2004
    Posts:
    1,846
    Likes Received:
    0
    Have you enabled the Terminal Service web interface?
     
  8. kenco_uk

    kenco_uk I unsuccessfully then tried again

    Joined:
    28 Nov 2003
    Posts:
    9,696
    Likes Received:
    308
    Just to throw something else in..

    I tried setting up remote desktop on two XP Home PC's. One connects through a usb modem (client) and the other sits behind a Voyager 2110 router (server). I opened both ports, but am still unsure of what ip to forward the port to - would it be wan or lan? Both are fixed numbers.

    To make it easier (or harder :) ) I got the client connected succesfully to the server via vpn - it connects no problems.. but I can't see the computer at the other end, nothing comes up in the workgroup. I followed portforwarding's guides for both vpn and remote desktop to almost no avail.

    Like the op, I'm stuck! Apologies for the hijack, but if a solution comes along I'd give it a go.

    Sorry for the newbness, I understand a little about terminal services, but what's the benefit of the TS web interface? And would it apply to this situation or is it something the op needs to check?
     
  9. wtw1ster

    wtw1ster What's a Dremel?

    Joined:
    11 Nov 2006
    Posts:
    7
    Likes Received:
    0
    Ok I can remotely control his computer from the LAN, but when I try to connect from a remote location I keep getting this error message. "The connection to the remote computer was broken. This may have been caused by a network error. Please try connecting to the remote computer again." The remote desktop window appears, but the background is blank.
    I talked with his ISP and they said that we were connected and that our current DSL connection had an upload that would easily support remote desktop. I contacted the router manufacturer "ZyXEL" and they said that I had the router configured correctly. I also tried disabling windows firewall and the PC-cillin antivirus, but to no avail.
    I am soooo lost and I really don't want to look like a noob. Any more ideas?
    This is what it looks like. <http://img221.imageshack.us/my.php?image=windowrn3.png>
     
    Last edited: 18 Nov 2006
  10. CaseyBlackburn

    CaseyBlackburn Network Techie

    Joined:
    27 Jul 2004
    Posts:
    1,846
    Likes Received:
    0
    Have you tried connecting from a pc that isn't running Windows Xp Home, because Home does not cooperate with Remote Desktop all that well. This is the only thing I can think of, all other suggestions have been covered.
     
  11. wtw1ster

    wtw1ster What's a Dremel?

    Joined:
    11 Nov 2006
    Posts:
    7
    Likes Received:
    0
    Yep...I tried Win XP Pro too.
     
  12. Glider

    Glider /dev/null

    Joined:
    2 Aug 2005
    Posts:
    4,173
    Likes Received:
    21
    Just check every thing in the chain... Check (locally) if a RMD can occur to the pc (from an other pc), check in the router that the correct ports are forwarded to the correct IP. Check that you public IP is correct (maybe use a dynDNS servicen like no-ip.com or dynDNS).
     
Tags:

Share This Page