Discussion Locked

No Domain Logon across Router

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

Here's the scenario:
NT 4.0 SP5
Cisco 1720 router across
T1 line
Can ping IPs and server name across router qand T1.
Attempting domain logon across T1 and router and receive: No domain server or server unavailable.

18 replies

by jclaverie

Do you use address translation with the router ?
This could stop acquitments beetween client and domain controller.

by Former member

No, no address translation. Thanks.

by zk

You didn't specify what os the client is running.

Your router is blocking the broadcast. I assume you don't have WINS.

In this case, you need lmhosts file.

On 95/98 it is in C:\Windows folder. On NT it is C:\WINNT\system32\drivers\etc. If there is a file called LMHOSTS.SAM don't use it. Make a copy and Name it "LMHOSTS" without extension.

Then add these two lines and save it. Make sure ".txt" isn't appended when you're saving.

200.1.1.1 #PRE #DOM:Domain_name

200.1.1.1 "DOMAIN NAME \0x1C" #PRE

It is CRITICAL in line two to have 20 spaces between quotes. Also, try to follow the case in the example in LMHOSTS.SAM file. That is "mydomain^^^^^^^\0x1c". ^ is space.

Then do a reboot. It should be fine.

Read more in detail on MS website. The article numbers are Q163949, Q150800, Q119493.

by Former member

Read the comments I wrote at the top. I'm sorry I didn't fully explain the BDC->PDC relationship.

by Former member

I do have a WINS server located on the PDC. I should have specified --> The BDC at the remote site cannot find the PDC across the router (Eviewer) but I can ping the PDCs computer name and IP address from the BDC. Tracert resolves the netbios namecorrectly, but times out after the router on both sides. I can telnet into the remote router and BDC's router.

by Former member

The scenaio I wrote earlier was incorrect. Instead of No Domain Logon, clients DO logon, just into the BDC. The problem is actually between the PDC -->router-->BDC. Everyone authenticates from the remote site with the BDC. However, the BDC cannot see the PDC.

by Former member

Point value changed by question poster.

by tony.colgrove

I would create a LMHOSTS file for the DC's each with the address of the other and #PRE so its in the cache.
Make sure the routers are not blocking the required ports for the DC to replicate. I know RPC is 135, and NBT uses some others. If your connection is on a PVC then you should be able to open em all up, if any are in place.

by Former member

The question was auto-closed by TechRepublic

by Former member

Here's an update:
-BDC can ping PDC both IP and netbios name
-Netbios name cache on BDC correctly loads LMHOSTS file. No LMHOSTS on PDC.
-Telnet works both ways across routers.
-Tracert dies both ways at the routers.

by allan

You don't mention anything about DNS servers ? Do you have any ?
Make sure the BDC has the ip address of the PDC in it's WINS configuration.
Make sure the default gateway on the PDC and BDC are set to the respective router.
Make sure the routers are not blocking the neeeded protocols and ports.
Has this setup ever worked or is this a new install ?

by Former member

The question was auto-closed by TechRepublic

by ananthan15

if u have wins server on PDC which is installed at on site and from other site ,client will logon to PDC...u have to do the following steps
1. mention win server ip address on client network configuration
2. provide domain name.
3. very important is gateway address in client network configuration...

ANAND.

by Former member

The question was auto-closed by TechRepublic

by frank.peeters

The suggestion in some previous answers to specify the PDC's IP address in the BDC's WINS client configuration, usually does the trick.

Alternatively you could force the netbios name into the BDC's cache by including the following line in the BDC's LMHOSTS file:

[PDC IP address] "domainname \0x1B" #PRE

Make sure you put enough spaces after the domainname so that the backslash is exactly at the 16th position of the string.

Reload the netbios cache with a 'Nbtstat -R' command. A subsequent 'Nbtstat -c' should show the 1B domain registration with a time to live of -1 (forever).

Of course you should prefer WINS over LMHOSTS. If the PDC's IP address changes, you have to remember changing LMHOSTS files.

by frank.peeters

Also make sure the PDC points to itself in the WINS server properties in TCP/IP configuration. This will make sure the 1B domain name is properly registered.

by Former member

The question was auto-closed by TechRepublic

by Former member

This question was auto closed due to inactivity

This discussion is closed to new replies.