MarkMan
asked on
Master Browser anomaly
I have a Master Browser issue I’m trying to resolve. After the last set of MS Updates (June/06) one of my multi-homed DC’s suffered OS damage and the browse service was lost.
I have since reinstalled the NIC drivers (presently using single card), & WINS (was corrupted), then ran netdiag /fix and corrected anything noted, then purged all pertinent WINS/DNS records and made sure the controller records were gold. Next I ran Nbtstat -R, Nbtstat -RR, Ipconfig /flushdns, Ipconfig /registerdns. I then restarted NetLogon services, also stopped WINS and ran ““jetpack wins.mdb temp.mdb” then started WINS.
The Browser service now runs but Network Neighborhood browser shows clients that are not attached or even powered up. The browser splash is static.
I rebooted the DC and checked again but same issue.
Browstat status shows proper transport device\proto information.
Browstat dumpnet shows “Api call returned 50” instead of expected output. Which implies a binding issue.
I noticed DHCP (other DC) shows clients (that are not logged in, powered on, etc) as having active leases when they shouldn’t.
I see no relative events in the viewer of the Master Browser DC.
The other DC post the expected “The browser has forced an election on network \Device\NetBT_Tcpip_{47152
I’m guessing the graceful shutdown of the end stations was never received properly at the DC’s so DHCP and WINS are frozen for these clients.
I’ve restarted DHCP Client/Server on the DC without any progress.
I would appreciate any insight you might provide.
Thank you in advance for your time.
Mark
I have since reinstalled the NIC drivers (presently using single card), & WINS (was corrupted), then ran netdiag /fix and corrected anything noted, then purged all pertinent WINS/DNS records and made sure the controller records were gold. Next I ran Nbtstat -R, Nbtstat -RR, Ipconfig /flushdns, Ipconfig /registerdns. I then restarted NetLogon services, also stopped WINS and ran ““jetpack wins.mdb temp.mdb” then started WINS.
The Browser service now runs but Network Neighborhood browser shows clients that are not attached or even powered up. The browser splash is static.
I rebooted the DC and checked again but same issue.
Browstat status shows proper transport device\proto information.
Browstat dumpnet shows “Api call returned 50” instead of expected output. Which implies a binding issue.
I noticed DHCP (other DC) shows clients (that are not logged in, powered on, etc) as having active leases when they shouldn’t.
I see no relative events in the viewer of the Master Browser DC.
The other DC post the expected “The browser has forced an election on network \Device\NetBT_Tcpip_{47152
I’m guessing the graceful shutdown of the end stations was never received properly at the DC’s so DHCP and WINS are frozen for these clients.
I’ve restarted DHCP Client/Server on the DC without any progress.
I would appreciate any insight you might provide.
Thank you in advance for your time.
Mark
ASKER
I had done this already but gave it another try without success.
wasn't sure you mentioned you replaced the driver.
Check HKLM\System\CurrentControl
What do you have in IsDomainMaster? Should be "True"
What do you have in MaintainServerList? Should be "Auto"
Check HKLM\System\CurrentControl
What do you have in IsDomainMaster? Should be "True"
What do you have in MaintainServerList? Should be "Auto"
ASKER
What do you have in IsDomainMaster? Should be "True"
Prior to last reboot was True, Upon check was False, I changed back to True
What do you have in MaintainServerList? Should be "Auto"
Correct
Checked via Browstat Status both before and after Reg hack both stated this DC was Master Browser.
I'm afraid I have to wait to continue working on this as I'm on holiday until the 14th. I thank you for your reponses so far and look forward to working with you later.
Thank You
Prior to last reboot was True, Upon check was False, I changed back to True
What do you have in MaintainServerList? Should be "Auto"
Correct
Checked via Browstat Status both before and after Reg hack both stated this DC was Master Browser.
I'm afraid I have to wait to continue working on this as I'm on holiday until the 14th. I thank you for your reponses so far and look forward to working with you later.
Thank You
Have fun, ttyl
ASKER
OK I'm back in-house.
Checked this morning and the server stats for following are
IsDomainMaster "True"
MaintainServerList "Yes"
The other controller is as follows
IsDomainMaster "False"
MaintainServerList "Auto"
Browstat status shows proper post with exception to last line.
"Unable to retrieve server list from _____:64
Checked this morning and the server stats for following are
IsDomainMaster "True"
MaintainServerList "Yes"
The other controller is as follows
IsDomainMaster "False"
MaintainServerList "Auto"
Browstat status shows proper post with exception to last line.
"Unable to retrieve server list from _____:64
Back early? That can't be good. (:
Anyhow check out this link:
https://www.experts-exchange.com/questions/21555144/unable-to-retrieve-a-list-of-servers-from-the-browser-master.html
Anyhow check out this link:
https://www.experts-exchange.com/questions/21555144/unable-to-retrieve-a-list-of-servers-from-the-browser-master.html
ASKER
Yes I looked at Browstate but since nothing is missing it didn't pan out.
The issue (other than the "Unable to retrieve server list from _____:64") is that the Network Neighborhood info is static.
The only other item I've noticed is that DHCP shows a few IP's active that are not. WINS & DNS seem healthy.
The issue (other than the "Unable to retrieve server list from _____:64") is that the Network Neighborhood info is static.
The only other item I've noticed is that DHCP shows a few IP's active that are not. WINS & DNS seem healthy.
Is the TCP Netbios helper running on the DC?
ASKER
Yes on both of them
What are the outputs for the following:
nbtstat -a YourPDCe
nbtstat -a yourBDC
nbtstat -a YourPDCe
nbtstat -a yourBDC
ASKER
PDC
DALETH <00> UNIQUE
DALETH <20> UNIQUE
CAMELOT <00> GROUP
CAMELOT <1C> GROUP
DALETH <03> UNIQUE
MENSVR <03> UNIQUE
CAMELOT <1B> UNIQUE
CAMELOT <1E> GROUP
Bdc
ALEPH <00> UNIQUE
CAMELOT <1C> GROUP
CAMELOT <00> GROUP
ALEPH <20> UNIQUE
ALEPH <03> UNIQUE
CAMELOT <1E> GROUP
CAMELOT <1D> UNIQUE
..__MSBROWSE__.<01> GROUP
DALETH <00> UNIQUE
DALETH <20> UNIQUE
CAMELOT <00> GROUP
CAMELOT <1C> GROUP
DALETH <03> UNIQUE
MENSVR <03> UNIQUE
CAMELOT <1B> UNIQUE
CAMELOT <1E> GROUP
Bdc
ALEPH <00> UNIQUE
CAMELOT <1C> GROUP
CAMELOT <00> GROUP
ALEPH <20> UNIQUE
ALEPH <03> UNIQUE
CAMELOT <1E> GROUP
CAMELOT <1D> UNIQUE
..__MSBROWSE__.<01> GROUP
We're getting in deep here, but look in the registry of the bad server and look for the the NIC key:
The NICS will be located at
HKLM\SYSTEM\CurrentControl
(where {Adapter} equals the service name of the installed network card. This might be a guid) In your case from the the first message the guid would be {47152109-9B1D-4D46-95BD-9
You might want to take note to see if the old nic that you removed is still in here. I know sometimes when I have nic issues and delete Local Area Connection and it redetects it as Local Area Connection 2, it is because the first NIC is still in the registry at the above key. I usually axe the NICs from the registry as well as Computer Management Hidden then redetect. You mgith want to try that.
Now if the old NIC is still in there, it still might be bound to Netbios/NetBT. Look in the following keys:
HKLM\System\CurrentControl
HKLM\System\CurrentControl
Look at the Bind\Export\Route values. These might have your old NIC present and the Browser Service is bound to the old non present nic. you'll notice these values match your {Adapter} value from above.
Compare these settings between the two and you might find something.
The NICS will be located at
HKLM\SYSTEM\CurrentControl
(where {Adapter} equals the service name of the installed network card. This might be a guid) In your case from the the first message the guid would be {47152109-9B1D-4D46-95BD-9
You might want to take note to see if the old nic that you removed is still in here. I know sometimes when I have nic issues and delete Local Area Connection and it redetects it as Local Area Connection 2, it is because the first NIC is still in the registry at the above key. I usually axe the NICs from the registry as well as Computer Management Hidden then redetect. You mgith want to try that.
Now if the old NIC is still in there, it still might be bound to Netbios/NetBT. Look in the following keys:
HKLM\System\CurrentControl
HKLM\System\CurrentControl
Look at the Bind\Export\Route values. These might have your old NIC present and the Browser Service is bound to the old non present nic. you'll notice these values match your {Adapter} value from above.
Compare these settings between the two and you might find something.
ASKER
Thanks I will look into this.
I have gotten the splash from Network Neighborhood to change since the last email. I'll know in the morning once the clients gracefully power down tonight if the Browser is now dynamic.
I'll post you once I know if it's functioning properly, the Reg content, and the latest browser related problems.
I have gotten the splash from Network Neighborhood to change since the last email. I'll know in the morning once the clients gracefully power down tonight if the Browser is now dynamic.
I'll post you once I know if it's functioning properly, the Reg content, and the latest browser related problems.
ASKER
The Reg KLM\SYSTEM\CurrentControlS
Not much to see at HKLM\System\CurrentControl
So I guess Reg NIC is gold. How about the Computer Management Hidden then Redirect, you've got me on this one. I'll need more clues please.
Not much to see at HKLM\System\CurrentControl
So I guess Reg NIC is gold. How about the Computer Management Hidden then Redirect, you've got me on this one. I'll need more clues please.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You may have mentioned it previously, the updates damaged two other servers so I've been doing multiple threads, it probably was an oversight on my part.
I checked network neighborhood and it seems to be dynamic now. I just have a little Wins issue and "Ta Da!".
I can't believe I've never utilized the "show hidden" before, did reg hacks previously. Ok the NIC's are clean in device manager also.
I'll follow up shortly.
I checked network neighborhood and it seems to be dynamic now. I just have a little Wins issue and "Ta Da!".
I can't believe I've never utilized the "show hidden" before, did reg hacks previously. Ok the NIC's are clean in device manager also.
I'll follow up shortly.
ASKER
I think I've got it now.
Thanks for all your help.
Thanks for all your help.
So did things clear up on their own or did you find something?
ASKER
I had re-installed Wins on one of the servers, rebooted, tweaked Reg as per our notes.
This morning the browser seemed dynamic and the only remaining issue was a wins record (no master browser).
I changed reg to reflect PDC=Master browser, then purged all Wins records for both servers, rebooted both servers.
Now it seems happy, will know for sure in the morning.
Basically looking at what we did and what I did- I dismantled & re-installed Wins (kept partners off until list stabized), rmv'd & added NIC's, cleaned Dns, Wins, checked Dhcp, hacked Reg.
Sooooooooo
Nothing new, just kept doing and undoing until servers were happy.
This morning the browser seemed dynamic and the only remaining issue was a wins record (no master browser).
I changed reg to reflect PDC=Master browser, then purged all Wins records for both servers, rebooted both servers.
Now it seems happy, will know for sure in the morning.
Basically looking at what we did and what I did- I dismantled & re-installed Wins (kept partners off until list stabized), rmv'd & added NIC's, cleaned Dns, Wins, checked Dhcp, hacked Reg.
Sooooooooo
Nothing new, just kept doing and undoing until servers were happy.
What you could try is:
Delete the NICS in Device Manager.
Then do a redetect.
Sometimes this shakes things up enough to help Windows bind to everything properly again.