JFU49
asked on
vpn and ipsec services
I use a VPN connection (Cisco) to my company computer. Now I get "securing communication channel" when trying to connect then "Remote peer terminated connection." Recently I was playing with Systems Services and I think I disabled IPSec Services and can't seem to get it back. When I try to start it, I get "Could not start IPSec Services on local computer error 10048. Only one usage of each socket address protocol/network address/port is normally permitted." I've set the startup back to "Automatic" but IPSEC services will not start.
I use a VPN connection (Cisco) to my company computer. Now I get "securing communication channel" when trying to connect then "Remote peer terminated connection." Recently I was playing with Systems Services and I think I disabled IPSec Services and can't seem to get it back. When I try to start it, I get "Could not start IPSec Services on local computer error 10048. Only one usage of each socket address protocol/network address/port is normally permitted." I've set the startup back to "Automatic" but IPSEC services will not start.
Additionaly I had connected my second computer through the same Ethernet port using a crossover cable.
Additionaly I had connected my second computer through the same Ethernet port using a crossover cable.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I uninstalled and re-installed the client and that did the trick.
It's sad that that is the fix isn't it... I should do more research when this happens again- maybe there is something else that can be done... thanks again.
-rich
-rich
Ipsec only needs to be set to manual, not started really. Uninstall and reinstall the vpn client and certificates also. Did you enable a firewall recently, ICF on XP or add zonealarm... has your companies cert's expired or has their vpn address changed in any way?
I too use the vpn software from cisco, to a 3030 concentrator, it works well, both win32 and linux. I've encountered your error message before, and we needed to update our .pcf files (certs) to reflect a recent change. We also updated the client software on win32, it works much better now. (4.0.2b)
http://support.microsoft.com/default.aspx?scid=kb;en-us;314831
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q257225
enable oakley logging to better get an understanding of what the error might be: http://www.securityfocus.com/infocus/1526
Also, can you ping the ip or name the vpn is trying to reach...? "Contacting example.com
Cisco release notes for 4.0.2 are here- with possible bugs:
http://www.cisco.com/univercd/cc/td/doc/product/vpn/client/rel402/402aclnt.htm
GL!
-rich