Hi All I have complicated problem is two of my branch offices Exchange Servers. I have Exchange Server in HQ and 4 Exchange Servers in 4 Branches. Every Branch has its own Exchange Server that serves its users. I had some problems in the HQ Exchange and I restored some storage groups, and move some mailboxes between the storage groups, now I have the following problems: - Users within 2 branches can't send internal emails between them and to the other users in the HQ Exchange Servers. - Users can receive external mails (Outside the Company). - All messages are freeze in the Directory (Waiting for Directory Lookup) I noticed the following error always happens: Event Type: Error Event Source: MSExchangeSA Event Category: General Event ID: 9153 Date: 3/29/2010 Time: 5:12:13 PM User: N/A Computer: SRV-44 Description: Microsoft Exchange System Attendant reported an error '0xc0072141' when setting DS notification. For more information, click http://www.microsoft.com/contentredirect.asp. I have also errors: 9035-6004-9035 The Branch office has its own running GC and DC, Replications works without any problems between sites. Dcdiag returned no errors. Please help me

On Mon, 29 Mar 2010 18:47:04 +0000, Alaaay wrote:>I have complicated problem is two of my branch offices Exchange Servers. This might sound kinda lame, but have you tried rebooting those twomachines?---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

error "0xc0072141" means ERROR_DS_INVALID_GROUP_TYPE . I think there is an issue with Exchange and DS communication try to restart system attendant service and make sure Exchange is able to contact GC. as you said they are stuck at (Waiting for Directory Lookup) i think they can not be catagorized. Please check the dns issues and run dcdiag for any possible issues with AD.nAraYaN

hi Guys Thanks for your reply .... I solved it again ... I put hte Exchagne Server as GC. This is not best practice as I think and sure I didn't solve the GC problem but i m working now. Regards

Thats wat the problem was due to exchange unable to communicate with GC.nAraYaN