My company uses this as their VPN client. I have not had any issues with it until Monday of this week in which the VPN started throwing this error (from the Windows Events log) and disconnecting every 10 minutes or less on average:
NC route conflict detected, disconnect.
Peer address: <some.ip.address>
Any ideas as to what might be causing this? A couple more details:
netsh int ip reset ipconfig /release ipconfig /renew
I have reached out to our tech support in house but have received no feedback other than having me reinstall the client, reboot my home router, etc.
I'm hoping for some ideas on what I can do to troubleshoot this further.
Solved! Go to Solution.
Have you installed any persistent routes on that system? You can do a "route print" to see if there is anything under persistent routes.
Or, has the admin configured any split-tunneling rules that may be causing a conflict?
What are the differences between the two computers that can generate routes.
For example installing vmware workstation or fusion can create local route subnets. You are looking for routes on this computer that are needed in your split tunnel to the remote network. This would be what is causing the conflict.
@akanoon Thanks for the reply. I don't have any persistent routes. I will double check with the admins on the split tunneling possibility.
@spuluka That's an interesting idea because I do have Hyper-V installed. Could that (potentially) cause the issue you are describing?
Yes, these virtualization platforms create virtual networks inside your PC. If they choose a network that overlaps your resources used on the vpn this could cause the error you are getting.
In a dos window do a route print to see what networks on on the PC. Your help desk and let you know if there are any conflicts.
The issue has been resolved.
It ended up being an HP printer my work sent me. I found where some HP models conflict with the VPN for some reason (even though the IP address was different). See HP Printer Driver/Windows Print Spooler causes VPN to disconnect/reconnect continually.
It ended up being I had to disable the Spooler service and remove the HP printer drivers and packages completely. After that the issue went away.
Thank you for your help! It helped me eliminate other possibilities.
Thanks for the update. It would have been a long time before I suspected a printer driver.
But forgot to ask the important first question, anything new installed on this computer?