BDC not on browse lists

If the other BDC is recognized, you may want to be sure this one is configured in the same manner. (i.e. protocols, etc.)

You said that TCP/IP is it's only protocol...
You need to have NetBEUI bound to the BDC's NIC or it will not show up in the Network Neighborhood.

Good Luck...

I know it's a dummy question to ask, but did you syncronize the domain, yet?

Another thing to try, is to delete any static entries for this server in WINS remove it from Server Manager and reboot the server.
This particular technique is called "Shooting in the dark"!
That's a tough one!

Good luck!

make sure NetBios Interface service is installed.

You do not need netbui for browsing.
The information in server manager is gathered from the browse list when the "show domain members only" and therefore the bdc is greyed out because the browse list does not know about it.
Browse list are replicated over time and whenever a server is rebooted it may have to replicate again but this one has been up so it is not the issue.
I would suggest checking the event log of the dc's to check for any browse issues. Another option if the hardware is close and there is nothing new on this bdc is to clone the existing BDC and change the name. It may be quicker than troubleshooting this problem.

I expect it has been prevented from appearing in the browse list. Try this command from the Command Prompt: Net Config server /?
See if it says Hidden:YES, if it does then issue this command: Net Config server /hidden:NO it will cost a reboot, butshould then appear in the Browse list. There is a way through the registry but I prefer using the command prompt.

Check this setting in the registry

Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\LanmanServer\Parameters
Name: Hidden
Data Type: DWORD
Value: 0 = disable 1=Enable

This should fix what you require. The BDC will require areboot after the change.

If you have WINS installed on both servers - PDC and BDC, you need to enter TCP address of WINS server installed on PDC. I have the same problem, and when I changed the address of WINS server my BDC became visible on browse list

1. If you have workgroups chuck them. All servers and workstations need to be in the domain only. (On NT, network, identification, "Domain", not "Workgroup" - on Windows 95/98 set "Workgroup" to the domain name).

2. Best to make your PDC alsoyour primary WINS server. On WINS servers set "primary" and "secondary" WINS address to the address of the server itself. On all others make sure you have both a primary and a secondary IP address filled in.

3. On the above, verify that the settings are correct on your 'problem' BDC and reboot.

Don't sweat the BDC not being "lit up" in server manager if you can fully administer it. But having it on the browselist is a "nice to have" for your users.

Look in Event Log - System for any 'Browser' entries, forcing reelection or inability to refresh the browselist from 'server x' on 'transport y'.

On all Windows95/98 mchines, in network properties, file and print sharing, disable browsing (Keeps PCs from trying to playbrowse master).

If you feel

browser is horibble just deal with it. if you know its there whats the difference