XP Network Browse Problems
From: SA (anonymous_at_discussions.microsoft.com)
Date: 09/18/04
- Next message: Joao Brozoski: "IIS Snap in."
- Previous message: Michael Pardee: "***VERY DIFFICULT SOLUTION NEEDED***"
- Next in thread: Michael Pardee: "XP Network Browse Problems"
- Reply: Michael Pardee: "XP Network Browse Problems"
- Reply: Chuck: "Re: XP Network Browse Problems"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 18 Sep 2004 06:07:12 -0700
I'll try to be succinct about an issue that recently
flaired with and XP SP2 box.
Sympoms:
Win2000 Server, and workstations combined with one Xp pro
client. Peer-to-Peer Network. The Network was working
just fine for aeons, (even after updating to SP2).
a.) If the Win2000 machines boot first, they can all see
each other across the network; including accessing shares
etc. When the Xp machine boots, it can't "see" the other
boxes in the network neighborhood, and when it trys to
access either the Workgroup, or "Computers Close To Me" ,
it receives the message "[Workgroup] is not accessible,
you might not have permission...The list of servers for
this workgroup is unavailable."
>From any of the Win2K boxes the WinXp box shows in the
network neighborhood, but when trying to access it, it of
course "\\machine is not accessble."
I see Browser errors in the Event Viewer on the Xp box,
i.e. 8021, the "browser was unable to retrieve a list of
servers" and 8032 "The browser service has failed to
retrieve the backup list too many times."
When I run the utility Browstat with a status switch the
error is:
"Browsing is not active on the domain, Master name can not
be determined from GetAdapterStatus"
b.) If the WinXp box boots first, the exact reverse is
true, i.e. it can see the other boxes in its net
neighborhood, but can't access them and the Win2K machines
get the Workgroup is unavailable error.
Apparent Problem:
>From these two scenarios, what appears to happen is that
if the Win2K machines (any of them, Server or Workstation)
boot first and are therefore the "master browser" then
everything is fine between all the 2K machines, however
the Xp machine doesn't communicate with the master browser
effectively.
Conversely if the WinXp machine boots first and it is the
initial "master browser" then it hoses the entire network
because it doesn't communicate its browse list.
Fix attempts:
Things that have been reviewed or tried:
a.) The browser, server, workstation and other services
are up and running; restarts don't impact things
b.) The Xp firewall is set to allow the file and print
sharing on the local subnet. I've disabled the Xp2
firewall and there's no change in behavior.
c.) I've used a scanner across the local net and the XP
machine does have port 137 and 139 open on the local subnet
d.) Can ping all the machines back and forth so its not a
cable or router problem
e.) The XP' boxes NetBios setting is set to use the defaut
setting under the WINS tab on the TCP/IP settings for the
adapter and changing it to "Enable NetBios over TCP/IP"
changes nothing, the problem still occurs.
f.) There's no VPN or set up.
g.) Uninstall XP SP2, and no change
h.) Uninstalled and reinstalled client for MS networks and
the file and print sharing services on the Xp box; no
change.
There's got to be some reg setting that's gotten hosed,
what I don't know.
Help!
Steve Arbaugh
- Next message: Joao Brozoski: "IIS Snap in."
- Previous message: Michael Pardee: "***VERY DIFFICULT SOLUTION NEEDED***"
- Next in thread: Michael Pardee: "XP Network Browse Problems"
- Reply: Michael Pardee: "XP Network Browse Problems"
- Reply: Chuck: "Re: XP Network Browse Problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
