I might point out that in that KB there should be a link to tlist for download. You know, just to make sure it's on the machine in question. 
I suspect there's also not a lot of reason to read the event log first when netstat -ao would be able to tell you which servers (2003 expected) the Exchange server is talking to on GC ports. Piping it to something like FIND or GREP would further reduce the information domain.
 
Contact PSS for interpretation? Can't there be a DCR to make that better and the user more self-sufficient? :)
 
BGINFO is not something to rely on for Exchange troubleshooting.  I know it was assumed in the post, but BGINFO while a great and useful tool, is going to talk about the session information which may or may not be the same as what Exchange is using.  It would be coincidence if it was the same. Mostly.
 
-ajm


On 5/25/06, Steve Linehan <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> The following method will show you what GCs Exchange has discovered and believes are viable servers: http://support.microsoft.com/kb/316300/en-us .  While this will not tell you the exact GC Exchange is using, it could be using multiple GCs, it will help you narrow down the list.  You could then use a network capture or look at netstat –ao, assuming Windows 2003, which will list the current connections and the process ID that owns them.   If this still does not help you track it down you can enable Regtrace and have PSS help interpret the output.
>
>  
>
> Thanks,
>
>  
>
> -Steve
>
>  
>
>
>
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Stu Packett
> Sent: Thursday, May 25, 2006 10:09 PM
>
> To: [email protected]
> Subject: RE: [ActiveDir] How To Determine What GC a Server is Using?
>
>
>
>
> To: [email protected]
> Subject: RE: [ActiveDir] How To Determine What GC a Server is Using?
>
>
>
>
>
>  
>
> I got 'mad.exe' results, but not those specific port numbers.  Would the port number be different for all servers?
>
>  
> ________________________________

>
> From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Tony Murray
> Sent: Thursday, May 25, 2006 7:25 PM
> To: [email protected]
> Subject: RE: [ActiveDir] How To Determine What GC a Server is Using?
>
> How about "netstat –b" ?  Look for mad.exe connecting to port 3268 (or 3269 for SSL).
>
>  
>
> Tony
>
>  
>
> ________________________________

>
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Stu Packett
> Sent: Friday, 26 May 2006 1:13 p.m.
> To: [email protected]
> Subject: RE: [ActiveDir] How To Determine What GC a Server is Using?
>
>  
>
> Isn't the 'Login Server' the same as the Domain Controller?  If I do a 'set.exe' from a command prompt, I get the same info as "LOGONSERVER".  What I need specifically, is the Global Catalog server (unless I'm going about this incorrectly).
>
>  
> ________________________________

>
> From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Blair, James
> Sent: Thursday, May 25, 2006 5:51 PM
> To: [email protected]
> Subject: RE: [ActiveDir] How To Determine What GC a Server is Using?
>
> Stu,
>
>  
>
> Download and configure BGINFO and check to "Login Server" attribute...
>
>  
>
> http://www.sysinternals.com/Utilities/BgInfo.html
>
> James Blair     
>
>
>  
>
>  
> ________________________________

>
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Stu Packett
> Sent: Friday, 26 May 2006 10:34 AM
> To: [email protected]
> Subject: [ActiveDir] How To Determine What GC a Server is Using?
>
> We have a strange situation here where one of our Exchange servers keeps getting 8026 and 2102 errors.  This causes our users on that Exchange server to temporarily lose connection to the Exchange server.  Also, my Unity server just failed over to the secondary Unity server at exactly the same time my last Exchange 8026 error happened.  This leads me to believe I may have a problem with a global catalog server.  Is there a way to determine what GC each server is using?
>
> Thanks in advance. This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.
>
>

 

Reply via email to