gromack
asked on
Cisco Quick VPN problems...
I've got a remote user, windows 10 (groan!), connecting to a cisco RV110 gateway, that all of a sudden stopped working.
Firmware on router is current & made sure the .pem file was in users QuickVPN Client folder on their computer.
When connecting, I get the Activating Policy window, the Verifying Network window, then 'The remote gateway is not responding. Do you want to wait?' & never any further, but at the same time, the router's VPN staus shows as connected?!?
This was working fine, for the last year & a half, up until a day or two ago.
USer's firewall is set to allow program through, as well, although this never was a problem in the past!
I'm using comcast business on router end & ATT dsl on users end.
Any suggestions?
Thanks!
Firmware on router is current & made sure the .pem file was in users QuickVPN Client folder on their computer.
When connecting, I get the Activating Policy window, the Verifying Network window, then 'The remote gateway is not responding. Do you want to wait?' & never any further, but at the same time, the router's VPN staus shows as connected?!?
This was working fine, for the last year & a half, up until a day or two ago.
USer's firewall is set to allow program through, as well, although this never was a problem in the past!
I'm using comcast business on router end & ATT dsl on users end.
Any suggestions?
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I was wondering if a security update on Windows 10 caused the break.
You mentioned that the VPN worked even after Windows 10 upgrade, so I won't think the problem is exactly Windows 10.
Try uninstalling the client first and re-install it or do a system restore (You will need to re-install the client even after a restore as the tokens change)
Consider keeping your Windows 10 especially since it's free till mid 2016
You mentioned that the VPN worked even after Windows 10 upgrade, so I won't think the problem is exactly Windows 10.
Try uninstalling the client first and re-install it or do a system restore (You will need to re-install the client even after a restore as the tokens change)
Consider keeping your Windows 10 especially since it's free till mid 2016
ASKER
Rolling back to Win 7 did the trick. As it turned out, the user wasn't crazy about WIn10 & was glad to have her old computer back!
ASKER