Hi!
The server (W2003) that holds our AD master roles is dieing. I moved these roles off that machine to a new one and AD reports all roles are now being hosted by the new server however exchange (2003) keeps looking at the old server for its GC. The new server is a GC.
I've tried forcing exchange to use this new GC through directory access and although exchange accepts this server as a GC, this shows up in event log on the exchange server:
Process MAD.EXE (PID=2956). All Global Catalog Servers in use are not responding:
...and if course we can't authenticate.
How do I get Exchange to use this new GC?
Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Here's a 2080 log enevt entry:
Process EMSMTA.EXE (PID=4240). DSAccess has discovered the following
servers with the following characteristics:
(Server name | Roles | Reachability | Synchronized | GC capable | PDC
| SACL right | Critical Data | Netlogon | OS Version)
In-site:
newGC.mydomain.com CDG 7 7 1 0 0 1 7 1
oldgc.mydomain.com CD- 6 7 0 0 1 1 7 1
mail.mydomain.com CD- 6 6 0 0 1 1 6 1
terminalb.mydomain.com CD- 6 7 0 0 0 1 7 1
The new DC has no SACL rights.
(???)
Are you sure you transfered all of the FSMO roles? The PDC role is not showing in event 2080.
Here's the roles and the consoles need to transfer the roles:
Schema Master - from schema management MMC.
Domain Naming Master - from domains and trusts MMC
RID Master - from ADU&C MMC
Infrastructure Master - from ADU&C MMC
PDC Emulator - from ADU&C MMC
I am curious to know if this has been resolved yet as we have the same situation. We wanted to ensure that we had redundant DC's in our environment - we have 2 DC's both with GC's on them. The roles have been all switched to the second DC, made the changes to Direcotry Access. If I reboot the original DC, Exchange starts throwing the same kind of errors your are receiving about not being able to contact the Global Catalogue, etc. As soon as the old DC finishes loading the errors go away and the Exchange Server is happy again.
Just to add a bit of info, does this perhaps have something to do with re-running the Exchange /domainprep process? I also noted that another message i receive "Event ID 2080" provides certain DC characteristics and on the new DC the SACL Right has a value of "1" while the older DC shows the SACL Right as a value of "0".
In talking to some other experts, they feel the issue we are having sounds like a DNS issue, but I don't know what to check to ensure it is not DNS related. Both of these DC's are DNS Servers as well. The Exchange Server settings point to both DNS Servers so I don't think that is the issue.
Any help in figuring this out would be much appreciated as this one has had me stumped for quite some time now. Thanks,
"I am curious to know if this has been resolved yet as we have the same situation. "
I eventually got the Exchange Server to look at itself and it's working ok but because of the trust it's locked into this configuration. We have no choice but to re-build the Exchange server. Our network has a series of irreversable problems with AD, Echange and DNS and we're tearing it down to kill the trust and re-building it from scratch on partially new hardware.
We were able to solve our issue by running "Domain Prep" and "Forest Prep" on our Exchange Server. What I think happened to us was that our second GC server was not yet a GC when we originally installed Exchange Server (which would have been the last time Domain Prep and Forest Prep would have been run). What this did was it changed the "SACL Right" value to a "0" from a "1". It then matched the older GC server. We are now able to take down the original GC and our Exchange Server does not hiccup any longer. Hallalujah!!!
Business Accounts
Answer for Membership
by: PakaPosted on 2008-03-02 at 07:31:31ID: 21026276
Have you rebooted the GC after checking the make this a Global Catalog Server checkmark? This also might be a DNS issue - was the dying server a DNS server? Do you have another DNS server available? Is Exchange pointed at the new DNS server?