hi, When i type 192.168.1.xxx into remote desktop from within my network evey thing works fine. (replacing the xxx with individual sytem #) Now if i go to myip.com my ip is the same on all pcs in the network. (I am guessing this is the router's ip?) So how can i access my pc from another computer outside my routers home network? 192.168.1.xxx will only give me other systems in the network i am curently in. If i type the ip address of the router in...I get an error measage.. How should i set it up so i an access one of the pcs on my network from elseware. I dont need to be able to choose..I just want to set it up for one of the pcs. I hurd somthing about port foward ing or somthing, but i dont know enoguh about it. thanks, cody

kerodude3058, are you talking about the built-in Windows remote desktop? If so, disregard the URL Jordan posted. You will have to forward a port on your router, but not the ones listed on that website. How you setup port forwarding depends on which router you have. It will most likely be covered in the manual, and should be called something like "virtual servers" or "port forwarding". Once you've read the relevant section of your manual, forward port 3389 to the IP address of the computer on your local network that you want to connect to from outside the network. Then you will be able to that internal computer using the router's external IP address.

hi, I found out how to foward ports, just a few questions. What protacall do i use? Tcp or udp? Also, to remotly conect what ip address do i use? the one on myip.com? Or id there another ip someware? Thanks, Cody

Use TCP, not UDP. myip.com seems to be a placeholder/spam website. Don't use it to determine your IP address. Instead, you can get the correct IP address from your router configuration. It will probably be referred to as the "internet" or "WAN" address. Or, if you must use a website, use www.whatismyip.com. Either of these options will show you the IP address you will connect to from outside your network.

the ip adress is the same...if i type that into remote desktop, it gives an error saying remote computer can not be conected at this time. Do I need to do anything with my windows fire wall to get it to work? do i need to type the 3389 anyware in the remote conect box? Thanks, cody

You may have to enable the forwarding on both TCP and UDP. I forget offhand which brand it is but I've run into at least one highspeed internet router that required both protocols being forwarded in order to get the remote access working properly. When connecting remotely, you have to connect to the external IP address of the router. If you have a static highspeed address you won't need to bother getting it more than once. To get it, connect to the router configuration (while you're on the LAN) and look in there....it will tell you what it is. Write it down (or just memorize it) and use it to connect remotely. If you get your IP address from your ISP via DHCP this is going to be a little tougher to deal with as it can change (it doesn't always depending on your provider).

kerodude3058: if i type that into remote desktop, it gives an error saying remote computer can not be conected at this time Are you doing this from outside your network? Inside your network, you will still need to use the IP address of the computer you are actually connecting to, rather than the router's address. "Do I need to do anything with my windows fire wall to get it to work" If you're using the built-in XP firewall, then no. If you're using a third party firewall, then probably yes. do i need to type the 3389 anyware in the remote conect box?" no, just the address CurtR: "You may have to enable the forwarding on both TCP and UDP" Not for RDP you don't. "When connecting remotely, you have to connect to the external IP address of the router." Alread covered. Twice. I know you're just highlighting the key information, but give the poster some credit for being able to read and follow simple instructions. You really do have a low opinion of people who ask questions here, don't you? "To get it, connect to the router configuration (while you're on the LAN) and look in there....it will tell you what it is." Already covered. I also told him what to actually look for. Thanks for reiterating though. "If you get your IP address from your ISP via DHCP this is going to be a little tougher to deal with as it can change" Some newer routers have built-in "dynamic dns" clients, which can help with this problem. How long ago was that 10 years of "industry experience" of yours, Curt?