VPN versus Remote Desktop Connection

There is a lot of things happening here, i'm just thinking (if you haven't already done it) might be best if you ask your work network Admin to help you with this. Things might be alot more simplier than you think.

In hindsight, I got derailed from the simple solution when I was told that I needed to use Shrew Soft to VPN into the office. Now, I'm not so sure I ever understood. Why would Shrew Soft be necessary, if Windows 7 Professional (64-bit) already has a wizard for making a VPN connection? I was led to believe that the Windows 7 wizard was not compatible with the 64-bit OS. True? It seems kind of crazy.

I've searched to the end of the Internet to find a big-picture explanation of the relationship between RDC, VPN, and VPN client software. I would appreciate the version of the answer that is about 50 words or less.

it all depends on what type of vpn is being allowed, windows can do a PPTP vpn connection with its own built-in client, anything else requires another software client.

RDP- its just the connection protocal that allows you to remote into the machine, it doesnt care where that machine is as long as it can talk to it on the proper port (default 3389).

vpn- its a "virtual" connection that places you on the network your connecting to (as if you plugged in a network cable at that site).



Don't open up port 3389 to the world by forwarding it through your firewall/router, its not a good idea. You need to test the vpn connection (tunnel) to see if its actually comming up. Do this by opening the vpn client and connecting, then try to ping any device INSIDE the network you are vpn'd into (eg. a printer or another pc). IF you can ping them, then try to ping your machine by ip address that you want to rdp into. If that works, then try to connect with RDP by ip address. If that works then you just need to edit your "hosts" file on your machine at home so you can type in the name and it knows what ip to try. (vpn's usually have issues with dns). Let me know if that makes it clearer.

aem said:

There is a lot of things happening here, i'm just thinking (if you haven't already done it) might be best if you ask your work network Admin to help you with this. Things might be alot more simplier than you think.

Not a bad idea. If he was told he needs Shrewsoft one would hope the proper configuration would be documented somewhere. But what I found is he looks to be in control of the router config which leads me to think he's doing it on his own, or his Network Admin may not be familiar with mixing VPN products. I've endured considerable pain trying to get a VPN client from one vendor to talk to a server from another.

I've actually worked with the Shrewsoft free client a bit and it's not bad. A little slow but once you get it configured it seems to work ok. I have it running to a Procurve 7102 router at a remote site where I do RDP to a server.

You big dogs are going to love this one: I solved the problem. I scrapped everything and started over. I discovered my mistake as I went back over the steps. I had not put a password requirement on my account on my home computer. I don't have any kids, so I don't need a password, and I don't like using a password at home because I don't want my wife to feel like I'm hiding things from her. I was able to set up a VPN connection using the Windows 7 client; I never needed Shrew. RDC works perfectly.

Thanks to everyone who helped. It was an all-world effort (Australia, Kenya, England, Michigan, Illinois, etc.). I'm glad I could add to your list of boneheaded ways to mess up VPN and RDC.

Good to hear and thanks for letting us know.

Throughout my years in IT, 9.5/10 times it was mostly the simple things that people missed that got them into a mess. These simple things can even get the experts (IT instructors etc) buffled. They say if you need to do that and this things, and more that and this, then you are doing something wrong. This has proven correct time after time.

Glad to hear you got it going. It's amazing how many times just scrapping and starting over works. Like aem said, it's the little things.