I cannot access any device on my network via RDP or applications via host file - forwarded servers from my Windows 7 64 bit laptop using a Verizon wireless broadband connection and the Cisco 64 bit VPN client 188.8.131.520. I can connect easily via a DSL wired connection from home using the same laptop and VPN client and RDP.
The VPN client will connect to the VPN server (Easy VPN on Cisco 2821 router) over the wireless broadband connection (I can see it in the management console on the router) but it will pass no data. I cannot ping anything in the domain, nor the outside IP. When I try to ping from the laptop, it drops the VPN connection (Connection terminated by the peer).
The laptop is a Dell M4500 running Windows 7 Ultimate 64 bit OS. The VPN client is as stated, rev 184.108.40.2060. The internal wireless broadband card is a QualCom 5620 (EV-DO-HSPA) device (Gobi 2).
What must I do to get this configuration to perform and connect as the wired connection does?
Message was edited by: Timothy Carlisle Recently I discovered that the Cisco 64 bit VPN client running on my Dell Precision M6500 (Windows 7 64 bit OS) was able to connect correctly by using the wireless hotspot on my iPhone 4S (Verizon Wireless). It will also connect when tethered to the laptop via USB cable. Once I discovered this, I then was able to do the same on the laptop that spawned this discussion, by tethering to the boss's Blackberry Bold after downloading and installing a new Verizon Wireless Access Manager utility that allowed us to select the device (the Blackberry) for installation. I think that this has allowed us to bypass the Gobi2 wireless cards on both laptops and the factory installed Dell Connection Manager software which was incompatible with the Cisco 64 bit VPN client software. As far as I am concerned here, this new method (Smartphone hotspot and tethering) is the way to go for us, and has resolved all issues for remote connectivity for us. Thank you to all that contributed to this discussion. Tim Carlisle
The Solution provided in the Discussion has been captured in this Document:-
Solved! Go to Solution.
We fought with the same issue for quite some time before finding that it appears to be a default setting in the Verizon Access Manager Software that does not play well with the Cisco Client.
In VZAccess Manager, select Options | Preferences. Under the Connectivity options, the default setting of "NDIS Mode - Manually Connect" was selected. Changing this option to "Modem Mode - Manually connect" appears to have completely addressed the issue. We can now connect to the WWAN, establish a Cisco VPN session and have connectivity.
I had this problem on a Latitude e6510 with Windows 7 pro 32-bit.
The short story to how I fixed it is the following:
Completely uninstall VZAM, Dell Mobile Broadband Utility, Qualcomm Gobi 2000. Make sure there are no references to the WWAN card in device manager.
Restart the computer and reset the bios to default settings.
Install the R2750584 Driver for the 5620 wireless
Of course it took me a large amount of troubleshooting to get to this point. I tried 3 different versions of the Qualcomm Gobi 2000 drivers. R275082 doesn't work. Don't install the Dell Mobile broadband utility or connection manager or whatever it is. The Novatel one. I think that messes things up.
i don't know if this can assist you or not, i'm having same the same problem with HUAWEI 3G USB and found that even,
i'm running VM workstation 8 on my laptop and seems that is not supported (cisco VPN client start giving error 412 - remote peer not responding, connection terminated localy).
the work around was like this; install 3rd party VPN client (cisco compatible) where i was able to import my pcf file
and work flawlessly.
Shrew VPN client or any out there VPN client you can use to finish this headach, i hope cisco guys by that time correct what in the CVPND making these errors
Having this same problem. I have Dell Latitude E6510 with the Verizon Dell Wireless 5620 EV-DO-HSPA card. Using the latest version of Cisco VPN client (5.0.07.0290). The card appears to connect correctly and gains an internal address. But I can not ping any internal devices or access any the internal network resources.
The systems are running Windows 7 Enterprise x32 with the firewalls all turned off.
Same problem here on a Dell E6410. Dell Wireless 5620 EV-DO-HSPA connecting to Sprint. Version 5.0.07.0290 of the vpn client 64-bit on Windows 7 64-bit OS. I have been able to transmit vpn data when connected using CMU-300 Qualcomm card from the same laptop using Sprint's SmartView connection software.
I have an E6400 running Windows 7 x32 and have several co-workers running E6410's with Windows 7 x64 we all use the Verizon EVDO card. we have had some problems on the x64 but not on the x32's I believe it was a problem with the VPN client itself.
I gave up on the 64 bit client VPN WWAN connection on the Dell Precision M4500 Verizon EVDO 5620 card. What I am doing to affect the vpn connection I need, is to install the XP virtual machine (XP mode available from windows on Windows 7 Pro and Ultimate). On the XP virtual machine, install the Cisco VPN client 5.0.00.0340. Then you can run that from the XP mode Application on the windows 7 desktop, which starts the VM, and allows connection on the 32 bit client. It is not consistent however, and experiences dropped connections in some locations (Albany, Georgia) but runs fine in Columbus, GA. I think that is a Verizon issue however (cell resource allocation). I would really like for Verizon, Sprint, AT&T, et al to get together with Cisco, Qualcom, Dell, HP etc to work up a good WWAN connection solution for the 64 bit OS platform. They are not there yet, obviously.
I am having issues exactly like this as well but it is with the Dell AT&T card 5530. I have tried it on a Dell 6410 and 4300. I have tried running both Windows 7 32 and 64 bit both with the same result. The cisco client i am using is the 5.0.07.0290. It will connect but i can't ping or get to anything on the network. If i try the anyconnect connect client it will work just fine. Unfortunately only one of our 5 ASA’s is currently setup to use anyconnect, hence the need for the full client. If I use the exact same hardware and software configuration of the 5.0.07.029 client and the air card in Windows XP it works with no issues. It almost seems to be an issue with the cisco client. If anyone finds a solution to this issue please let us know.
Just wanted to put in a quick follow-up for anyone who can get the help. After speaking with our Verizon rep I was put in touch with a technician who had the answer in the simplest form. The Dell system ships with a program to manage the device. This default software is used to activate and run the broadband card and is needed for that activation. BUT --- Verizon has an enterprise class application (VZAccess) which fixes the issue. Using this program to connect to the Verizon network will allow the Cisco software to properly bind and now once a user has connected to the VPN they are given an internal IP address, bind correctly and can access the network properly.
Not sure if this problem will move to any other vendor (AT&T, Sprint) but I can only say for now we have a fix for our Verizon problem and I hope that I wont see it come back again.
Has anyone else experienced this problem?
I installed and verified that the VZAccess Manager was the correct version for the Chipset/OS (Dell 5620 / Win7 x32), the VZAM allows non-VPN surfing, but no access (as it shouldn't) to internal resources, the CISCO VPN client starts up, and nothing else happens. As described earlier in the thread. However once the Cellular Signal improves (starting at 1 bar of strenght: rated poor, improving to 4 bars: rated good) the VPN connection allows for access to internal resources.
Even with 1 bar of Cellular strength the VPN client is able to connect and stay connected. I need to give a definative answer to the boss that is a Cellular signal problem and not an IT/VPN problem.
When I was first working this issue, I contacted both Dell and Verizon for issue resolution. At that time, neither one could offer one. Is it possible that Verizon has produced something new that will address the 64 bit Cisco VPN client/Verizon wireless connection issue? I was hoping that they would release something soon, so that I can get a 64 bit connection going on my boss's Windows 7 Ultimate laptop, and stop all of the XP virtual machine hoop jumping, and latency issues. What exactly is the name and version number of the Verizon Access Manager that allows this improvement?
Please try and setup the WWAN Card connection as a Dial Up connection and try the VPN once more.
I hope this helps