Hello Stefan,
Sorry misunderstood it a bit. If you use your "supernet" exactly what you
describe can happen. To have it correct you have to add the single subnet's,
so that you can assign the DC to the correct subnet.
From: http://technet.microsoft.com/en-us/library/cc730718.aspx
"Identify the range of IP addresses that domain controllers in THIS site
use-and that identify the domain controllers as members of THIS site-by creating
a subnet object and associating it with the new site."
Also have a look here:
http://technet.microsoft.com/en-us/library/cc754697.aspx
http://technet.microsoft.com/en-us/library/cc731907.aspx
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Post by Stefan 'Birdie' VogelHi Meinolf,
so far about what I knew ;-)
The question has been: Is it ok to add "super-nets" or do I have to add the
subnets themself,
and, more important, because I need a proof for a discussion on this, I
search for any documentation from MS, telling this way or that way is the
correct way.
From what I have seen in the last years, if someone added only a
"super"net, we sometimes hove clients connecting to the wrong DCs.
After correcting this to the seperate detailed subnets, it is fine. So
from my experience it is obvious the detailed subnet information is
necessary, but I have been asked for a document with a proof from
MS... :-/
Regards
Stefan
Post by Meinolf WeberHello Stefan,
If zou have multiple sites and subnets, you have to configure the
subnets in ADSS and also create a site which belongs to the subnet.
Then move the DC to the site and the clients will use the DC in there
belonging site for the logon. Also make this DC's DNS and GC if not
done.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Post by Stefan 'Birdie' VogelHi together,
we sometime experience issues with clients that do not login to the
local DC, but to a DC in a different site.
We are using eg.
10.165.1.0/24
10.165.2.0/24
...
10.165.200.0/24
would it be ok to put
10.165.0.0/16
in sites and services, or do we have to put all 200 class C networks in
there (like I think)?
I'm searching for a MS white paper or similar on this, but can't find
anything.
Regards
Stefan