VPN Problem

[Bigtimbre]

I recently had to upgrade to ME on my home computer. the problem I am running into now is this:

I have a VPN connection back to work. I am using the built in VPN client for ME. By default it uses strong encryption, where I believe this is causing me a problem is with Windows Terminal Server and VNC. I can connect to everything fine, but after the initial connection it times out before I even get to a password prompt (With VNC I'm able to put in the session password, it times out before displaying the desktop). I have hear rumors that these two things don't work well with 128 bit encryption, they want 40. I cannot, however, find anyway to turn down the encryption level on ME's client. Any suggestions?

[imaeditedbysowulo]

I'm a little confused on exactly what you're trying to do. Are you just trying to VNC from your ME computer to the server, or are you connecting to the server via your VPN connection and then running a VNC session from the server to another remote computer? Or are you trying to do both at the same time?

I've had trouble connecting to VNC when it was running on ME, but I've never had a problem connecting from ME to another computer using VNC.

[Bigtimbre]

I have a VPN connection that connects me to my network at work. I am then attempting to use VNC from my ME computer at home, to connect to my computer at work. So in otherwords I am trying to use VNC over the VPN. I have also tried it with Windows Terminal Server and I get the same results.

Thinking that it may be a firewall issue on my home network, I moved my ME computer outside the firewall and made the VNC connection, with the same results. It just seems to time out.


I'm not sure if I can fit any more acronyms in there ;)

[imaeditedbysowulo]

As long as the server has a real IP address, you shouldn't need to establish the VPN in order for VNC to connect. I guess that's the part that was confusing me.

VNC utilizes the internet, so connecting to your VPN isn't even necessary for VNC to work. As long as your ME computer has an internet connection, and the server has a real IP address, you should be good to go.

Since you've already tried moving your ME computer outside your home firewall, the only thing it could be is your firewall at the server's location.

Check the VNC homepage for ports that need to be opened on the firewall, I know 5900 needs to be open, but there might be a couple others as well.


How's the weather up there?

[Bigtimbre]

It's been hot. Hovering around the 80's, which is highly unusual....

The VPN connection is established directly to the firewall at work. One of the other guys on my team is set up the same way. The only difference is the OS, he runs 2000 I believe. Thats why I think it may be something in the VPN client.

Like I said though I have also tried reachingour Terminal Servers using the TS client and get much the same result. So I don't think it's a port problem....

I'm going to bring home a laptop with 2000 on it and see if it makes a difference.

[Bigtimbre]

When I tried it with the 2000 machine everything worked fine. It turns out there is something in the implementation of IPSec in the ME/98 VPN client that is messed up, at least for connecting to Watchguard products. Once I switched to the MUVPN client from Watchguard everything started working fine.


Thanks for the help.

[The Computer Valet]

My wife used to VPN to her office via Win98. She also used a third-party VPN product. (Cisco, in this case.) Plus this was to connect Netmeeting, not VNC.

I wonder if your original setup would have worked with Netmeeting...?

m