Ipsec Service Not Starting Error 10048
Contents |
you try to restart the service, you may receive this message: Error 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted. If you look
Ipsec Service Not Starting In Windows Server 2003
in the Event Log, you'll see that IPSec has entered block mode. The ipsec driver has entered block mode recommendation is to disable IPSec services and restart the server. Don't follow that advice. To get everyone working quickly, stop
Hkey_local_machine\system\currentcontrolset\services\tcpip\parameters\reservedports
the DNS Server service. Then start the IPSec service start. Restart the DNS Server service and everything should be back to normal - at least for now. This behavior is due to a windows could not start the network policy server service on local computer problem after installing update MS08-037 which addressed DNS vulnerabilities. To avoid the problem in the future, you'll need to edit the registry key that lists the DNS port reservations. Check out the details here for more info. Share | Posted by Al Eriksson at 8:05 AM Labels: SBS, Server 4 comments: DStiner said... Thanks Al, this helped me out. July 22, 2011 at 8:46 AM Patrick said... You saved me! Thanks. June 11, 2012 at 6:51 AM Unknown said... You saved me too, Thank you for existing my friend! July 30, 2014 at 3:10 PM Rob Falk said... Thanks for the band-aid and providing the link for the permanent fix. September 29, 2014 at 8:01 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me Al Eriksson Based in San Clemente, California, Attainity LLC provides business technology consulting and services for growing companies. As president of Attainity, Al Eriksson presents his ideas, thoughts and suggestions on this blog. For more information, visit Attainity's web site at www.attainity.com. View my complete profile Subscribe To Posts Atom Posts Comments Atom Comments Blog Archive ► 2012 (7) ► November (1) ► October (2) ► August (1) ► July (1) ► May (1) ► March (1) ► 2011 (8) ► October (1) ► September (2) ► August (1) ► July (1) ► June (2) ► January (1) ▼ 2010 (50) ► December (2) ► November (4) ► October (5) ► September (4) ► August (4) ► July (5) ► June (4) ► May (4) ▼ April (5) IPSec service won't start
360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet http://www.seasideit.com/2010/04/ipsec-service-wont-start.html Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/912023 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
any issues. IPSEC Services could not be started Tags: Windows XP, Network Monday, September 11, 2006 5:15:27 AM I ran into some troubles with http://www.wictorwilen.se/Post/IPSEC-Services-could-not-be-started.aspx 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 http://www.theeldergeek.com/forum/index.php?showtopic=9408 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 not start 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: ErrorEvent Source: Service Control ManagerEvent Category: NoneEvent ID: 7023Date: 2006-09-11Time: 10:08:10User: N/AComputer: LAPTOPWWDescription: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 ipsec service not 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 500UDP 0.0.0.0:500 *:* 316UDP 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! 19 Comments Michael said Tuesday, May 20, 2008 9:43:39 AM Thanks for this post. I was experiencing the same issue and Google led me here. All is good now! Wictor said Tuesday, May 20, 2008 10:27:36 AM Glad I could help! Nick said Wednesday, October 8, 2008 9:12:53 AM Many thanks for an excellent spot of troubleshooting, helped me out of a tight spot! Wictor said Thursday, October 9
the page. Sometimes the error will need to be fixed by an administrator before the site will become accessible again. You can try to refresh the page by clicking here ← Return to the index