Blank domain list when browsing network

1. Load Services.msc, and make sure following services are running:
a) Remote Procedure Call (RPC). Use by client for MS networks.
b) Server
c) Workstation. Both used for MS networks and File/print sharing
d) TCP/IP Netbios helper.
e) Computer Browser. Allow to see other computers on network.
f) Network connections
g) DHCP Client - not necessary if you don't use DHCP

You can also reset TCP/IP by this command:
netsh winsock reset.

The RPC service was not running on the Domain controller- I started it and set it to automatic.  Everything else was already going.  I ran the netsh and have to reboot to complete the change- which I am doing in an hour anyway for some updates.

I will check it out after I reboot.  Once again I've done this only on the DC, haven't checked a workstation yet.  As for the workstations- I usually disable the Computer Browser service to prevent elections being forced between them and the server.  Is that going to cause an issue?

Not to jump to another subject, but...
Disabling that service was the suggested fix from MS for the Master Browser conflict- I know there is a reg hack that tells a PC it's not the Master Browser that I could do instead, but I'm suprised MS would recommend something that was going to cause another issue.

OK, I'm not really THAT suprised.

Still blank when browsing after the reboot.

even after u started the computer browser service?

That is correct.  I just brought the server back up and checked- still completely empty.  One of the other servers (on the same domain) actually told me the <domain name> was not available when attempting to browse it via Symantec Anti-Virus's Remote Client install.  I checked just to be sure and the Computer Browser service DID start on it's own after the reboot.  Still nothing suspicisious in the Event Logs either.

Any other ideas?

Do you still need assistance?

Yes, please.  I have tried everything I can think of, but the issue still exists.

Ports 137 and 138 are not being restricted (that I know of) anywhere on the subnet.  I already have WINS running, and all clients pick that IP up from the DHCP list.  Last week I made the suggested registry changes from the article to make the DC the Domain Master Browser and the Terminal  Server a Backup Master Browser.  Both can now see the domain list.

I am going to apply the same change to a few workstations this week and if it works I will deploy the change via Group Policy (and award ChiefIT the points).

Sounds like a good plan. Let me see if I can find the GPO settings. It may end up being a logon script, as I don't know of a domain policy on the GP admin templates.

You may not have to do anything with the clients. If they are rebooted, they will do another broadcast/election to look for available master browsers. Now that you defined the Domain Master Browser and Backup Browser, the clients might populate the browse list if they see the browsers you editted. Give it a little bit of time, maybe a day or so, and see if the list populates itself.

One thing I would be concerned about is the prior to your configuration settings. If a computer was elected a master browser, then it may conflict with the newly defined domain master browser and backup browser. If so, you may see a partial list of computers on some clients, or sometimes clients will disapear from the list of computers.

I looked up the ability to use a GPO and force a master browser. I couldn't find one. So, I went back to the article I shared with you and this is what it said.

""\HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \Browser \Parameters

Unless the computer is configured as the preferred master browser, the parameter entry will always be False or No. There is no user interface for making these changes; the registry must be modified.""

So, I am leaning towards the belief that a GPO doesn't exist for this.

Setting up the clients to play nice may be a little more tricky. So, let's see how they perform with the defined domain master browser and backup browser before we play with the clients. Maybe all you need to do is reboot the client.

I will be at the site tomorrow and I"ll check the two computers I set up to be backup browser to see if they have a full list and then check other stations.

If both do, I'm done.
If only the Backup Browsers do,  I'll add a registry entry to the logon script for a few days.
If neither--- back to the drawing board!!!

If you read these sections of the article,

Browse Service Across Multiple Workgroups and Domains
Browse Service Across a Wide Area Network (WAN)
The Windows Internet Name Service (WINS)


http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx?mfr=true

It sounds like you have a firm understanding between a Domain master browser, Master Browser, and Backup browser now. It also sounds like the Domain master browser and Backup browsers are populating their list. So, it sounds like things are going your way and you will probably be pleasently suprised.


Please note: You will need a master browser and backup browser per domain and per workgroup.

Please note: I am anticipating a problem that may not exists. You may not need to prevent clients from becoming a master browser once you define the master browsers on all domains and workgroups. If there is a conflict between elected browsers and manually forced browsers, you will see stuff like clients disappearing in the browse list from time to time. If so, you will need to edit the registry key to prevent clients from becoming a master browser.  

I know this is stating the obviouse. Sorry in advance for being thurough.
When applying the logon script to edit the registry key to "FALSE" don't apply that logon script to any domain master browsers, master browsers, and backup browsers you create on each domain or workgroup. This key prevents them from participating in elections.

\HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \Browser \Parameters (->>set to FALSE for anything you don't want to be a master browser).

Hope all goes well.

Still having troubles.  Tried two workstations, both of which I had added the TRUE setting.  One was blank, the other gave me the "you may not have permissions" error.  I checked and the Computer Browser service wasn't running on either of them (not sure why that is, there are no policies preventing it that I know of).  I started the service on both.  The workstation with the error now has what appears to be a full list (yay!).  The other still blank.  I'm going to let it sit a bit and see if it merely needs to build it's list, then take it from there.  If it works, I guess I'll make a policy to start the Computer Browser service on everyone and see what that does.

Disabled browser services explains a lot. The computer you are still having problems with may have Netbios disabled on the NIC. Netbios is necessary to populate the browse list. All you have to do is go to the advaced settings of the TCP/IP properties and elect the default of Netbios over TCP/IP. If Netbios is disabled, you should see problems with DNS as well on that 'puter.

I think it's time to add on to your knowledge. You seem to be understanding the browse service very well. There are some good command line utilities for troubleshooting the browser service. One is browstat. This article will give you the syntax and some examples of how to use Browstat.

http://support.microsoft.com/kb/188305

No, Netbios was enabled.  So far every PC I've checked has a blank list, with the exception of the one.  Hopefully it's a result of the Browser service being stopped.  I'll start a bunch of them...
...and see what happens by next week's visit.

I'll read over the article you sent in the mean time.

Brief update- I was on site yesterday.  While I didn't have time to address this issue, I did check a few of the PCs that I had modified and the list is still blank.

Back to reviewing the issues:

The browser and RPC services:
The browser and RPC services were stopped on some computers, in not all computers. (did we get those up and going)

Netbios and the WINS/WAN configuration:
Netbios will not propogate over Network Address translation, firewalls and other port blocking. So, WINS will have to be enabled on both client and server. DETAILS, are provided on this link:
http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx?mfr=true

NOTE: Furthermore, depending on your security, ISA needs rules to allow WINS I believe. You may want to check your firewall settings and make sure you are not blocking WINS resolution.

Preventing Browser conflicts and elections over multiple domains:
To prevent from having a browser conflict and multiple elections forced on your domains and workgroups, each workgroup or domain should have its own master browser. Then, the registry keys should be set to the appropriate level, (example: domain master browser, backup browser, master browser) DETAILS on setting up a browser per domain and editting the appropriate registry keys are located on this article:
http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx?mfr=true

Further troubleshooting the browser:
The browser may still have problems in some locations or certain PCs. After a reboot, if these problems occur, try using the BROWSTAT command at the command prompt to troubleshoot the browser. DETAILS will be located on this article:  http://support.microsoft.com/kb/188305

I think we are close to a resolution. I hope you hang in there with us.

My Domain Controller is set to "TRUE" or "YES" for IsDomainMaster, IsDomainMasterBrowser, and MaintainServerList

I have manually changed some workstations to "YES" or "TRUE" for MaintainServerList and "NO" or "FALSE" for the others

There are no internal firwalls and nothing on my external that should be a problem.

The RPC service has been re-enabled and is running HOWEVER- the PCs that are failing to browse do not have the Computer Browser service running (although it is set to Automatic).  Apparantly it wasn't turning back on after a reboot.  I've re-enabled it and we'll see if that fixes it, if so I'll have to make sure it's starting each time.

I was working on a similar post and came up with a very defined solution to your problem. Elections from the clients may have been made to computers that don't have netbios records to support your client. Some of this information might be redundant and I think you are at step 3 already:

This will be run on the remaining troubled client machines after the browser service is enabled and you still have problems with it.  

On the client:
After you download the xp sp2 support tools or 2003 server support tools, run Browstat Status at the command prompt. That will tell you what your client computer elected as its master browser and has a connection to for netbios translation. (HERE'S YOUR PROBLEM) If that elected master browser doesn't have WINS, NetBUI or DNS to make some sort of netbios translation to a HOST or LMHOST records, you will not be able to manage your client or see this client computer in My Network Places because the netbios record of some sort will not exist for that client. So, nothing can make the netbios translation to that client for the browser.

NOTE very important::: You have to decide what to do on your combined network. You want a master browser (and shoot for a backup browser) per domain, workgroup and subnet. If going across a subnet, different domains, or across NAT, you will have to use the WINS/WAN configuration of the browser service. Then, you want a DOMAIN MASTER that will be the centerpoint for the master browser service.

Step 1: (Disabling elected master browsers that can't do nebios translation)
What you will want to do is go to elected master browser, that you saw on the trouble client browstat, and either disable that machine from becoming the master browser or give it the means to do a netbios translation with the domain master browser. ->Most likely, prevent it from being a master browser.
(NOTE: You will find that registry edits on this Browser thread.
http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx?mfr=true
Example for disabling it from being a master browser: Isdomainmaster=false, and Participates as a master browser = false)


Step 2) Defining domain master and backup master browsers:
Then, go to your PDC holder of roles, that I assume does your DNS translation and maybe WINS, and force it to be the master browser. Example: Set this to ISdomainMaster=True. Also set Participates as a browser=True.
Then make sure your backup browser can also do netbios translation. If you have a BDC, then IsDomainMaster=false and Participates as master browser=true.

Step 3: (Fixing the Netbios connections)
Now go back to each troubled client's command prompt and type NBTstat -RR a couple times. This should sort out cached netbios connections to that old, elected master browser. As the result of NBTstat -RR, you should see a number of NBT connections refreshed and fixed.

To check your work, type browstat status. You should see your PDC role holder as a browser and your back up browser also as a browser. If you removed the ability for the elected master to become a master browser, you might see that netbios connection dissapear.
 
This article was very helpful in figuring this out. So, maybe this won't confuse you like I probably did:
http://support.microsoft.com/kb/188305

Thanks to you both for your input- this was actually resolved once the registry entries on the workstation were put into place- we didn't know for sure until yesterday when we had the same problem with another client which prevented us from installing a program (You had to browse for the license server).  End result- setting all workstations to not be the Master Browser but changing the Maintain Browse list in the Registry from Auto to True did the trick.