I’m having some issues. We have 3 exchange servers in our environment. Were running Exchange 2007 SP1 Rollup 9 on all 3. All of our clients are using outlook 2007 to connect. I recently had to reboot one of the exchange servers because backups were failing. Before the reboot, I ran the latest security updates from Microsoft just to get that up to date since I was rebooting it. I figured I’ll update the other 2 at a different time. Don’t know the exact timeframe but it seems to coincide with the reboot that I’m having problems with users on the server I rebooted. Any user on that server now has to type in their password when they first open up outlook. That wasn’t happening before the reboot. Autodiscover cannot resolve user names from anyone on that exchange system. It gives the error “The name could not be resolved. The connection to Microsoft Exchange is unavailable, outlook must be online or connected to complete this action”. I can’t resolve by host name or IP. The way around this is I point it to either of the other 2 exchange servers and then it can resolve the name. Once the profile loads up. They can’t load up the Global Address List. The same error is given: “The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.” They do receive emails and they are connected to exchange. I was thinking it was a DNS problem. I’m able to ping the exchange server in question from our domain controller and vice versa. On the exchange server, I ran a “Ipconfig /registerdns” . Still does the same thing. The other 2 exchange systems are working just fine. No other changes have been made besides updating to the latest patches and rebooting. Anyone have any suggestions on what else I can try?

Is the System Attendant service running on the server?

WOW!!! Sometimes we make things harder than they need to be. That solved the issue. It was setup to start automatically but it never did. Thank you so much! I should have looked there first.