Remote Desktop conflicts with VPN

Desktop management applications
Fault isolation
Incident response
Intrusion management
Microsoft Windows
Network applications management
Network management software
Network monitoring
Network protocols
Network security
Network testing
Performance management
Protocol analysis
Remote management
I am connecting using Remote Desktop from my Laptop PC (Windows 2000 Pro Sp4) to a Server (Windows 2000 Server Sp4) in our DMZ over our Corporate Network. I am then using a Network & Dialup Connection on the Remote Server to connect over VPN to our Customer Sites. However, this is currently unusable as when the VPN connects, the Remote Desktop loses its connection to the Server! After a while the VPN connection times out (due to inactivity?) and then the Remote Desktop can again be re-connected to the Server! Can anyone help me to resolve this conflict so that I can make use of the VPN connection to our Customer Sites?

Answer Wiki

Thanks. We'll let you know when a new response is added.

Sounds like your VPN system has split tunnelling disabled.

Split tunnelling is where only the VPN related traffic goes over the encrypted tunnel, all other traffic is allowed to use the normal network connection. Split tunnelling carries the risk that one could be connected to a “secure” network, and that some other Internet connection could go through the workstation and infect the “secured” systems.

You will probably have to talk with whomever manages your VPN setup.


Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Ramheka
    while conected to your work server go to your VPN properies under networking select TCP/IP properties then advance untick use default gateway on remote network that's all you need to do remember you need to do that before istablishing a VPN connection to your clients ( meaning in the disconnected mode)
    0 pointsBadges:
  • HenryKafeman
    Sorry I thought I got the Split Tunneling link directly from the first Reply it is at the followin URL: "Split Tunneling for Concurrent Access to the Internet and an Intranet" (Sorry for leaving the contents of the previous 2 replies in my first reply, that was as a result of doing too many different things at once!).
    0 pointsBadges:
  • HenryKafeman
    Can anyone offer any more Help please on Split Tunneling, et al?
    0 pointsBadges:
  • Astronomer
    Henry: Disabling of split tulleling is a security feature. The theory is that end user systems can't be trusted. I tend to agree with this assessment. If you connect to your internal net with a VPN you are essentially on the internal network and behind the firewall. If you still have a connection to the rest of the internet, your system can be a conduit for attacks that bypass the firewall. If split tunneling is disabled then you can't talk to any other networks while the VPN is in place even though you are using other nets to get to the internal net. When we set up our pix we left split tunneling disabled and immediately got complaints from prople who wanted to browse the internet while they were connected. The pix will not allow traffic to go back out the interface it just came in from. My workaround for this is to have them use the internal web proxy while they are using the VPN. This way they have to go out thru the firewall just like internal traffic. If you want to have real security, you shouldn't allow split tunneling for home users. On the other hand, if you trust the networks on both ends of a VPN, there is no need to prevent split tunneling. This in essence is how companies set up VPNs between sites so traffic will be secure even though it runs on public networks. Hopefully this is enough information for you to make an intellegent decision on where to allow split tunneling. rt
    15 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: