--------------------
>From: "Byron" <(E-Mail Removed)>
>Subject: Can't see WinXP systems when browsing 2003 domain
>Date: Sun, 4 Apr 2004 10:05:44 +0200
>Lines: 8
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <(E-Mail Removed)>
>Newsgroups: microsoft.public.windows.server.networking
>NNTP-Posting-Host: pD9E0C801.dip.t-dialin.net 217.224.200.1
>Path: cpmsftngxa06.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTN GXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.ph x.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.networking:11232
>X-Tomcat-NG: microsoft.public.windows.server.networking
>
>When I browse the 2003 domain I can see the two DCs and two standalone
>servers, but none of the WindowsXP Pro systems even though there are shared
>resources on them.
>
>I know there is a simple solution to this, but I'm under the gun and can't
>find any references to the issue. Can someone help me out here?
>
>
>
Byron,
Domain Browsing is a broadcast based system that is affected by network topology. Are the XP clients in a separate Broadcast Domain than the
Domain Controllers and Servers? That is to say are the clients on a separate network than the DC's or at least a separate VLAN, etc?
Can the clients see all of the client and not the servers from their brows list? The trick here is to figure out who can see what and that will tell us what is
happening. Can the server access the shared resource from START --> RUN \\Computername\Sharename?
I have included several articles below to help you troubleshoot this issue. You will also want to take a look at the BROWSTAT utility that is part of the
support tools for XP and for 2003.
188305 Troubleshooting the Microsoft Computer Browser Service
http://support.microsoft.com/?id=188305
120151 Browsing a Wide Area Network with WINS
http://support.microsoft.com/?id=120151
T.J. Campana [MSFT]
Microsoft EPS Networking
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.