C
Chuck
Chuck, are you still watching?
This is getting interesting again.
Right after rebooting the Master Browser (PRINCE this time)
Firewall comes up. I have verified that, with or without the firewall,
you need that mapped drive, and it needs to be active. Otherwise you
get the Error 53 on Registry fetch from other workgroup machines.
This message is interesting in another way. Reboot starts the firewall.
I know I need to wait for the completion of one or more of the 12
minute browser process cycles before BROWSTAT results get consistent.
I can't seem to get rid of this message:
"Unable to retrieve server list from PRINCE: 64" until I shut down the
Kerio Firewall. (I will do some testing with Zone Alarm tomorrow).
I have also noticed that often, after 2 or three of the 12 minute
browser process cycles, that message may go away, anyway. I would love
to know what that is all about.
I also notice, without a Firewall, if I break the mapped drive link, a
few seconds later, BROWSTAT (From remote workgroup (KING-DADDY) still
gives all good results. ...but wait a minute or two, and the message:
"Unable to retrieve server list from PRINCE: 64"
message returns. I expected that. What surprises me is the:
"Master browser is running build 2195."
is present instead of the error 53 for the registry fetch.
Without the mapped drive, how can he fetch the registry data for browser
build without the link? But can't get the server list? Maybe the build
list is considered not so dynamic, but the server list is dynamic?
Still here, Carl.
The firewall is probably affecting the browser results. Browstat only reports
what the browser service sees.
I wish you would not use tinyurl. I can't keep track of what you're
referencing. Here's my "bible" about the browser.
<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
The confusion that you're expressing is that the browser uses SMBs (Server
Message Blocks) to communicate thru the LAN. Some SMBs are broadcast (point to
multipoint), others are individually addressed (point to point). Browser
elections (and thus knowledge of who is the master browser) uses broadcast SMBs.
Browstat sends point to point queries to the master browser, and thus requires
name resolution, and remote registry access.
You also need to know about SMBs hosted over NetBIOS (NetBT) vs SMBs hosted
directly (over TCP).
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279