We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

MSExchangeDSAccess Event ID 2103

Rizzen1
Rizzen1 asked
on
Medium Priority
1,808 Views
Last Modified: 2013-06-04
My exchange server 2003 installation has been a bit quirky.  I seem to get this error alot.  Exchange 2003 is installed on a member server.  I also have a Primary domain controller (PDC1) and a seperate backup domain controller (BDC1).  This error states that "All Global Catlog servers in use are not responding" PDC1@Domain.local in reference to MAD.exe

However some successful App Log entries for MSExchangeDSAccess report that "DSAcces will user servers from the follwing list: BDC1@domain.local Cofiguration Domain controller is set to: BDC1@domain.local. in reference to inetinfo.exe

Should it be refrencing my Backup domain controller at all?  Also I continue to get the error entry every 20mins referencing the same Mad.exe program.  What have I done wrong here. It seems to be causing Outlook some issues.  When users open outlook they get the "requesting information" message for a longtime before outlook opens.  Then sometimes it opens really quickly.

Note: All installation steps (/forestprep and /domainprep) were done on the Exchange member server.

Thanks in advance

Comment
Watch Question

Expert of the Year 2007
Expert of the Year 2006

Commented:
Exchange will use all the domain controllers that it finds - plus it will use the first one that responds.

The main reason for the the error that you are receiving is DNS configuration errors. Ensure that you only have domain controllers listed in the DNS configuration of all servers.

Simon.

Author

Commented:
All of my servers are configured to point to the PDC for DNS
Expert of the Year 2007
Expert of the Year 2006

Commented:
Just that domain controller? (remember that there are no PDC and BDC in active directory - all domain controllers are equal with just some holding roles).
Is that machine a global catalog? Do you have any other global catalog domain controllers? You should ideally have two as the GC/DCs handle logins.

Any replication errors in the event logs of the domain controllers?

Simon.

Author

Commented:
Sometimes it works well somtimes it doesnt, I am begining to think it is a problem with my switch.  When I ping the server i occasionally get no reply, then othertimes I do.
Expert of the Year 2007
Expert of the Year 2006

Commented:
It may not be the switch, could be the NIC or the network cable. If you are getting intermittent traffic then you need to investigate. Exchange needs almost constant access to the domain controller.

Simon.

Author

Commented:
Well I have finally fixed the problem.  My servers have two NIC cards each.  They are Broadcom NetXtreme's.  It appears these network cards dont work very well if theres more than one in the same box (at least with Windows).  The packets would get confused as to wich NIC they were to go in and out from. Simply unplugging one network card from each box solved the problem.  Just to make sure I dont have any more problems I also set the BDC to host the Global catalog as well.
PAQed with points refunded (500)

Computer101
EE Admin

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
This is no Solution
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.