Exchange Server Not Functioning...

Here is the situation.

I have two servers.
The first server acts as a web server / 2003 exchange front-end.
The second server acts as the 2003 exchange server.

I can get the first server to startt all the services that exchange requires, and start pop3.

on the second server, I can not get the services to start.

I get the following errors in my event viewer.

I also get an error when I Try to create a new user, or mount the mailbox sahres. This error is related to a DC issue.

Does anyone know how I could troubleshoot these issues to get things working again?


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Have you cheked to make sure the services are set to start automatically? You should also check to make sure the LOGON service is started as well. Look in the eventviewer and provide specific events that are taking place so we can get a better idea of what is happening.

jacobbeckleyAuthor Commented:
The servcies are set to start automatically and when I start them I get errors. Below is a list of the errors from the eventviewer.

Event Type:      Error
Event Source:      MSExchangeTransport
Event Category:      Routing Engine/Service
Event ID:      929
Date:            7/6/2005
Time:            8:02:44 PM
User:            N/A
Computer:      BMEDIA-WEB
Failed in reading Connector's DS Info Process Id: 2884 Process location: "C:\Program Files\Exchsrvr\bin\store.exe" ConnectorDN: CN=Internet Mail SMTP Connector (BMEDIA-WEB),CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=BMedia,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=bmedia-online,DC=com Hr:80040920 Attribute:[]

For more information, see Help and Support Center at

Event Type:      Error
Event Source:      NTDS General
Event Category:      Global Catalog
Event ID:      1126
Date:            7/6/2005
Time:            6:29:30 PM
Computer:      BMEDIA-WEB
Active Directory was unable to establish a connection with the global catalog.
Additional Data
Error value:
1355 The specified domain either does not exist or could not be contacted.
Internal ID:
User Action:
Make sure a global catalog is available in the forest, and is reachable from this domain controller.  You may use the nltest utility to diagnose this problem.

For more information, see Help and Support Center at

Event Type:      Error
Event Source:      NTDS Replication
Event Category:      Replication
Event ID:      1864
Date:            7/6/2005
Time:            6:14:30 PM
Computer:      BMEDIA-WEB
This is the replication status for the following directory partition on the local domain controller.
Directory partition:
The local domain controller has not recently received replication information from a number of domain controllers.   The count of domain controllers is shown, divided into the following intervals.
More than 24 hours:
More than a week:
More than one month:
More than two months:
More than a tombstone lifetime:
Tombstone lifetime (days):
 Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
To identify the domain controllers by name, install the support tools included on the installation  CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest.   The command is "repadmin /showvector /latency <partition-dn>".

For more information, see Help and Support Center at

jacobbeckleyAuthor Commented:
I also get these errors when I try to start the Exchange Services on the exchange server.

The Microsoft Exchange System Attendant service on Local Computer started and then stopped.  Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

can you check the dns on that machine and make sure that it is poiting to an internal DNS server and not an external DNS server?

network connection>local area connection>properties>internet protocol (tcp/ip)>properties>use the following DNS servers (should both be internal addresses)

jacobbeckleyAuthor Commented:
The main server has the ip address of

The DNS on this server is set for standard primary. All of the a hosts and mx records point to

Then on the second server. The dns is also set for Standard primary but with the ip addresses pointing to the correct boxes within the network.

One issue I am having is that I can't change the DNS from standard primary to active directory integrated on the exchange server.

check what dns settings the 2nd server is using though.

it isnt in DNS server settings, it is in network connections

make sure it is using itself (or better yet another domain controller) as the DNS server

jacobbeckleyAuthor Commented:
The second server uses itself as the dns provider in it's network tcp/ip settings.

Any other ideas?

this is from ( and has been modified to make it easier to use

See for a hotfix applicable to Microsoft Windows 2000.
See and the link to "Microsoft event 1126 from source Active Directory" for more details on this problem.

Make sure a global catalog is available in the forest, and is reachable from this domain controller. You may use the Nltest utility to diagnose this problem.

After applying MS security bulletin MS04-011 on a DC that is a catalog server, that domain controller after reboot does not register itself as a Global Catalog server in DNS. Hence, other domain controllers that are not global catalog servers may get this error. A hotfix is available from Microsoft see

I had this problem trying to promote a replicated AD machine to be the "first" DC after my original DC went bye-bye. After switching all the roles and getting the active database to rebuild, I was left with this error. Here is the fix I used:
1. Go to Administrative Tools, Sites and Services.
2. Browse the tree, Sites -> Default first name -> Servers -> your DC -> NTDS settings.
3. Right click NTDS settings and choose properties.
4. Check the box Global Catalog.
5. Reboot.

I got this kind of errors after I changed the DC with a new one, namely after I promoted the new DC, demoted the old DC (which remained a GC). To fix the problem I modified the Service Location Record (SRV) for _gc in DNS that it would point to the new DC.

This error will also appear if you have removed the Global Catalog tick in NTDS Settings located under "AD Sites and Services".

Check your domain Controllers Local Policy User Rights Assignment to be sure that Exchange Enterprise Servers account is under Manage Auditing and security Log. If not add it or run Domain Prep from the Exchange 2000 CD again to fix all security issues. Then re-install Exchange service pack.

This can be caused by clocks on AD controllers being out of sync.

As the error says, verify the availability of the server hosting the Global Catalog (network, DNS, etc..) and if the Global Catalog is online.  See for more information.

Sometimes, certain applications may affect the functionality of the Global Catalog (Citrix, Surf Control, and others).

As per, this problem may occur if you have a damaged object. points to a connectivity problem between Exchange 2000 and the Global Catalog.

As per Microsoft, this behavior can occur if you lock the system partition and remove the Everyone group from various locations. See for more details and how to fix this.

If the error occurs on a Small Business Server, see

This event can also occur when the Netlogon service fails.

Ensure that the Netlogon service is running. This service must be running for the GC to "Advertise". Eliminate any errors that cause the Netlogon server to fail to start.  

there are quite a few paths to travel there, i think the fact that it cant contact your GC server is vital to solving this.  let me know if any of the above are applicable to you, and if they help at all (or change the problem in some other way)


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
glad you got it sorted

what specifically from my post helped you?

this information may greatly help the next person that has the same problem

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.