Local IP address conflicts with the subnet of the remote VPN Server. Also, regardless of the Windows Firewall state, the Cisco VPN client works perfectly so I'm not convinced the statement that IPSec can't work if the WF is disabled unless the Cisco VPN v5 client uses a different protocol.)ĥ. (The Windows Firewall service on this Vista box is running as is the IPSec Policy Agent. Windows Vista with Windows Firewall disabled, which disabled IPSec service. (One location has a server that has RDP enabled through the RV082 and I can copy/paste the address into mstsc.exe and connect with no problems so the address is correct).Ĥ. (What network card is it talking about? The NIC on this computer allows ful LAN and Internet access so it obviously has a valid IP)ģ. Incorrect Password (I've checked, rechecked, and checked again, it's right)Ģ. This could be caused by one of the following:ġ. The client installs fine then returns the error: We installed first on a Vista Ultimate SP1 (fully patched through March 2009's update cycle).
Created a test user account then proceeded to install QuickVPN 1.2.11 downloaded yesterday from the Cisco web site. We ensured both had the current firmware (1.3.12.6-tm for the 42, 1.3.98-tm for the 82). We have a couple of customers seeking to use QuickVPN to allow their employees to connect to RV0x2's (one is a 42, the other an 82).
0 kommentar(er)
