I have been spending a little more time on this. RPC Dump wouldnt run before and gave me an error (see earlier post). I now managed to get it working.
To summarize it all: Exchange 2003 SP2 throws an error in the Eventlog (Event ID 9176) which seems to indicate that the GC it is contacting doesnt support the NSPI service. According to the information in that same Event ID this would be due to the fact that the DC had not been rebooted after it having been made a GC. I ran RPC Dump on the GC in question and have enclosed the output (I took everything but NSP). By the way, this GC is a root DC which is on W2K. Is NSP listed the way it should be? Cheers and thanks, Victor -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe Sent: zaterdag 23 september 2006 2:52 To: [email protected] Subject: RE: RE: [ActiveDir] OT: Exchange in environment - reboot necessary after a DC has been made a GC What is the rev of the DC? Using RPC Dump do you see "MS NT Directory NSP Interface" interfaces listed? joe -- O'Reilly Active Directory Third Edition - http://www.joeware.net/win/ad3e.htm -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of victor- [EMAIL PROTECTED] Sent: Friday, September 22, 2006 11:07 AM To: [email protected] Subject: Re: RE: [ActiveDir] OT: Exchange in environment - reboot necessary after a DC has been made a GC Yeah, I thought so, thanks for the info. The damn thing is that Exchange still throws event 9176: Event ID 9176 from MSExchangeSA occurred 1 times (NSPI Proxy can contact Global Catalog "servername" but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients. Reboot "servernamerio" as soon as possible. ----- Oorspronkelijk bericht ----- Van: joe <[EMAIL PROTECTED]> Datum: vrijdag, september 22, 2006 4:38 pm Onderwerp: RE: [ActiveDir] OT: Exchange in environment - reboot necessary after a DC has been made a GC > This is no longer necessary with current revs of AD. It was necessary > previously to get the NSPI functionality to fire up. Now it does that > automagically. > > > -- > O'Reilly Active Directory Third Edition - > http://www.joeware.net/win/ad3e.htm > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of victor- > [EMAIL PROTECTED]: Friday, September 22, 2006 10:31 AM > To: [email protected] > Subject: [ActiveDir] OT: Exchange in environment - reboot necessary > after a DC has been made a GC > > A question came up wether or not a reboot is really necessary after a > DC has been made GC and Exchange would need to use this GC. > > I have worked in a pretty large environment (at least to my standards > :- )). Where DC's did not get rebooted afther having been made GC's. > The > AD admins simply waited until event 1119 appeared. > > I have read the following article which indicates a reboot is > necessary if you have Exchange in the environment. > > http://support.microsoft.com/kb/304403/ > > But is this really still necessary with Exchange 2003 SP2 and Windows > 2003 SP1? > > Cheers, > > > Victor > List info : http://www.activedir.org/List.aspx > List FAQ : http://www.activedir.org/ListFAQ.aspx > List archive: http://www.activedir.org/ml/threads.aspx > > List info : http://www.activedir.org/List.aspx > List FAQ : http://www.activedir.org/ListFAQ.aspx > List archive: http://www.activedir.org/ml/threads.aspx > List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ml/threads.aspx List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ml/threads.aspx
Querying Endpoint Mapper Database... 62 registered endpoints found. ProtSeq:ncacn_http Endpoint:1029 NetOpt: Annotation:MS NT Directory NSP Interface IsListening:NOT_PINGED StringBinding:ncacn_http:10.34.0.4[1029] UUID:f5cc5a18-4264-101a-8c59-08002b2f8426 ComTimeOutValue:RPC_C_BINDING_MIN_TIMEOUT VersMajor 56 VersMinor 0 ProtSeq:ncadg_ip_udp Endpoint:1028 NetOpt: Annotation:MS NT Directory NSP Interface IsListening:NOT_PINGED StringBinding:ncadg_ip_udp:10.34.0.4[1028] UUID:f5cc5a18-4264-101a-8c59-08002b2f8426 ComTimeOutValue:RPC_C_BINDING_MIN_TIMEOUT VersMajor 56 VersMinor 0 ProtSeq:ncalrpc Endpoint:NTDS_LPC NetOpt: Annotation:MS NT Directory NSP Interface IsListening:NOT_PINGED StringBinding:ncalrpc:[NTDS_LPC] UUID:f5cc5a18-4264-101a-8c59-08002b2f8426 ComTimeOutValue:RPC_C_BINDING_MIN_TIMEOUT VersMajor 56 VersMinor 0 ProtSeq:ncalrpc Endpoint:LRPC00000190.00000001 NetOpt: Annotation:MS NT Directory NSP Interface IsListening:NOT_PINGED StringBinding:ncalrpc:[LRPC00000190.00000001] UUID:f5cc5a18-4264-101a-8c59-08002b2f8426 ComTimeOutValue:RPC_C_BINDING_MIN_TIMEOUT VersMajor 56 VersMinor 0 ProtSeq:ncacn_np Endpoint:\pipe\WMIEP_190 NetOpt: Annotation:MS NT Directory NSP Interface IsListening:NOT_PINGED StringBinding:ncacn_np:\\\\servername[\\pipe\\WMIEP_190] UUID:f5cc5a18-4264-101a-8c59-08002b2f8426 ComTimeOutValue:RPC_C_BINDING_MIN_TIMEOUT VersMajor 56 VersMinor 0 ProtSeq:ncacn_np Endpoint:\PIPE\lsass NetOpt: Annotation:MS NT Directory NSP Interface IsListening:NOT_PINGED StringBinding:ncacn_np:\\\\servername[\\PIPE\\lsass] UUID:f5cc5a18-4264-101a-8c59-08002b2f8426 ComTimeOutValue:RPC_C_BINDING_MIN_TIMEOUT VersMajor 56 VersMinor 0 ProtSeq:ncacn_ip_tcp Endpoint:1026 NetOpt: Annotation:MS NT Directory NSP Interface IsListening:NOT_PINGED StringBinding:ncacn_ip_tcp:10.34.0.4[1026] UUID:f5cc5a18-4264-101a-8c59-08002b2f8426 ComTimeOutValue:RPC_C_BINDING_MIN_TIMEOUT VersMajor 56 VersMinor 0 C:\temp\rpcdump.exe completed sucessfully after 1 seconds
