IPSEC

I have a Windows 2003 Std server that I recently upgraded from Windows2000
that is serving as a Exchange 2003 Front End.

Recently we lost power and the server was restarted when the power came back
up. Once the system came up, there was no connection to the network and the
network devices did not show up. When I tried to restart several services
that failed to start, I received an error that the dependancies were not
started so the service couldn't start. I tried to look at the dependancies,
and received "win32: access denied".

I was able to correct the problem with not being able to access the service
dependancies. Most of the services are now starting as they should. I'm
still having problems with the Exchange services.
I can also see the network devices and properly configure them.

In order to connect to the network, I had to disable the IPSEC service. I
believe this is required for me to connect to the Exchange backend server.

When I enable IPSEC and restart the server, I can ping my local IP address,
but can't access the gateway.

Any ideas on fixing the problem are appriciated.


Thanks

Charles W

I'd need a lot more specific information on the types of IPsec policies in
the environment to really dig in, but here are some general pointers....

Basically, if you have account logon and logon auditing enabled, the system
should generate event id 547 audit failures in the Security event viewer if
IPsec Phase 1 (main mode) negotiations fail, so I'd start there. The
chapter 7 guide will walk you through them speciifc messages and much, much
more...

General IPsec Troubleshooting guide for server and domain isolation (applies
to just about any IPsec implementation)
http://www.microsoft.com/technet/sec.../ipsecch7.mspx

How to Enable an Oakley.log file
http://support.microsoft.com/kb/257225

How to configure IPsec on an Exchange backend on a cluster (may be related
to your config)
http://support.microsoft.com/kb/821839/


Jason


"CharlesW" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>I have a Windows 2003 Std server that I recently upgraded from Windows2000
>that is serving as a Exchange 2003 Front End.
>
> Recently we lost power and the server was restarted when the power came
> back up. Once the system came up, there was no connection to the network
> and the network devices did not show up. When I tried to restart several
> services that failed to start, I received an error that the dependancies
> were not started so the service couldn't start. I tried to look at the
> dependancies, and received "win32: access denied".
>
> I was able to correct the problem with not being able to access the
> service dependancies. Most of the services are now starting as they
> should. I'm still having problems with the Exchange services.
> I can also see the network devices and properly configure them.
>
> In order to connect to the network, I had to disable the IPSEC service. I
> believe this is required for me to connect to the Exchange backend server.
>
> When I enable IPSEC and restart the server, I can ping my local IP
> address, but can't access the gateway.
>
> Any ideas on fixing the problem are appriciated.
>
>
> Thanks
>
> Charles W
>
>
>
>