03-09-2020 05:45 AM
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. . . . . . . . . . . : 172.77.0.114 Subnet Mask . . . . . . . . . . . : 255.255.255.248 Default Gateway . . . . . . . . . :
And also Configures the following IP Routing rules
IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 172.16.0.0 255.255.0.0 172.77.0.113 172.77.0.114 100 172.77.0.112 255.255.255.248 On-link 172.77.0.114 291 172.77.0.114 255.255.255.255 On-link 172.77.0.114 291 172.77.0.119 255.255.255.255 On-link 172.77.0.114 291
I am supposed to connect to remote server IP address
172.16.14.65
when I execute the following PowerShell command line
Find-NetRoute -RemoteIPAddress "172.16.14.65" | Select-Object ifIndex,DestinationPrefix,IPAddress,InterfaceAlias,NextHop,RouteMetric -Last 1
I get this result
ifIndex : 12 DestinationPrefix : 172.16.0.0/16 IPAddress : InterfaceAlias : Ethernet 3 NextHop : 172.77.0.113 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 172.16.14.65, 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,
Martin
03-09-2020 05:59 AM
SonicWall VPN - when you installed this one, is this working, if so can you post show ip route on working one to compare ?
03-09-2020 06:03 AM
Hello
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
03-14-2020 03:48 AM
Hi,
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.
Regards,
Cristian Matei.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide