Windows Forum

Ask something
Discussion Locked

synchronize remote BDC

0 helpful
3 replies

by kma11

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a PDC in this office and a BDC at a remote site connected by a T1. Whenever I try to synch the BDC to the PDC I get the following message in the event viewer:

The event ID is 5719, with a description of "No windows NT domain controller is available for domain XXX. (This event is expected and can be ignored when booting with the 'no net' hardware profile). The following error occurred: There are currently no logon servers available to service the logon request."

I am not booting with the 'no net' hardware profile. Also users on the remote end are able to access e-mail and there seem to be no other connectivity issues. New users cannot log on to the network from that office because the controllers are not synched up. Allsynchronization in this office works fine. It seems to be WINS related but I haven't been able to come up with the answer. Any insight would be greatly appreciated.
TIA,
Kurt

3 replies

by dlw6

Hi Kurt,

It's been a year since I had to solve one like this, but you're on the right track. Do the following from your BDC (or over the network if you want):

Using Notepad, open a file called "lmhosts.sam" under %systemroot%\system32\drivers\etc (where %systemroot% means C:\WinNT or whereever your NT is installed.

This is a sample LMHOSTS file (hence the SAM extension). It contains detailed instructions for making LMHOSTS files, which you should read, but here's the short version:
Make a text file called LMHOSTS (no file extension!) and put it in the same location described above on the BDC. It should have one line, and that line will read:

X.X.X.X PDCNAME #PRE #DOM:DOMAINNAME

where x.x.x.x is the PDC's IP address, PDCNAME is its UNC name, and DOMAINNAME is the Domain name.

There is also a setting under Network properties you have to fix. Go to Protocols, TCP/IP Properties, and the WINS tab and check the Enable LMHOSTS box.

When you reboot the BDC, it will preload that entry into its Hosts table. Test it by trying to ping the PDC by name from the BDC:

Ping PDCNAME

If the ping goes through, or attempts to do so, then your BDC knows how to contact the PDC and your problem should go away.

Goodluck,
Don

This discussion is closed to new replies.