Re: IPSEC PolicyAgent Service failure on first boot of new server
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Mar 2006 15:47:36 -0600
Off hand I don't know and if future reboots do not exhibit the problem then
that is probably a quirk you will expect to see. If you have not seen it the
link below it is the best I know of on troubleshooting ipsec for Windows and
may help. --- Steve
http://www.microsoft.com/technet/security/topics/architectureanddesign/ipsec/ipsecch7.mspx
"bbergero" <bbergero@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EE4726E7-4E27-4A9A-80D6-10EADB9FC4C3@xxxxxxxxxxxxxxxx
Win2K Adv Svr SP2 Cluster Active/Passive
Virtual SQl Server 2K SP2
When one of the servers in the cluster is replaced (re-use same drives),
on
the first boot, PolicyAgent events 319 and 321 (Oakley and Ipsec driver
failed to start). Services shows IPSEC PolicyAgent is stopped. However,
everything is OK on next boot. Is this expected? Is there some
association
with hardware (CPU identity or NIC MAC address)? Or is this related to
something fixed in a later Service Pack?
Thanks
.
- Follow-Ups:
- Prev by Date: Re: Security Updates and RDP
- Next by Date: Re: tracking files to/from Windows 2003 server
- Previous by thread: Re: Enter network password workaround for hosted documents
- Next by thread: Re: IPSEC PolicyAgent Service failure on first boot of new server
- Index(es):
Relevant Pages
|
|
