Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » Up and Running » Virtual Private Networking » Cisco VPN VZWireless and Snow Leopard
Search Topic:
Uniqs:
176
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
AuthorAll Replies

bg1999

join:2005-10-02
Bayville, NJ

Cisco VPN VZWireless and Snow Leopard

I have an error 51 issue and maybe one of you have experienced this before.

I'm happy to say that my VPN client works fine with Apple Snow Leopard when I connect via WIFI or Ethernet.

When I'm online with VZ Wireless, I can't connect with the VPN. Instead, I get this message:

Error 51: Unable to communicate with the VPN subsystem.
Please make sure that you have at least one network interface that is currently active and has an IP address and start this application again.

Any suggestions would be appreciated. The VPN is 4.9.01 (0030)

Thanks,

bg


LinkTech
Former Linksys Tech
VIP
join:2002-07-02
Mission Viejo, CA

I had someone on Verizon card and this worked. Found on another forum.

1. Quit the VPN client
2. Unload the VPN drivers: sudo kextunload /System/Library/Extensions/CiscoVPN.kext
3. Insert card and connect
4. Reload VPN drivers: sudo kextload /System/Library/Extensions/CiscoVPN.kext
5. Start the VPN client
6. Connect

bg1999

join:2005-10-02
Bayville, NJ
Thanks for the tip. I also found a similar workaround but they are both based on stopping and re-starting the vpn. I'm glad I'm only on cellular once and a while.


NoFix

@cox.net

Just an FYI - this is a known problem in Cisco's VPN client on the MAC. it was discovered a couple of years ago. Whether is occurs depends on a lot of factors so two seemingly identical machines can exhibit different behavior. Even a single machine may behave differently at times.

It is known that the CIsco VPN client was written to assume all connections were hardwired ethernet or 802.11 wireless. The ppp connection setup when you use VZ Wireless (or any other vendor's "cellular " network) confuses it.

The only known workaround has already been mentioned. Our company is not aware of a fix from Cisco so our uses have to unload and reload the VPN as described. Quite a pain.
-
Forums » Up and Running » Virtual Private Networking


Friday, 04-Dec 23:44:53 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.
page compression OFF
Most commented news this week
· [163] Comcast Releasing Promised Usage Meter
· [145] Avast Antivirus Has Gone Mad
· [126] Comcast Makes NBC Universal Acquisition Official
· [104] Graduate Student Unveils Sprint's GPS Sharing With Feds
· [101] Google Invades ISP, OpenDNS Turf With Google Public DNS
· [83] FCC Ponders Moving From PSTN To IP Voice
· [81] Latest Consumer Reports Survey Not Kind To AT&T
· [75] The Bandwidth Hog Does Not Exist
· [74] Sprint Defuses GPS Privacy Media Bomb
· [70] Baltimore To Ban Lazy Cable Installs
Most people now reading
· False positive in Avast! or is it real? [Security]
· Windows 7 boot manager editing questions [Microsoft Help]
· Using AirMax to provide triple play services? [Wireless Service Providers]
· 3.x Feral Druid - Bear Tanking Guide [World of Warcraft]
· IMG 1.7 (IMG Updates and Discussion) [Verizon FIOS TV]
· Google takes aim at browser redirection [Security]
· Connecting to Google Voice Via SIP [VOIP Tech Chat]
· IPComms Free DIDs now with sip registration maybe?? [VOIP Tech Chat]
· UPS - What do you people think happened? [General Questions]
· Farewell [Bell Canada]