Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPN connection kills outside connection

Status
Not open for further replies.

tristanlee85

Programmer
Jul 6, 2009
5
US
I'm really not sure how to explain it technically, but here is my scenario: I have my LAN connection configured as a static IP of 192.168.1.120/255.255.255.0 on a gateway of 192.168.1.1. With this set, I am able to take my laptop and RDP into this (.120) machine.

Now for work, I have 2 VPN connections I am required to use. One is a Cisco VPN and the other is a PPTP connection I setup using the Windows VPN connection wizard.

I can't seem to recreate the problem over and over, but here is my issue. Once these VPN connections have been established, I am no longer able to RDP into my machine. It's like one of the VPN connections is taking over. I made sure to un-check the "Use default gateway on remote network" for the PPTP connection. Otherwise, if it's checked, my outgoing IP is that of the VPN instead of my modem IP.

Sometimes I can go days without issues and then sometimes I can go days with the issue. Does anyone have any ideas for me? This critical because I am unable to do work from time to time. I RDP from my laptop to my desktop for my work. My desktop (.120) is running Windows XP on VMWare as my development machine.
 
Regarding the Cisco VPN. Ask the VPN administrator to enable split tunneling. This will allow you to talk to your local LAN while the VPN is connected.

Be advised however, that some orgs have policys against using split tunnelying.

James
 
Hmm. I don't believe it is the Cisco VPN because I don't have the problem when connected to Cisco, only the PPTP VPN. Once I connect to the PPTP, I can't remote to my desktop from my laptop, but as soon as I disconnect, I can RDP in... I don't get it.
 
Using the Cisco VPN as an example. The destination device (The VPN Server) usually has to be configured to allow the source device (The VPN Client) to bypass the tunnel for local traffic. I'm sure whatever terminates your PPTP connection needs to be configured likewise.

I haven't tried this but in theory you should be able to install a static route on your windows box to ignore / over rule what the VPN client mandates.
 
That's what one of my friends was telling me. He's been doing VPN stuff for a long time (way way over my head) and he said that static routes would probably fix my problem. I'll have to look into that.
 
Maybe a second NIC would work too? It's a VM maybe a second virtual NIC?
 
Well, I tried having a 2nd virtual NIC, but that didn't help. I have looked into the windows 'route' command, but I'm a bit stuck on what to do. I am guessing I need to add a persistent route? If so, I'm not exactly sure what to set as my destination, gateway, and interface as well as metric.

Currently, with both VPNs connected, here is my routing table:
Code:
C:\Documents and Settings\Administrator>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x20003 ...00 0c 29 c6 a6 cf ...... AMD PCNET Family PCI Ethernet Adapter - Pack
et Scheduler Miniport
0x30004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x30005 ...00 05 9a 3c 78 00 ...... Cisco Systems VPN Adapter - Packet Scheduler
 Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1   192.168.1.120       10
         10.0.0.0        255.0.0.0     10.10.10.101    10.10.10.101       1
     10.10.10.101  255.255.255.255        127.0.0.1       127.0.0.1       50
   10.255.255.255  255.255.255.255     10.10.10.101    10.10.10.101       50
      67.216.17.2  255.255.255.255      192.168.1.1   192.168.1.120       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
       172.17.0.0      255.255.0.0   172.17.194.106  172.17.194.106       10
   172.17.194.106  255.255.255.255        127.0.0.1       127.0.0.1       10
   172.17.255.255  255.255.255.255   172.17.194.106  172.17.194.106       10
     173.9.203.29  255.255.255.255      192.168.1.1   192.168.1.120       10
      192.168.1.0    255.255.255.0    192.168.1.120   192.168.1.120       10
      192.168.1.0    255.255.255.0       172.17.0.1  172.17.194.106       1
    192.168.1.120  255.255.255.255        127.0.0.1       127.0.0.1       10
    192.168.1.255  255.255.255.255    192.168.1.120   192.168.1.120       10
        224.0.0.0        240.0.0.0     10.10.10.101    10.10.10.101       50
        224.0.0.0        240.0.0.0   172.17.194.106  172.17.194.106       10
        224.0.0.0        240.0.0.0    192.168.1.120   192.168.1.120       10
  255.255.255.255  255.255.255.255     10.10.10.101    10.10.10.101       1
  255.255.255.255  255.255.255.255   172.17.194.106  172.17.194.106       1
  255.255.255.255  255.255.255.255    192.168.1.120   192.168.1.120       1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top