Yet I'm certain that's not the issue here, as I can easily prove to myself when using the VPN Client on the VM and changing nothing else. That error is normally attributed to bad credentials having been entered, and every troubleshooting reference I've found points to user error being the only possible cause. However, when I run VPN Client directly on the development workstation's OS itself (also Win 7), it has been failing, and gives me Authentication Error 413. It's a typical set up, using an RSA SecureID soft token, and I'm successfully able to connect through VPN Client (v 5.) when I run it within a VirtualBox instance (Win 7) on my development workstation.
#Cisco vpn client 5.0.07 software
I'm a software developer contractor, and I've been given Cisco VPN access to a customer's network.
0 kommentar(er)
