We help IT Professionals succeed at work.

Exchange 2003 FE will not star excchange services

scusack
scusack asked
on
System Attendant does not want to seem to start. All dependencies are running.  
It seems like it cannot connect to a GC or DC based on the errors. Can ping the GC server without anny issues.

How can I manually change the GC the exchange 2003 server looks to via the registry. There are lots of GC's in the network and I want to point it to one specifically.

Here are some event viewer errors. Also when I try to click on the server is ESM the program hangs.

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2114
Date:            6/13/2010
Time:            9:13:40 PM
User:            N/A
Computer:      NOCSV10407
Description:
Process MAD.EXE (PID=4836). Topology Discovery failed, error 0x80040a02.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type:      Information
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2069
Date:            6/13/2010
Time:            9:13:40 PM
User:            N/A
Computer:      NOCSV10407
Description:
Process MAD.EXE (PID=4836).  DSAccess could not find any Global Catalog servers in neither the local site 'DMZ' nor the following sites:  
 

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type:      Information
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2077
Date:            6/13/2010
Time:            9:13:40 PM
User:            N/A
Computer:      NOCSV10407
Description:
Process MAD.EXE (PID=4836).  DSAccess could not find any Domain Controller servers in neither the local site 'DMZ' nor the following sites:  
 

For more information, click http://www.microsoft.com/contentredirect.asp.





Comment
Watch Question

Manually Pointing the Exchange Server to a DC/GC is not recommended.
How ever if you want to force it then
Open the ESM -> Expand Servers -> Properties of your FE Server -> Directory Service Tab.

Uncheck the Option -> Automatically Discover and Click on Add and Choose the DC, GC & ConfigDC you want.

Author

Commented:
The problem is we cannot click on the properties of the server in ESM as it hangs.

Working with policytest now to see if all DC/GC have the proper rights.



Ok when you go to the properties of the FE Server -> On the General tab do you see any error on the Log File Directory.
From the command prompt -> Run a dcdiag /s:
See if there are any errors in that.

Check the Network Binding Order.
Make sure that the Active NIC Card is on top of the Network Binding.

Author

Commented:
Kicked the DNS servers and rebooting the FE to see if that helps. Binding and dns on the server are OK.
cool. If that does not help try with the nltest /dsgetsite command to see if it is pointing to the right Site.
Also try nltest /dsgetdc:

Try with nslookup and see if all the DC's names are getting resolved.

Author

Commented:
All exchange services are working now. Internal email is working however, we still cannot send email outside. It seems that the messages are getting stuck at the SMTP server though it can resolve the public domain names. Any idea?
What about the Mail Flow from Internet coming to your Domain. Do you get Mails from Internet?

Author

Commented:
After all the services have started again we were able to send just few emails outside. It did work when we send emails from outside as well. But now it's totally screwed. I thought we cannot just send emails outside.

For info:
Our front end server is in the DMZ.
We have 3 back end servers in the enterprise network.
Current routing group master is one of the back end servers. Should I change the routing group master to the front end server since it is responsible for routing messages?
Yes since the Front End Server is Internet Facing from the DMZ, the Front End Server will process the Mails for the Internet and then Send them to the Back End Servers.