Re: Need help interpretting browstat output

>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.

All computers posted are running WinXP Pro SP2
All computers only have tcp/ip and use NetBIOS over tcp/ip. No other
protocols are installed.

I went thru the steps you suggest to confirm this. The links you post
are far too technical for me. For example, the following passage seems
to be relevant to my problem, but it describes an option I cannot find.
That is, it says to "go into the TCP/IP properties in the Control Panel
and enable "Use DNS for Windows Resolution". I see stuff about DNS
suffixes and the like, but I am afraid that I'll make my problem works
if I muck w/ these settings.

Is there anything else I can try?

Thanks again,
Rob




The Need For Name Resolution

To ensure successful communication on a network, your systems need to be
able to associate a name with an IP (or other relevant network number)
so that users do not need to memorize the numeric identifier, such as a
TCP/IP address. Proper name resolution is essential for fast network
communication, and if it is not configured correctly, your network will
be slow, and your network users will be unhappy.

On Windows networks running TCP/IP, the following options exist for name
resolution:
Host Name Resolution
HOSTS ............... Static
DNS ................... Dynamic
NetBIOS Name Resolution
LMHOSTS ........... Static
WINS ................. Dynamic
DNS ................... Dynamic (not the default for NT4 or earlier)
HOSTS ............... Static (with NT/2000/XP/2003)
Although commonly advocated, there is no need to run NETBEUI on your
Windows network. It is a chatty, non-routable broadcast protocol, and
only useful on very small networks, or if you don't want to connect to
the Internet at all. Instead, you can rely on NetBIOS support, tunneled
over another protocol such as TCP/IP. All versions of 32-bit Windows
support NetBIOS over TCP/IP.

If you want to use DNS for resolving NetBIOS names on versions of
Windows prior to Windows 2000, you must go into the TCP/IP properties in
the Control Panel and enable "Use DNS for Windows Resolution". With
2000, XP and 2003, Windows has an increased reliance on DNS, whether on
a peer network or through Active Directory.
If you are unable to get Windows 95/98/ME machines to talk to systems in
the Windows NT-family without installing NetBEUI, then it is very likely
that you have not setup NetBIOS Name Resolution for your client systems.
Also, remember that NetBIOS traffic should always be confined to your
internal network ONLY. There is no need to allow NetBIOS traffic to
traverse the Internet or another public network without the benefit of a
VPN.

.

Relevant Pages

  • Re: File sharing breaks while already in use (XP HOME Differences)
    ... Consider a home network with two PCs connected to a linksys router. ... Windows 2000 PRO ... After rebooting QUEENIE, the NET VIEW command works okay. ... But a name resolution error generally isn't chronic. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Network and XP
    ... >In 'My Network Places' viewing workgroup computers displays the four PCs ... >currently powered up on the LAN, ... Make sure that NetBIOS over TCP/IP is enabled on all computers, ... TCP/IP and NBT Configuration Parameters for Windows XP ...
    (microsoft.public.windowsxp.network_web)
  • Re: netBIOS Alert
    ... That'll fix your NetBIOS ... >it a bit differently than NT and 98, which are the only Windows ... >>I checked in Network and I have no tab that says NetBios. ... the probe could be a port scan. ...
    (comp.security.firewalls)
  • Re: RAS Error 720
    ... make sure both RAS server and client have the correct protocol setup. ... establishing logical names and sessions on the network for Windows NT/9x/ME. ... > Anyone know of a resolution before I go for a system restore? ...
    (microsoft.public.windowsxp.network_web)
  • WIn 98 browsing to Windows 2000 Server
    ... Netbios over TCP/IP is enabled on the server...any other ... >Which network protocols do you have on your network? ... >>I am having trouble browsing to a Windows 2000 Server ...
    (microsoft.public.security)