Exchange error 8231 and can not mail enable accounts
I had a client conatct me with a 2000 domain and has a 2003 server hosting the exchange 2003. He has a DNS server that was a GC but was demoted to a member server and now this is happening. I have since promoted another 2000 server to be a GC and rebooted exchange but still same error and still cna not mail enable a email account my plan is to dcpromo and promote taht server that he demoted and make it a GC reboot exchange and see if that resolves I think he was having this or some issues and that is why he demoted in teh first place thought?jason eberhardt
January 28th, 2010 7:32am

Strange , in case you have other DC in the same AD site. some how i feel , this can be a DNS issue. Run IPCONFIG /ALL on the exchange and see if the pri. and sec. DNS are point to correct DC's.Run a DCDIAG and see if you can get some hints from there. Also run a exbpa from exchange and check the result. Also on the exchange server properties in EMC, check the DSACCESS tab and see if it showing the correct GC's and DCs.Raj
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2010 8:20am

Hi Jason, At the Initial Installation of Exchange Server, the Recipient update service (RUS) will choose an active Global Catalog as default domain controller for Email stamping. So When you demote the old GC make sure RUS is pointing to Existing Global Catalog. You may use the following steps. Plan: 1. Make sure the old Global Catalog (GC) is completely removed from active directory using metadata cleanup. 2. Goto Exchange system manager -> Recipients -> Recipient Update Service 3. You will find Enterprise and Domain RUS listed 4. Right click on them -> Goto Properites -> Change the OLD GC to Existing GC Using Browse button. 5. Make sure you change for both RUS. 6. Apply Changes. 7. Make sure your exchange server will resolve New GC without any issues. 8. Use nslookup in command prompt, Make sure you can resolve your new Global catalog NETBIOS Name and FQDN. 9. If possible, Restart the Server 10. Right click on the RUS and Update them Ref to: How to work with the Exchange Recipient Update Service http://support.microsoft.com/kb/319065 Exchange Recipient Update Service does not stamp proxy addresses in Exchange 2000 Server and in Exchange Server 2003 http://support.microsoft.com/kb/286356 Creating Exchange Recipient Update Service instances for remote domains http://support.microsoft.com/kb/275294 All the Best :) Sathish Kumar Elango | MCSE 2003 & MCSA Messaging | http://msexchangehelp.wordpress.com
January 28th, 2010 8:31am

what are the steps to check DSACCESS is this in exchange system manager?jason eberhardt
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2010 5:58pm

how do i make sure it is cleaned up with the metadata cleanp, shoudl I not just dcpropo the demoted server back to a GC fro teh imediate need, so he can get some users working, and then make a bigger plan for restructure? i already checked teh RUS both of them and they are pointing to the current DC/GCjason eberhardt
January 28th, 2010 5:59pm

Right click on the server in exchange system manager, properties and then DSACCESS tab.No need to check the metadata at this point. even if this is not clean , exchange should work any ways.Raj
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2010 6:06pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics