Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Master Browser errors on Win2k Server

Status
Not open for further replies.
Sep 25, 2002
4
0
0
US
Here is the setup.
I have (2) Windows 2000 Servers
The first is setup as a DC with DNS and Active Directory
The second is also setup as a DC with the replicated AD from the Main server.
DNS is NOT installed on the second DC but does point to the Main DC in the IP Config settings.
There are two problems.
1. I'm receiving an error message in Event Viewer stating the following: "The browser was unable to retrieve a list of servers from the browse master on the network \Device\NetBT_Tcpip....."
2. The second DC gets very sluggish every so often. This problem seems to point to Network traffic as it's not all that sluggish when working on the server, only when accessing shared files and folders on the server. Does this have to do with replicating AD? It looks like its replicating the default Once per Hour.

Any information will be greatly appreciated.
Thanks in Advance!!
 
some questions:

1) Is either of these servers multihomed?
2) What happens (from the second DC) if you do an NSLOOKUP?
3) What protocols are you running (if any) besides TCP/IP?
4) Are you running WINS, and/or have you enabled NetBIOS name resolution?
 
The servers have one NIC a piece
When I do NSLOOKUP the default server comes up as the first DC (the one without the problem) and the IP address of the first DC
I'm also running NETBEUI on this server to attach to an old printserver
I'm running WINS on the main DC to support several Win98 machines in the office
I don't have WINS in the IPConfiguration of the second DC enabled
 
If you're not in Native Mode, to relieve the browser issues may I suggest enabling WINS on the second DC. Actually, it might even help with your second issue. Aside from that, make sure that you can resolve local names from the second DC via that NSLOOKUP prompt, just in case.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top