AD site problem

I am adding a 3ed site to my AD, with a new subnet... I have gone into sites
and services and added an IP range, a new site and added a domain controller
to the site... I put the DC in the new subnet, everything seams to be
working fine, however when a client connects to that site, it's logon server
continues to be from another site. So traffic is going over a slow link
rather then the local DC that is set to be the server for that site.



I checked the client with some VB script and it's defiantly part of the
site, why would it not be picking up the DC for that site?



Thanks

It might be worth posting in the AD newsgroup. It is really an AD
question, not networking. Does the DC in the site have a copy of the Global
Catalog?

"John Smith" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I am adding a 3ed site to my AD, with a new subnet... I have gone into
>sites and services and added an IP range, a new site and added a domain
>controller to the site... I put the DC in the new subnet, everything seams
>to be working fine, however when a client connects to that site, it's logon
>server continues to be from another site. So traffic is going over a slow
>link rather then the local DC that is set to be the server for that site.
>
>
>
> I checked the client with some VB script and it's defiantly part of the
> site, why would it not be picking up the DC for that site?
>
>
>
> Thanks
>
>
>
>

Possible Netlogon failure to update SRV records:

http://support.microsoft.com/default...b;en-us;259435

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"John Smith" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I am adding a 3ed site to my AD, with a new subnet... I have gone into
sites
> and services and added an IP range, a new site and added a domain
controller
> to the site... I put the DC in the new subnet, everything seams to be
> working fine, however when a client connects to that site, it's logon
server
> continues to be from another site. So traffic is going over a slow link
> rather then the local DC that is set to be the server for that site.
>
>
>
> I checked the client with some VB script and it's defiantly part of the
> site, why would it not be picking up the DC for that site?
>
>
>
> Thanks
>
>
>
>

Check to see if the clients at that site are pointing to the domain
controller at the site as the first preferred dns server in their tcp/ip
properties. I don't know if that will be the solution for sure, but worth
trying. Using the support tools netdiag and dcdiag on the domain controller
and netdiag on the client computers could be very helpful in determining if
network connectivity and domain configuration is correct. --- Steve


"John Smith" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I am adding a 3ed site to my AD, with a new subnet... I have gone into
>sites and services and added an IP range, a new site and added a domain
>controller to the site... I put the DC in the new subnet, everything seams
>to be working fine, however when a client connects to that site, it's logon
>server continues to be from another site. So traffic is going over a slow
>link rather then the local DC that is set to be the server for that site.
>
>
>
> I checked the client with some VB script and it's defiantly part of the
> site, why would it not be picking up the DC for that site?
>
>
>
> Thanks
>
>
>
>