![]() |
IOBit Software
|
|
|
||||||
| Software Software such as operating systems like Windows XP, Windows Vista, Windows 7 etc., or specific programs. |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Hello,
I have a home network and am trying to connect to a pc at work which is also on a network. Both computers are running windows XP prof. I have followed the instructions for remote desktop conncection at http://www.microsoft.com/windowsxp/u...moteintro.mspx (Not a great article, I believe, since it doesn't even mention the router issue...) I have a static IP on the PC at work and have configured both routers for remote desktop. It just don't work. K |
| Sponsored links |
|
|
|
#2
|
||||
|
||||
|
what about firewalls? Did you open port 3389 on both ends?
Are you sure you did the port forwarding corectly on the work machine? |
|
#3
|
|||
|
|||
|
Hi,
Yes I did open port 3389 on both machines. I'm not sure what I could have done wrong on the work machine... what details should I check? k |
|
#4
|
||||
|
||||
|
Make certain that 3389 is pointing to the correct machine in the router--just opening it isnt sufficient. Thats usually the cause, firewalls aside.
|
|
#5
|
|||
|
|||
|
now you've lost me. What do you mean be pointing to the correct machine. Pls excuse my ignorance...
K |
| Sponsored links |
|
|
|
#6
|
||||
|
||||
|
Well, you have machines behind a router. Traffic gets distributed to the correct machine when requested by a machine behind the router.
For example. If a machine requests a website by browsing to it--the data packets will come back to that machine. HOWEVER Incoming traffic from the outside must have a direct path. So, if you try to connect to port 3389 (Remote Desktop/Terminal Services), it floats around in limbo, not knowing what machine to go to because the machine that you are trying to connect to did not request it. So, you have to use something called Port Forwarding. What this does is open up port 3389, and direct it to a specific place. So, when you try to connect to your work machine--your request hits the router, the router sees it and thinks "ah, this goes over to machine x". This prevents the request floating around in router limbo. That is extremely over simplified, but does that answer your question? |
|
#7
|
||||
|
||||
|
Port forwarding is pretty standard--select the port 3389 (UDP and TCP), and direct it to the IP address of the work machine to be connected to.
|
|
#8
|
|||
|
|||
|
The IP address you are referring to here is not the static IP that was assigned by my ISP?
K |
|
#9
|
|||
|
|||
|
Thank you so much for your help. That worked!
![]() ![]() |
|
#10
|
|||
|
|||
|
One more question...I this setup sufficiently secure?? Is there anything else that I should do to improve security?
K |
| Sponsored links |
|
|
|
#11
|
||||
|
||||
|
Just close it down when not in use. Its relatively secure, but the port is open for others too--if they know how to find it. It will only be a problem if they can get through the password protection on the work machine.
As long as you practice safe computing-- good antivirus, strong passwords, you should be fine. Of course, there are no absolutes on the internet. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Remote Desktop - Unable to connect from LAN to WAN | Squeaner | Networking | 5 | 01-01-07 19:46 |
| Remote Connect | trp | Software | 4 | 05-10-06 19:47 |
| Remote Control(remote desktop) via USB cable ? | Jbullock | Networking | 1 | 03-04-06 15:53 |
| Remote connect | trp | Networking | 2 | 11-11-04 21:18 |
| Remote Desktop | Shizoku | Software | 31 | 09-22-04 14:10 |