Re: Need help interpretting browstat output



On Sat, 14 May 2005 16:24:34 -0400, Robert Solomon <rob@xxxxxxxxxx> wrote:

>I read some of the posts here and noted that my problem matched the
>browstat problem. So I d/l and ran it. But I'm having trouble
>interpretting the output. Any help would be appreciated.
>
>Thanks,
>Rob
>
>>From computer called P4
>Status for domain WORKGROUP on transport \Device\NetBT_Tcpip_{C6C41128-
>7959-44E1-BBF2-17DC8B5483BB}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>
>
>
>
>
>>From computer called P4a
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfIn
>{63982BF5-2485-4E30-BD46-EF1E45A12AF3}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfIn
>{28372BD7-DDCE-4755-8860-27646E896A8E}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfOut
>{32BDA32A-8F21-4773-A8D3-1C078ACD6A22}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfOut
>{575255A6-EF41-48DC-A33E-8456B33C18B5}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfOut
>{A9223FFF-CCFC-4D53-82D3-B087C6F25723}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfIn
>{8D94D3F9-2E66-4B46-9FA0-8EA2B885A74C}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\NetBT_Tcpip_{E2F6AACA-
>BB91-4433-B3A1-0282670D6395}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>
>
>
>
>>From computer called P4b
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfIn
>{C0259003-75E4-4457-B489-2E4B36CEA324}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfOut
>{9EB94CAA-AF03-4E48-9A61-197B2F9DD995}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfOut
>{CBA4ED03-F4BF-4BB3-9041-FEE401373A57}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfOut
>{8E3E976C-8919-4DE0-803E-CD020000C8A9}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfIn
>{C8C2F496-218B-4C76-936A-F27BA115E8F8}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfIn
>{62C1E184-650F-4105-8998-C7367CB18F7C}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>Status for domain WORKGROUP on transport \Device\Nbf_{3BB0BA97-1EF4-
>41EF-BF84-7E97668D36A5}
> Browsing is active on domain.
> Master browser name is: <some garbage characters here>
>Could not connect to registry, error = 53 Unable to determine
>build of browser master: 53
> Unable to determine server information for browser master: 123
> 1 backup servers retrieved from master <garbage characters>
>\\P4B
> Unable to retrieve server list from <garbage characters>: 2351
>Status for domain WORKGROUP on transport \Device\NetBT_Tcpip_{3BB0BA97-
>1EF4-41EF-BF84-7E97668D36A5}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.

Rob,

Which computer is running the browser?
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>

Are you running XP Home, XP Pro, a combination, other? All of this makes a
difference in the results in browstat.

What protocols are you running on your LAN? Windows networking is built around
TCP/IP, and uses NetBIOS Over TCP/IP as an interface to file and printer
sharing.

Installation of IPX/SPX, NetBEUI, or Ndis serves as a workaround when the
problem is related to the TCP/IP on the LAN (maybe a firewall misconfigured).
If you have physical connectivity issues, or if file sharing is not set up
properly on one or more computers, adding IPX/SPX or NetBEUI will not help. And
if you don't setup IPX/SPX or NetBEUI properly, it will simply hamper diagnosing
the actual problem.

If there's a problem with TCP/IP, or with NBT, IPX/SPX or NetBEUI may provide a
workaround. But it will also add needless complexity, and may cause long term
stability problems.

If the problem being experienced is caused by authentication / authorisation,
IPX/SPX or NetBEUI won't resolve anything.

Fix the problem. Don't add to it.

Here are a couple good articles on the subject (remember, WinXP is WinNT V5.1):
<http://support.microsoft.com/?id=128233>
<http://www.networkmagazine.com/article/NMG20000517S0009>
<http://www.ultratech-llc.com/BrainWave/TechDocs/Resolution.html>

To start, you need to eliminate excess protocols from the list of items under
Local Area Connection Properties. You only need the following items in the
list:
Client for Microsoft Networks
File and Printer Sharing For Microsoft Networks
QoS Packet Scheduler (optional)
Internet Protocol (TCP/IP)

Then, make sure that NetBIOS Over TCP/IP is enabled on each computer. Local
Area Connection - Properties - TCP/IP - Properties - Advanced - WINS - Enable
NetBIOS over TCP/IP.

You specifically don't require IPX/SPX, NetBEUI, or Ndis.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.
.



Relevant Pages


Loading