For reference: I have had sporadic problems with the Cisco VPN client, which I installed after installing Parallels (3.0, 4128). For me, the solution was "ifconfig fw0 down" -- none of the other stuff, to do with restarting the kext, appears to have been either necessary or relevant.
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Cisco VPN madness - ifconfig fw0 down
- Thread starter seebs
- Start date
What is maddening is that this issue has been around since the beginning. I had to de-install and re-install PWS and Cisco also (several times). Downing the one interface does work but this is a pain and problematic in some cases. By comparison VMWare, while it warns of this potential issue, does not cause this problem.
My final fix was to de-install both (leave the HD images), reboot, re-install PWS, reboot, re-install Cisco, reboot, and to script the downing of the fw0 interface. After that the host VPN started to work again.
My final fix was to de-install both (leave the HD images), reboot, re-install PWS, reboot, re-install Cisco, reboot, and to script the downing of the fw0 interface. After that the host VPN started to work again.
Upton O'Good
Member
I'm having this problem too.
The other problem I had was that, when I migrated a couple of my Virtual PC VMs, they were created with Shared Networking by default, which caused an error when I tried to start them. Changing Networking to Bridged Ethernet fixed this problem, but now this appears to be the only network option available in these VMs.
Could these problems be related?
Oh, it also adds two copies of a configuration called "Ethernet Adapter ((null))" to my Mac's Network Port Configurations, which seems rather an odd thing to do.
The other problem I had was that, when I migrated a couple of my Virtual PC VMs, they were created with Shared Networking by default, which caused an error when I tried to start them. Changing Networking to Bridged Ethernet fixed this problem, but now this appears to be the only network option available in these VMs.
Could these problems be related?
Oh, it also adds two copies of a configuration called "Ethernet Adapter ((null))" to my Mac's Network Port Configurations, which seems rather an odd thing to do.