Re: Help with long term network problem
- From: Chuck <none@xxxxxxxxxxx>
- Date: Thu, 06 Apr 2006 19:12:07 -0700
On 6 Apr 2006 16:27:15 -0700, "Gallon_Jug" <batsncats@xxxxxxxxxx> wrote:
Browstat status for DATA now
Status for domain WCSBZ on transport
\Device\NetBT_Tcpip_{1F02A786-7D73-4DC3-8F1B-3E88A6152BD3}
Browsing is active on domain.
Master name cannot be determined from GetAdapterStatus. Using
\\NEOBAT
Could not connect to registry, error = 5
Unable to determine build of browser master: 5
Unable to determine server information for browser master: 5
1 backup servers retrieved from master NEOBAT
\\NEOBAT
There are 4 servers in domain WCSBZ on transport
\Device\NetBT_Tcpip_{1F02A786-7D73-4DC3-8F1B-3E88A6152BD3}
There are 2 domains in domain WCSBZ on transport
\Device\NetBT_Tcpip_{1F02A786-7D73-4DC3-8F1B-3E88A6152BD3}
This is result of Dell-8400 Browstat status
Status for domain WCSBZ on transport
\Device\NetBT_Tcpip_{D36A89D0-B62B-4C28-8BFC-35C5C6B66222}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.
Again for Dell-8400
Windows IP Configuration
Host Name . . . . . . . . . . . . : Dell8400
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit Controller
Physical Address. . . . . . . . . : 00-11-11-3D-F2-29
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.10
DNS Servers . . . . . . . . . . . : 66.82.4.8
66.82.4.12
NEOBAT again
Status for domain WCSBZ on transport
\Device\NetBT_Tcpip_{CF0813A7-220D-429B-A2DA-8FC2566D4BB8}
Browsing is active on domain.
Master browser name is: NEOBAT
Master browser is running build 2600
1 backup servers retrieved from master NEOBAT
\\NEOBAT
There are 4 servers in domain WCSBZ on transport
\Device\NetBT_Tcpip_{CF0813A7-220D-429B-A2DA-8FC2566D4BB8}
There are 2 domains in domain WCSBZ on transport
\Device\NetBT_Tcpip_{CF0813A7-220D-429B-A2DA-8FC2566D4BB8}
Notebook
Windows IP Configuration
Host Name . . . . . . . . . . . . : Dell_D510
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless
2200BG Network Connection
Physical Address. . . . . . . . . : 00-13-CE-11-52-93
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.10
DNS Servers . . . . . . . . . . . : 66.82.4.8
66.82.4.12
Notebook Browstat status
Status for domain WCSBZ on transport
\Device\NetBT_Tcpip_{BAF7C207-B703-4D2A-9B58-97D3DF561B0F}
Browsing is active on domain.
Master name cannot be determined from GetAdapterStatus. Using
\\NEOBAT
Could not connect to registry, error = 53 Unable to determine
build of browser master: 53
Unable to determine server information for browser master: 53
1 backup servers retrieved from master NEOBAT
\\NEOBAT
Unable to retrieve server list from NEOBAT: 53
Bruce,
This is going to be fun. If you can take it that way, we can get started. ;)
From your sample of diagnostics, I can see a couple significant symptoms:# Browstats for Data and Neobat acknowledge Neobat as the master browser.
# Browstats for Data and Neobat both note a segmented workgroup ("There are 2
domains in domain WCSBZ").
# Browstat for Dell_D510 acknowledges Neobat as the master browser, but gets the
"error = 53" when trying to access its registry.
# Browstat for Dell8400 acknowledges no master browser.
# IPConfig for Dell8400 and Dell_D510 shows no gratuitous protocols, and shows
both computers on subnet 192.168.0/24, as Data and Neobat previously shown.
Comparing with previous diagnostics,
# Browstat for Data previous showed "error = 53" on Neobat, as Dell_D510 does
now.
# Browstat for Neobat previously showed 3 servers and 1 domain, and now shows 4
servers and 2 domains.
Now then, you have several problems, maybe related.
# Name resolution: "error = 53". Are all computers set up as Node Type =
Broadcast?
# Browser advertisement: "There are 2 domains in domain WCSBZ".
# Server access: "Could not connect to registry, error = 5".
Are all computers running NetBT? That is, has NetBT been explicitly Enabled in
TCP/IP Properties - Advanced - WINS? If so, you are going to have to look at
your personal firewalls. And in your case, looking at them means un installing
them on each computer. Since you're behind a router, you're protected from the
Internet. A personal firewall is generally significant, when used on a LAN and
behind a router, to protect each computer from the other computers.
Since your file sharing has problems, you need to start with no personal
firewalls. And I don't mean disabling them, I mean un installing each personal
firewall, from each computer, very thoroughly. I can't stress how thoroughly.
If you half do this, and you don't solve at least some of the above problems,
what are you going to do next? We need to eliminate PIS as a possible problem.
Hoping that you read my browser article, I now show you the Microsoft NT Browser
article, which has a section on Microsoft TCP/IP and Name Resolution.
<http://www.microsoft.com/technet/archive/winntas/deploy/prodspecs/ntbrowse.mspx?mfr=true>
http://www.microsoft.com/technet/archive/winntas/deploy/prodspecs/ntbrowse.mspx?mfr=true
That's where you need to start, for background information. Both name
resolution and server advertisement uses NetBIOS Over TCP broadcasts. Something
on the various computers - probably a personal firewall - is blocking the
broadcast packets, and causing the problems. That is, if NetBT is ENABLED on
EACH computer.
And did Dell_D510 has Internet access when the browstat was performed? Lack of
connectivity, however brief, could be a problem too. That will give
inconsistent results. Always make sure that every computer is reliably
connected, when performing any diagnostics.
I'll let you get to work reading this now. Don't be too long.
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.
- Follow-Ups:
- Re: Help with long term network problem
- From: Gallon_Jug
- Re: Help with long term network problem
- From: Gallon_Jug
- Re: Help with long term network problem
- References:
- Re: Help with long term network problem
- From: Gallon_Jug
- Re: Help with long term network problem
- From: Chuck
- Re: Help with long term network problem
- From: Gallon_Jug
- Re: Help with long term network problem
- From: Chuck
- Re: Help with long term network problem
- From: Gallon_Jug
- Re: Help with long term network problem
- From: Chuck
- Re: Help with long term network problem
- From: Gallon_Jug
- Re: Help with long term network problem
- From: Chuck
- Re: Help with long term network problem
- From: Gallon_Jug
- Re: Help with long term network problem
- Prev by Date: Re: Win XP Networking
- Next by Date: Re: Help with long term network problem
- Previous by thread: Re: Help with long term network problem
- Next by thread: Re: Help with long term network problem
- Index(es):
Relevant Pages
|
Loading