RDC over VPN problem

[Spyderturbo007]

I attempted to set up a VPN from work to home using Windows XP. The router is a DLink DI-624 that supports VPN passthrough, so I'm using XP as the endpoint (PPTP). I am able to connect to the VPN, browse files on the endpoint side, but I'm unable to initiate a RDC session. I noticed a couple things that could be the problem.

First, my PC at home (VPN Server) has a local IP address of 192.168.0.145, but when I connect with my work PC (Client), I see that the VPN server address is listed as 192.168.0.180. I've tried both IP addresses and neither work with the RDC. Additionally, I am using the same login information for both connections. Is that causing the problem? But I would think that if you can't use the same username/password combination, that the PC would connect but I would get an error about invalid credentials.

I attempted to Telnet to port 3389 using "telnet 192.168.0.180:3389" and "telnet 192.168.0.145:3389" and it keeps coming back saying that no connection can be established. I verified that RDC is enabled on the VPN server, so I can't figure out what is blocking the connection. I don't think it would be the router, since it's just set as a passthrough. Any thoughts?

Thank for your time!!!!

[guest]

The command should be telnet 192.168.0.180 3389 (no . Please post back with the result.

[Spyderturbo007]

I changed the command to "telnet 192.168.0.180 3389", without the quotes and got this as a response:

Connecting to 192.168.0.180...Could not open connection to the host, on port 3389: Connect failed.

Thanks for your help.

[guest]

Can you ping 192.168.0.180?

[Spyderturbo007]

Yes I can. I can also browse the shared files on the drive by using the \\192.168.0.180 switch in windows explorer. Copy and paste from one PC to the other works just fine. I was even streaming some music with no problems.

[guest]

Have you enabled RDC on remote computer? Also posting the result of netstat -a on the remote command may help.

[Spyderturbo007]

I had enable RDC on the remote computer, but I think I'm an idiot.

It looks like even though I enabled RDC, the netstat -a command didn't list Port 3389 as "Listening". I double checked and the windows firewall didn't list RDC as an exception. I guess I assumed that when you enabled RDC, the firewall would automatically add it as an exception. Oops!

After setting up an exception, netstat lists Port 3389 as listening. I think my problem might be solved, but I won't know until tomorrow when I get back to work. I'll let you know if it worked.

Sorry for wasting your time with this, as I'm sure you have better things to do.

[Spyderturbo007]

Alright, everything works now. Thanks for all your help. Turns out I was an idiot in the end.