Windows or Exchange?

  • Thread starter Thread starter EdwardLHall
  • Start date Start date
E

EdwardLHall

Ok, this is a good one.

2003 DC, GC, DNS, & WINS

NetDiag & DCDiag pass all tests

Always get the following errors on boot:

1. Kerberos [537] An error occurred during login.
2. UserENV [1097] Windows cannot find the machine account, the local
security authority cannot be contacted.

According to Microsoft these errors are normal and should be ignored.

THEN we installed Exchange Server 2003. Now we get the first two
errors followed by these,

1. SA fails to start [No log error]
2. IS fails to start [Dependency on SA]
3. MTA fails to start [Depenency on SA]
4. Event fails to start [Dependency on IS]
5. MSADC [8026] LDAP bind was unsuccessful - Server down.

After boot we can manually start all of these services.

Any Ideas?
 
Never mind, we found the problem.

There was a second network adapter in the server that was not being
used so we had disabled it in device manager.

Apparently this was causing a delay in starting either the Kerberos or
Netlogon service.

After we enabled the extra adapter and fed it a bogus IP address all of
the other problems resolved.
 
If you've configured a bogus scope on this NIC, ensure that it is not being
registered in DNS (netlogon does this on startup and every 12 hours
thereafter). If you have an unreachable IP address registered in DNS you'll
have serious issues.

You can stop it from registering in DNS by unchecking "Register this
connection in DNS" in the advanced DNS tab of TCP/IP properties.


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/
 
Back
Top