General discussion

Locked

Connect to Domain over a subnet

By Peter Bate ·
Hi there,

Just a quick question on NT domains.. I have tried to connect a PC to a domian that is on a different subnet (1 hop away) and the system is telling me that it can't find the domain controller.

I have set up an LMHOSTS file and can ping the PDC nicely.. But I can not add the machine to the domain. I have heard rumors that you can not do it, but I would like a second opinion. Is there any work-around for such an issue?

Thanks once again.

Peter

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Connect to Domain over a subnet

by Allen Wilkes In reply to Connect to Domain over a ...

Peter,
It can be done, we run several remote sites over ISDN & Leased lines, using the domain controllers at HQ.
I don't recall it causing to much hassle to set-up, the clients are using thier router as the gateway and each WINS, PDC, BDC, DNS & DHCP server have persistant routes set for the routers return address.
Have you tried creating the account in Server manager and then logging on?
Is the Domain controller specified as such in the LMHOSTS File?

Allen

Collapse -

Connect to Domain over a subnet

by Peter Bate In reply to Connect to Domain over a ...

Poster rated this answer

Collapse -

Connect to Domain over a subnet

by Ian Mclaws In reply to Connect to Domain over a ...

Hi Peter,
You don't mention if you are pinging the PDC using its IP address or its name. NT, when no WINS is configured, uses a broadcast to find it's DC for logon. This only works locally, but with a properly configured LMHOSTS file, it will definitely allow the client to "see" the domain controller. My suspicion is that the problem lies in your LMHOSTS. Here's some pointers:

1. Here is the entry for an LMHOSTS for your situation
X.X.X.X Servername #PRE #DOM:nameofdomain

syntax is x.x.x.x is the DC's address
Servername is your DCs NetBIOS name
#PRE causes the entry to load
into the NetBIOS name cache on boot
#DOM:x identifies that the entry
is a domain controller in the "x"
domain

NOTE: Use the tab key between the IP address, name, and the #PRE, then a space between the #PRE and the #DOM.

File must be saved (no extension, make sure you are viewing extensions of known file types!) in the %systemroot%\system32\drivers\etc folder as LMHOSTS

Good luck,

Ian

Collapse -

Connect to Domain over a subnet

by Peter Bate In reply to Connect to Domain over a ...

Poster rated this answer

Collapse -

Connect to Domain over a subnet

by jvohs In reply to Connect to Domain over a ...

If you can ping a domain controller, your in like flynn, as log as:
1. NetBIOS ports must not be blocked any where along the way, specifically ports 137 and 138 UDP for WINS, and 135-139 for the full range used by NetBIOS.
2. If you have a WINS server it should resolve the name as long as the DC registers with WINS, and the client queries WINS.
3. Test first with an lmhosts written according to Q180094 on the Microsoft Knowledge Base. This will allow for domain validation. The lmhosts mustcontain a 1b entry for the DC, and the spacing must be exact. On the client load the file into cache with the "nbtstat -R" command. Check cache with the "nbtstat -c" command, and you should see a <00>, <20>, and <03> for the domain controller name, and a <1b> for the domain name.

Now if you can't get in the link may contain a firewall or router that is blocking ports. Good luck!

Collapse -

Connect to Domain over a subnet

by Peter Bate In reply to Connect to Domain over a ...

Poster rated this answer

Collapse -

Connect to Domain over a subnet

by Peter Bate In reply to Connect to Domain over a ...

This question was closed by the author

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums