Professional Documents
Culture Documents
INTRODUCTION
This document is designed for VPN users who are having issues connecting
to the VPN service. If the VPN Service is up and running, users should follow
these troubleshooting steps before contacting C&IT Services.
Problems connecting
to VPN service
Home
router/firewall N See Section C –
set up for VPN? Home Network
Y
See Section E –
Capture Client Log
Many users will have personal firewalls installed on their home computers.
When using the Cisco VPN client you may be prompted to allow the client
through your firewall on these ports. Check that the firewall allows the 3 ports
through – if not, statically add the 3 ports listed above into your personal
firewall.
F-Secure Firewall
F-Secure 2007 does not work with Cisco VPN client – see F-Secure
technical note below:
Firewall in Cisco VPN Client does not work with Client Security [52211]
Cisco VPN Client has a built-in stateful firewall, which is not compatible with
F-Secure Internet Shield. If Cisco VPN is installed before F-Secure Client
Security, the side-grade component disables the firewall in Cisco VPN Client.
However, in some cases it might be that the side-grade cannot identify a new
version of VPN Client. In that case you can disable the integrated firewall
manually.
Bullguard 7.0 currently causes a blue screen when using the VPN client. The
resolution is to downgrade Bullguard:
If your home network is setup correctly and your ISP isn’t blocking any ports,
there may be an issue with your broadband router. Try the following:
http://applications2.napier.ac.uk/software/default.aspx?option=VPN
Click Enable
Log window
After the connection attempt fails, go back to the Log tab and click Log
Window. Click Save to save the log.
Email the file to c&it.support@napier.ac.uk
The following error ―Reason 442: failed to enable virtual adapter‖ appears
after Vista reports a duplicate IP address detected. Subsequent connections
fail with same message, but Vista doesn't report a duplicate IP address
detected
To work around error 442, do the following steps:
If this procedure does not work, run the following command from cmd:
reg add HKLM\System\CurrentControlSet\Services\Tcpip\Parameters /v
ArpRetryCount /t REG_DWORD /d 0 /f
Then reboot.
This resolves the issue until Vista reports a duplicate IP address again. Follow
the preceding steps to resolve it again. If that doesn't work, you might have
UAC enabled. If so, you must run cmd as administrator and repeat the
previous registry workaround.