Add to My Yahoo! | Google Reader or Homepage | Add to Windows Live | Add to Windows Live Alerts

Wictor Wilén

SharePoint Server MVP / Author / MCT / MCTS / MCP / MSc writing about SharePoint and other interesting Microsoft technologies

IPSEC Services could not be started

Posted at 2006-09-11 03:15 by Wictor Wilén in Windows XP , Network with 14 comments.

I ran into some troubles with the IPSec Services on my Windows XP SP2 machine today. This service was needed by a VPN application that I installed to connect to one of our customers. But during the last re-install of my machine, I set this service to manual startup, and now when I tried to start it It could not start. I recieved the following error message when trying to start it:

Error message 10048: Only one usage of each socket
address (protocol/network address/port) is normally
permitted.  

The Event Viewer displayed the following:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 2006-09-11
Time: 10:08:10
User: N/A
Computer: LAPTOPWW
Description:
The IPSEC Services service terminated with the following error:
Only one usage of each socket address (protocol/network address/port) is normally permitted.

To find out which application that used the ports that the IPSEC Services needed I started up a command prompt and used netstat, as below, to find out the PID of the process. This command below will display all the active UDP connections and the PID (-o). The findstr function searches the output from the netstat and shows the lines containing the text "500" - which is the UDP port the IKE uses.

c:\> netstat -p UDP -n -a -o | findstr 500
UDP 0.0.0.0:500 *:* 316
UDP 0.0.0.0:4500 *:* 316

Using the Task Manager I found out that PID 316 was used by the Cisco VPN Service and I shut it down and then IPSEC services started fine!

Comments and trackbacks

#  Thanks! by Michael
Screenshot from websnpr Thanks for this post. I was experiencing the same issue and Google led me here. All is good now!
#  Re: Thanks by Wictor
Screenshot from websnpr Glad I could help!
#  More thanks! by Nick
Screenshot from websnpr Many thanks for an excellent spot of troubleshooting, helped me out of a tight spot!
#  Re: More thanksG by Wictor
Screenshot from websnpr Great! According to the stats this post is one of the most searched for posts.
#  Thank you :) by Baljeetsingh
Screenshot from websnpr It worked, were able to make it work very quick. Thanks for posting this. Cheers.
#  MANY MANY THANK by Teddy
Screenshot from websnpr My DNS was blocking IPsec from starting after a KB911829 update. This update was to prevent Vista from getting a X in 'new message' body area using OWA. Netstat found PID 1348 to be the issue, which was DNS (searched task mgr pid), so I ended the task. Stared IPsec, then restared DNS in Services. All is back to normal! Thanks,
#  Perfect! by Markus
Screenshot from websnpr Thanks for this post! It was the solution.
#  great job by M.H.
Screenshot from websnpr thanx dude, It was driving me crazy... this helped really a lot
#  awesome by Julian
Screenshot from websnpr One of my clients started getting this error. Turned out it was DNS also like Teddy. Proved to be a quick fix thanks to Google search :-)
#  Crazying by Randy
Screenshot from websnpr Thanks body. It seems good for everybody, but the service block the port is the VPN itself. What should I do?
#  IPSec failure by Peter Merner
The solution posted worked for me on Windows Server 2003 on January 14 2010. Never was able to figure out what rogue app hijacked UPD 500 though.
#  IPSec Failure by Gabriel Tetrault
Screenshot from websnpr Same issue as Peter. Client had this issue on their SBS 2003 server. DNS was using UPD 500. Ending the DNS.exe process, starting the IPSec service, then starting the DNS service did the trick. Thanks for help!
#  Error 10048 by Steve
Screenshot from websnpr Same issue as Peter and Gabriel, issues began after being hit with AntiVirus 2010 virus/malware. Great tip, very much obliged!
#  IPSEC issue by zykon
My IPSEC service works...for about 10mins..after new install...then it stops...drops everyone from my RDP session...when i want to restart IPSEC...it says lsass.exe missing...but its there...in windows\system32 folder...but ipsec wont start...error -2...file missing...
Make a comment on this post:
Subject:  

Your name:  
Your Url:  
Note: submissions may have to be approved before being visible, so don't submit your comment multiple times.
Real Time Web Analytics