General discussion

Locked

No Domain Logon across Router

By Zakk ·
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.

This conversation is currently closed to new comments.

18 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

No Domain Logon across Router

by jclaverie In reply to No Domain Logon across Ro ...

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

Collapse -

No Domain Logon across Router

by Zakk In reply to No Domain Logon across Ro ...

No, no address translation. Thanks.

Collapse -

No Domain Logon across Router

by zk In reply to No Domain Logon across Ro ...

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 <tab> <PDC computer name> #PRE #DOM:Domain_name

200.1.1.1 <tab> "DOMAIN NAME \0x1C" <tab> #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.

Collapse -

No Domain Logon across Router

by Zakk In reply to No Domain Logon across Ro ...

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

Collapse -

No Domain Logon across Router

by Zakk In reply to No Domain Logon across Ro ...

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.

Collapse -

No Domain Logon across Router

by Zakk In reply to No Domain Logon across Ro ...

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.

Collapse -

No Domain Logon across Router

by Zakk In reply to No Domain Logon across Ro ...

Point value changed by question poster.

Collapse -

No Domain Logon across Router

by tony.colgrove In reply to No Domain Logon across Ro ...

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.

Collapse -

No Domain Logon across Router

by Zakk In reply to No Domain Logon across Ro ...

The question was auto-closed by TechRepublic

Collapse -

No Domain Logon across Router

by Zakk In reply to No Domain Logon across Ro ...

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.

Back to Windows Forum
18 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Operating Systems Forums