Showing results for 
Search instead for 
Did you mean: 

IP route not working on Windows 10 after connection to VPN


I am on Windows 10 Home Version 1903


I have installed SonicWall VPN (as a workaround) and Cisco VPN client.

My VPN client shows "connected" a few secs after I start the vpn session


VPN Client creates the following IP Interface on my Windows

Ethernet adapter Ethernet 3:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::745b:83cd:3481:761f%12
   IPv4 Address. . . . . . . . . . . :
   Subnet Mask . . . . . . . . . . . :
   Default Gateway . . . . . . . . . :

And also Configures the following IP Routing rules

IPv4 Route Table
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric    100         On-link    291         On-link    291         On-link    291

I am supposed to connect to remote server IP address

when I execute the following PowerShell command line

Find-NetRoute -RemoteIPAddress "" | Select-Object ifIndex,DestinationPrefix,IPAddress,InterfaceAlias,NextHop,RouteMetric -Last 1

I get this result

ifIndex           : 12
DestinationPrefix :
IPAddress         :
InterfaceAlias    : Ethernet 3
NextHop           :
RouteMetric       : 65

So, what I get from this is that the route should work as expected.

I am running wireshark on Ethernet 3 interface and I am checking on traffic on this interface.

When I try to ping, I do not see any traffic going through this interface in Wireshark as a matter of fact, when i sniff traffic on all interfaces, i dont see any icmp traffic at all

Can anyone show me some pointers as to what could be wrong here ?


best regards,


3 Replies 3

VIP Community Legend VIP Community Legend
VIP Community Legend

SonicWall VPN  - when you installed this one, is this working, if so can you post show ip route on working one to compare ?



***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help



SonicWall is only installed so that Cisco VPN Client works on Windows 10. It is a workaround.

What I mean by "routing not working" is that even though the IP rule seems to be configured as shown in my original post, ping does not get routed to the Ethernet 3 interface



   Running multiple VPN clients on the same devices, creates some issues on the long run. Given the fact that also Legacy Cisco VPN Client is EOL for long time, and not officially supported on Windows 10, you'll constantly run into issues, whenever a Windows update, or driver update happens. I would consider deploying a currently supported VPN solution, like AnyConnect.



Cristian Matei.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers