Server 2003 IPSec Event ID 4292 ocasionally after reboot - Blocking TCP/IP traffic

We reboot our servers weekly, every 7 weeks or so, one of the servers is unreachable and needs to be rebooted.  
Windows Server 2003 R2 Standard edition
I have attached a txt file with the systeminfo output.
This server is not used to create VPN tunnels.

Is there any reason for Server 2003 to run IPSec Service?
Let me know if you need more information, I didn't want to make this too unreadable.
In the Event Log I recieve the following Event:
Event Type:      Error
Event Source:      IPSec
Event Category:      None
Event ID:      4292
Date:            11/16/2008
Time:            12:04:52 PM
User:            N/A
Computer:      SERVER
Description:
The IPSec driver has entered Block mode. IPSec will discard all inbound and outbound TCP/IP network traffic that is not permitted by boot-time IPSec Policy exemptions. User Action: To restore full unsecured TCP/IP connectivity, disable the IPSec services, and then restart the computer.  For detailed troubleshooting information, review the events in the Security event log.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 54 00   ......T.
0008: 00 00 00 00 c4 10 00 c0   ....Ä..À
0010: 01 00 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........

systeminfo-server2003.txt
runsysrunAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bignewfCommented:
Since you don't have an IPSec policy, disable the service. It should have no effect on the server functionality. However, test it just to make sure functionality is not impaired. The IPSec driver could be corrupt. It could be some local or group policy done by an admin that is not disabled. Unfortunately, I have seen this but have not found any hotfixes. Make sure all service packs are current. You will need to reboot after disabling this service

In a worst case scenario, you might have to rebuild the TCP/IP stack, and sometimes the winsock fix might even help
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.