Logon to domaincontroller from subnet

[arnaudvdv]

Hello,

Does anyone know if it is possible to logon to a domaincontroller from a subnet in another location?

We have a new very small office, without a server, which is connected through SDSL with the main office. The DC (Win2k Server) is in the main office and can be reached from the new office. Now I would like to know if it is possible to add a system in the small office to the domain in the main office. Or at least if it is already in the domain, is it possible to logon to the DC from the new office?

Thx in advance.

Arnaudvdv

 

[Davetoo]

As long as a computer can see the DC, then you should be able to logon to it no problem.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[Koonan]

If the clients in this small have entries for a DNS server that is part of our AD, the client will query for the nearest DC to log it in. You can help the clients find the DCs you want them to use by configuring the Subnet in AD Sites and Services, and adding that subnet to whichever Site you want them use. I thinking you have not created any Sites yet, so you should just have the one "Default-First-Site-Name". By default any subnet that is not configured will authenticate with this site.

Remember DNS is the key when logging into a domain. DNS tells the client which DCs to use. Creating Sites and Subnets helps control which DCs the clients try first.

=====================================
The good ole days weren't always good
and tomorrow ain't as bad as it seems
=====================================

 

[arnaudvdv]

Great, thanx. I have added the subnet to the "Default-First-Site-Name" and will try if it works asap.

 

[Seaspray0]

If you are having difficulty at the branch office, try the following:

Set a fixed IP address on a client PC in the branch to be within the subnet for that branch, set the gateway to your router so you can get to the corporate subnet with IP packets, set the DNS server as your corporate server DNS.

ping your corporate server DNS IP address to make sure you can see it. If you can't you have a routing issue.

logon.


A+/MCP/MCSE/MCDBA