Home / server / Questions / 126458
Accepted
Bryan Roth
Asked: 2010-03-26 16:39:18 +0800 CST

Unable to access local network when Cisco VPN client is connected

  • 772

I'm a developer and don't have much networking expertise, so bear with me.

I'm using the Cisco VPN Client 5.0.02.0090 to connect to my work's VPN that way I can RDP into my work computer. Once connected, I can't ping anything on the local network once connected to the VPN thus I am unable to access my work's network. This used to work about two weeks ago but abruptly stopped working today.

However, I have the Cisco VPN Client installed on my laptop and I am able to ping and RDP into my work computer from there. Both my desktop and laptop computers are connected to the same router at home.

I have tried the following so far:

  • Rebooted my computer
  • Reinstalled VPN client
  • Updated NIC drivers
  • Disabled firewall
  • Opened up ports 500, 4500, and 10000

Any help would be much appreciated. Thanks!

cisco-vpn local-area-network

5 Answers

  1. Best Answer

    This is completely normal behaviour for the Cisco VPN client. In fact, many workplaces absolutally DEMAND this, as their contracts may require that if a computer is on their network, then it must ONLY be on their network (and not multi-homed).

    Yes, there are ways around it, but you need to speak to your sysadmin about this.

    • 2

  2. Did you try disabling the client's built in firewall(not the one of the OS)? That frequently gets in the way.

    • 1

  3. Well, have you talked to your IT department? Seems like the most logical first step.

    • 0

  4. I have never seen a VPN configuration where the local network was accessable when the VPN connection was live. This is to protect the data from being clone out on the LAN. The only was around this is if the VPN admin will possibly allow what is known as "split tunneling". My guess is it will be a serious no go.

    • 0

  5. Make sure "Allow local lan access" is checked in the VPN client.

    If you are in control of your lan, consider changing the subnet of that lan to one of the following if its not this already.

    • 192.168.214.0/24
    • 192.168.215.0/24
    • 192.168.216.0/24

    This is what my Sys Admin buddy told me I needed to do to make this work. YMMV.

    Ed

    • 0