<div>
If you check your event log, are you getting the Event ID 4292 along with 7023. <br />
If it is the case, then take a look at the following KB.<br />
Follow the resolution section in the KB<br />
<a href="http://support.microsoft.com/kb/912023/en-us" rel="ugc">http://support.microsoft.c<wbr />om/kb/9120<wbr />23/en-us</a><br />
&nbsp;<br />

</div>


<div>
This appears to have been definitely the answer! &nbsp;Thanks!<br />

</div>


<div>
<div class="content wysiwyg-content">
I have a Windows 2003 Standard server as a single domain controller for my domain. &nbsp;I have been having the IPSEC service failed to start on the server periodically. &nbsp;The Event log has the following:<br />
<br />
Event: 7023<br />
<br />
The IPSEC service terminated with the following error:<br />
Only one usage of each socket address (Protocol / &nbsp;Network Address / Port) is normally permitted.<br />
<br />
The server seems to be pretty much dead in the water as for doing its normal roles. &nbsp;DHCP is not allocating addresses. &nbsp;A ping to the server is not returned. &nbsp;I can't connect a network drive. &nbsp;Etc.<br />
<br />
This server does NOT have the Cisco VPN client on it. &nbsp;I have read numerous sites that have shown a problem with it that generates this problem. &nbsp;It's not the case with this.<br />
<br />
I am looking for any suggestions as I have not had much luck finding anything else that might be the cause.<br />
Thanks!<br />

</div>
</div>


I have a Windows 2003 Standard server as a single domain controller for my domain.  I have been having the IPSEC service failed to start on the server periodically.  The Event log has the following:

Event: 7023

The IPSEC service terminated with the following error:
Only one usage of each socket address (Protocol /  Network Address / Port) is normally permitted.

The server seems to be pretty much dead in the water as for doing its normal roles.  DHCP is not allocating addresses.  A ping to the server is not returned.  I can't connect a network drive.  Etc.

This server does NOT have the Cisco VPN client on it.  I have read numerous sites that have shown a problem with it that generates this problem.  It's not the case with this.

I am looking for any suggestions as I have not had much luck finding anything else that might be the cause.
Thanks!


If you check your event log, are you getting the Event ID 4292 along with 7023. 
If it is the case, then take a look at the following KB.
Follow the resolution section in the KB
http://support.microsoft.com/kb/912023/en-us
 


This appears to have been definitely the answer!  Thanks!


IPSEC service fails on Windows 2003 domain controller

I have a Windows 2003 Standard server as a single domain controller for my domain.  I have been having the IPSEC service failed to start on the server periodically.  The Event log has the following:

Event: 7023

The IPSEC service terminated with the following error:
Only one usage of each socket address (Protocol /  Network Address / Port) is normally permitted.

The server seems to be pretty much dead in the water as for doing its normal roles.  DHCP is not allocating addresses.  A ping to the server is not returned.  I can&amp;#39;t connect a network drive.  Etc.

This server does NOT have the Cisco VPN client on it.  I have read numerous sites that have shown a problem with it that generates this problem.  It&amp;#39;s not the case with this.

I am looking for any suggestions as I have not had much luck finding anything else that might be the cause.
Thanks!


Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).