Issues with Remote Desktop

whosey

Junior Member
Jul 15, 2006
6
0
0

I recently setup a home network and have been trying to access it from work. I have a DLink DI-634M router, which setup was quite easy. After the initial setup I went into the options and forwarded port 3389 for Remote Desktop. I also allowed Remote connection in XP and allowed the service in my network connections. Both the XP firewall and the router firewall are disabled.

I have been extremely unsuccessful connecting to it from work. I think the issue maybe with the IP address, but I have tried everyone I have been given. I tried looking into ipconfig to get the IP assigned by my ISP and the only IP it displays is the one assigned to it by the router, in this case 192.168.0.109. When I pull up the router management I get the router, default gateway, and primary DNS IP's. Again the only IP it displays for my system is the one assigned to it by the router.

I have tried everything I can think of other than switching my connection directly to the modem. Any suggestions?
 

RebateMonger

Elite Member
Dec 24, 2005
11,586
0
0
Among others, you can use http://GRC.COM 's Shields Up service to tell you your IP address and to test whether Port 3389 is open on your router.

Use this IP address from the remote computer to access your router.
Then, make sure that TCP Port 3389 is forwarded to the IP address of your PC that you want to remotely access.

I suggest using a Static IP address on your home PC (something like 192.168.0.10). That way, it can never change. This is one situation where I recommend using a Static IP address on a client PC.
 

cleverhandle

Diamond Member
Dec 17, 2001
3,566
3
81
Originally posted by: whosey
When I pull up the router management I get the router, default gateway, and primary DNS IP's. Again the only IP it displays for my system is the one assigned to it by the router.
The external IP is probably in there somewhere. Usually you can see it under "system status" or something similar. But in any event, you can find your external IP by pointing your desktop's web browser to WhatsMyIP.

 

whosey

Junior Member
Jul 15, 2006
6
0
0
Thanks a lot RebateMonger and cleverhandle I will be sure to do just that as soon as I get off work. I appreciate the help.
 

Cloud Strife

Banned
Aug 12, 2006
475
0
0
Your work network could possibly be blocking outbound port 3389. In that case, there's nothing you can do about it. Port scan 3389 like RebateMonger has suggested to see if that port is forwarded correctly. You should also try Remote Desktop in your local network to see if it's actually working.