Subnet

[Bob H.]

Hello all,
I have a site (I'll call site 1}that is connected to
another site {site 2)via a dedicated T1. At site 2, we
utilize mostly thin clients, but we are adding some PC's.
Site 2 has no domain controller as of yet. Also, the
subnet for site 2 is not listed in AD. the problem is when
a user tries to logon from a PC to the domain from site 2,
they get an error that no domain controller is available.
If I add the subnet to AD can I pick a domain controller
to authenticate them? Site 1 has it's own domain
controller and subnet. Can I add site 2's subnet to site
1? In other words, can site 1's DC have 2 subnets
associated with it? I hope I explained this right and
thanks for the help.
Bob H.

 

[David Brandt [MSFT]]

I think I understand what you have, and I'd recommend just associating the
site2 subnet to site1 in AD sites & services. Since there is not a dc in
that site, creating an AD site and associating site2 subnet to it would
cause problems since the clients in that site would be looking for a dc in
that site to validate against. They would eventually find the other dc, but
it will slow things up a bit.
With the bandwidth you appear to have, just using one "logical" site in AD
appears to be the best option and I'd just associate the remote site's
subnet to it so that one AD site covers both. Clients look for dc's based
on their ip header info, and will look for a dc in the site associated with
that ip, and then if none found or responding will look for any dc they can
find.

You probably already know, but site definition in AD is based more on
bandwidth than on physical location. If I had a dc in San Fran, one in
Dallas, and one in NY with a T1, I'd probably have all 3 in the same logical
site in AD and whatever subnets all associated with that site.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

 

[Guest]

Thanks Dave,
I appreciate the help,
Bob H.

-----Original Message-----
I think I understand what you have, and I'd recommend just associating the
site2 subnet to site1 in AD sites & services. Since there is not a dc in
that site, creating an AD site and associating site2 subnet to it would
cause problems since the clients in that site would be looking for a dc in
that site to validate against. They would eventually find the other dc, but
it will slow things up a bit.
With the bandwidth you appear to have, just using one "logical" site in AD
appears to be the best option and I'd just associate the remote site's
subnet to it so that one AD site covers both. Clients look for dc's based
on their ip header info, and will look for a dc in the site associated with
that ip, and then if none found or responding will look for any dc they can
find.

You probably already know, but site definition in AD is based more on
bandwidth than on physical location. If I had a dc in San Fran, one in
Dallas, and one in NY with a T1, I'd probably have all 3 in the same logical
site in AD and whatever subnets all associated with that site.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.



.

 

[Herb Martin]

Go ahead and make the subnets -- you can change their Site association when
you add a DC to the remote site.

In general, you don't have to create "client-only" sites -- those that don't
have
DCs or DFS servers.

These are the only servers that (currently) seem to be site aware (or have
site
aware clients).

BTW -- I would love to hear of any new examples of "site aware" services.