• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 301
  • Last Modified:

Replication Errors, Browser Errors, Don't know where to look.

We have two domain controllers, both Win2k3 SP2.
Users are complaining of slow network browsing. We are seeing lots of BROWSER errors in the System Log and NtFrs erros in File Replication Service log.
One domain controller has all the roles. They are both running DNS.
They can both ping eachother by name, so resolution appears to work. Nslookup on each server can resolve both servers.

So I'm looking for ideas one where to look. Here are excerpts of some of the logs:

The File Replication Service is having trouble enabling replication from OFFICESERVER to UPDATESERVER for c:\windows\sysvol\domain using the DNS name OFFICESERVER.ad.stephen.sevenways.org. FRS will keep retrying.
 Following are some of the reasons you would see this warning.

 [1] FRS can not correctly resolve the DNS name \\OFFICESERVER.ad.stephen.sevenways.org from this computer.
 [2] FRS is not running on \\OFFICESERVER.ad.stephen.sevenways.org.
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{8431EFE6-D218-46AF-AF19-0B67FE456DD7}. The backup browser is stopping.

The browser service was unable to retrieve a list of servers from the browser master \\OFFICESERVER on the network \Device\NetBT_Tcpip_{8431EFE6-D218-46AF-AF19-0B67FE456DD7}.
 Browser master: \\OFFICESERVER
 Network: \Device\NetBT_Tcpip_{8431EFE6-D218-46AF-AF19-0B67FE456DD7}
 This event may be caused by a temporary loss of network connectivity. If this message appears again, verify that the server is still connected to the network. The return code is in the Data text box.

  • 3
2 Solutions
First thing to check is DNS. Make sure all clients point to your internal DNS server - normally the domain controller - for their preferred DNS server. The DNS server (DC) should point to itself as DNS server. The alternate DNS server should be blank unless you have two or more internal DNS servers. These settings may be set in the static TCP/IP settings or may be set with DHCP options.

cogenttechAuthor Commented:
Both DCs are running DNS.
Both DCs have the Master DC set has their primary DNS server and the "backup" DC set their second DNS server.
We have the same settings in DHCP for all the clients.

The Master DC is also running WINS and both servers and all clients have it set as their WINS server as well.
cogenttechAuthor Commented:
Looking for some ideas on where to look here.
Is Netbios over TCPIP selected on the network bindings?
cogenttechAuthor Commented:
I appear to have resolved the problem with a combination of restoring the Sysvol and changing the order of NICs in Adapters and Bindings under Advanced in Network Control Panel.
I will split the points between the two people who responded with ideas.

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now