We had a single box running exchange 2003 in a all server 2003 ad(native). I've successfully did a swing migration to a exchange 2007sp1 temp box and removed the old exchange server. After some hardware upgrades to the original box i installed 2003r2 and exchange 2007sp2 Everything is working fine,mail flows, i can move mailboxs to their new home, etc. However on a reboot i get a number of errors in the event log and the exchange services don't start. I can however manually start them and everything works without error. Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5719 Date: 11/8/2009 Time: 4:21:48 PM User: N/A Computer: HERMES Description: This computer was not able to set up a secure session with a domain controller in domain HARRIS-NT due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 5e 00 00 c0 ^.. Event Type: Error Event Source: Userenv Event Category: None Event ID: 1053 Date: 11/8/2009 Time: 4:21:50 PM User: NT AUTHORITY\SYSTEM Computer: HERMES Description: Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: MSExchangeSA Event Category: General Event ID: 1005 Date: 11/8/2009 Time: 4:22:00 PM User: N/A Computer: HERMES Description: Unexpected error No authority could be contacted for authentication. ID no: 80090311 Microsoft Exchange System Attendant occurred. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. However after i get these errors i then get the info that the nic driver as initiated. I'm thinking there it's trying to load evertyhing before the nic has connectivity. It's running on a hp dl380 server. Any help would be greatly appreciated I can contact all dc once logged in, the nic is setup with the correct values and dns (we don't use wins) and DNS has all the entries correct.

For the first error i think you are guessing it correctly on the NIC (http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23632138.html). how ever the third one (SA service), i think thats not very normal.1. Can you put SP2 or atleast roll up 9 for the exchange server.2. Try the steps from http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/b34abbaa-1b36-43df-811b-d6b7472453bdRaj

Hi, I agree with you that it can be caused by the network issue. Please try the steps provided by Raj first: fix the nic driver issue, install latest updates, disable the SNP. If the issue persists, I suggest you use the bootpause registry key to delay the startup of Exchange Server and test the issue again. Please refer to method 3 of the following KB article: http://support.microsoft.com/kb/940845 Thanks, Elvis