Force clients to use DC for logon.

I have a network consisting of 3 DC's (all are GC's) and are located in 3
different locations. One of the locations was sold to another company but I
have to maintain the server and clients till 2010. The new company installed
all new networking and it takes over 20 hops to get to the servers at the
other locations. When one of the other servers authenticates a login request
it takes 10 minutes to logon. Is there a way to have the clients always use
the server that is located in that building?

Thanks...

You do that through Active Directory sites. You create additional sites
and link the sites to specific IP subnets. Machines will then logon to the
DC in the local site.

"BigMo" <(E-Mail Removed)> wrote in message
news:355780C1-8E30-40B7-8557-(E-Mail Removed)...
>I have a network consisting of 3 DC's (all are GC's) and are located in 3
> different locations. One of the locations was sold to another company but
> I
> have to maintain the server and clients till 2010. The new company
> installed
> all new networking and it takes over 20 hops to get to the servers at the
> other locations. When one of the other servers authenticates a login
> request
> it takes 10 minutes to logon. Is there a way to have the clients always
> use
> the server that is located in that building?
>
> Thanks...

Hello,

Thanks for your post and thanks Bill Grant for the information he shared.
This is Neo and I will be assisting you in this post.

From your description, I understand that:

Currently, you have an AD-based domain. You have three DCs in three
locations. The Internet connection speed between the first location and the
other two is slow. Your requirement is to force the clients in the first
location to use local DC for logon authentication.

If there is any misunderstanding, please let me know.

Generally speaking, AD based domains are site-aware. We can use AD Sites
and Services MMC snap-in to create 3 Subnet objects for the 3 physical
network, create 3 Site objects, and associate the Site objects to the
corresponding Subnet objects. After that, we should also manually move the
DCs to the related sites.

When user in the first location logs on, it will automatic identify which
physical network it locates and then find the related Subnet, Site objects
and the related DC. It always try to authenticate with the DC in its own
site.

For more information, please refer to:

Managing Sites
http://technet.microsoft.com/en-us/l.../bb727051.aspx

Windows 2000 Active Directory Sites and Services
http://www.microsoft.com/technet/sec.../w2kccadm/adsi
tes/w2kadm37.mspx

I hope this helps. Thanks.


Sincerely,
Neo Zhu,
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks Neo. That makes sense. Currently all 3 DC's are in the same site. I
figured that there would be no way that the first site server wouldn't answer
up for logon everytime but I was mistaken. I'll create a new site and move
the DC into it when I get back from Christmas break. Thanks again and Happy
Holidays.

"Jian-Ping Zhu [MSFT]" wrote:

> Hello,
>
> Thanks for your post and thanks Bill Grant for the information he shared.
> This is Neo and I will be assisting you in this post.
>
> From your description, I understand that:
>
> Currently, you have an AD-based domain. You have three DCs in three
> locations. The Internet connection speed between the first location and the
> other two is slow. Your requirement is to force the clients in the first
> location to use local DC for logon authentication.
>
> If there is any misunderstanding, please let me know.
>
> Generally speaking, AD based domains are site-aware. We can use AD Sites
> and Services MMC snap-in to create 3 Subnet objects for the 3 physical
> network, create 3 Site objects, and associate the Site objects to the
> corresponding Subnet objects. After that, we should also manually move the
> DCs to the related sites.
>
> When user in the first location logs on, it will automatic identify which
> physical network it locates and then find the related Subnet, Site objects
> and the related DC. It always try to authenticate with the DC in its own
> site.
>
> For more information, please refer to:
>
> Managing Sites
> http://technet.microsoft.com/en-us/l.../bb727051.aspx
>
> Windows 2000 Active Directory Sites and Services
> http://www.microsoft.com/technet/sec.../w2kccadm/adsi
> tes/w2kadm37.mspx
>
> I hope this helps. Thanks.
>
>
> Sincerely,
> Neo Zhu,
> Microsoft Online Support
> Microsoft Global Technical Support Center
>
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Hello,

Thank you for your feedback.

If you need further assitance, please feel free to let me know.

Thanks for using our products and hope you have nice holidays, too! : )


Sincerely,
Neo Zhu,
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.