One site - manual subnet

[Guest Marc S]

I am an IT Director that inherited a network from consultants:

I have One site, listed as the default "Default-First-Site-Name" with 3

Domain Controllers. 2 DCs are at local, 1 DC is remotely connected to a

Disaster Recovery Site by a BOVPN. (Branch Office. No users at remote site,

just 1 DC as a ready-hot site).

 

We use subnet at the main office 192.168.10.0 and a subnet at the remote

192.168.11.0 that communicate thru the BOVPN. No connection issues.

 

(1) Currently there are NO subnets listed in AD Sites and Services, and all

communication and replication seem fine? Is this normal for a One Site

shop???

 

(2) Is there a reason I should add either of the subnets manually? Maybe

just the local?

 

(3) My only issue is that when I connect from my workstation thru Active

Directory Users and Computers, I always to connect to the remote DC

first...which seems like a DNS issue...and slow?

[Guest thomville]

Re: One site - manual subnet

 

No subnets listed in a one-site shop is normal. I can't think of an

advantage to adding them if you are not going to create a second

site. Which you might want to do, as you likely have users using that

DC as their logon server setup the way you are. You could have your

local subnet in one site and the remote subnet in another - users

would look first to the site they are in (by the machine IP) for

resources, so they would only log in against the local DCs unless they

were down.

 

Not sure this is universal, but my ADUC initially connects to the DC

that holds the domain FSMO role of PDC. If that is the case for you,

think about moving at least that FSMO role off of your remote server.

 

Thom

 

 

 

On Feb 12, 12:14 pm, Marc S <Ma...@discussions.microsoft.com> wrote:

> I am an IT Director that inherited a network from consultants:

> I have One site, listed as the default "Default-First-Site-Name" with 3

> Domain Controllers. 2 DCs are at local, 1 DC is remotely connected to a

> Disaster Recovery Site by a BOVPN. (Branch Office. No users at remote site,

> just 1 DC as a ready-hot site).

>

> We use subnet at the main office 192.168.10.0 and a subnet at the remote

> 192.168.11.0 that communicate thru the BOVPN. No connection issues.

>

> (1) Currently there are NO subnets listed in AD Sites and Services, and all

> communication and replication seem fine? Is this normal for a One Site

> shop???

>

> (2) Is there a reason I should add either of the subnets manually? Maybe

> just the local?

>

> (3) My only issue is that when I connect from my workstation thru Active

> Directory Users and Computers, I always to connect to the remote DC

> first...which seems like a DNS issue...and slow?

[Guest Marc S]

Re: One site - manual subnet

 

Thanks. Yes. You are correct regarding some users logon to the remote DC. Not

sure why there aren't two sites. A project for another day.

 

Regarding the FSMO. Only 1DC that is local has this role, but my PC hits the

remote DC first. No one seems to have an answer.

 

"thomville" wrote:

> No subnets listed in a one-site shop is normal. I can't think of an

> advantage to adding them if you are not going to create a second

> site. Which you might want to do, as you likely have users using that

> DC as their logon server setup the way you are. You could have your

> local subnet in one site and the remote subnet in another - users

> would look first to the site they are in (by the machine IP) for

> resources, so they would only log in against the local DCs unless they

> were down.

>

> Not sure this is universal, but my ADUC initially connects to the DC

> that holds the domain FSMO role of PDC. If that is the case for you,

> think about moving at least that FSMO role off of your remote server.

>

> Thom

>

>

>

> On Feb 12, 12:14 pm, Marc S <Ma...@discussions.microsoft.com> wrote:

> > I am an IT Director that inherited a network from consultants:

> > I have One site, listed as the default "Default-First-Site-Name" with 3

> > Domain Controllers. 2 DCs are at local, 1 DC is remotely connected to a

> > Disaster Recovery Site by a BOVPN. (Branch Office. No users at remote site,

> > just 1 DC as a ready-hot site).

> >

> > We use subnet at the main office 192.168.10.0 and a subnet at the remote

> > 192.168.11.0 that communicate thru the BOVPN. No connection issues.

> >

> > (1) Currently there are NO subnets listed in AD Sites and Services, and all

> > communication and replication seem fine? Is this normal for a One Site

> > shop???

> >

> > (2) Is there a reason I should add either of the subnets manually? Maybe

> > just the local?

> >

> > (3) My only issue is that when I connect from my workstation thru Active

> > Directory Users and Computers, I always to connect to the remote DC

> > first...which seems like a DNS issue...and slow?

>

>

[Guest thomville]

Re: One site - manual subnet

 

My two cents still says that it is one of the FSMO roles. The PDC

that my ADUC connects to actually holds all of the FSMO roles, so my

singling out the PDM Emulator earlier may have been a red herring. Of

course there are reasons that my two cents is only two cents ..... At

any rate, I would be more concerned at having users logon against it

than I would be at having ADUC connect to it.

 

Have fun!

 

Thom

 

 

On Feb 12, 2:33 pm, Marc S <Ma...@discussions.microsoft.com> wrote:

> Thanks. Yes. You are correct regarding some users logon to the remote DC. Not

> sure why there aren't two sites. A project for another day.

>

> Regarding the FSMO. Only 1DC that is local has this role, but my PC hits the

> remote DC first. No one seems to have an answer.

>

> "thomville" wrote:

> > No subnets listed in a one-site shop is normal. I can't think of an

> > advantage to adding them if you are not going to create a second

> > site. Which you might want to do, as you likely have users using that

> > DC as their logon server setup the way you are. You could have your

> > local subnet in one site and the remote subnet in another - users

> > would look first to the site they are in (by the machine IP) for

> > resources, so they would only log in against the local DCs unless they

> > were down.

>

> > Not sure this is universal, but my ADUC initially connects to the DC

> > that holds the domain FSMO role of PDC. If that is the case for you,

> > think about moving at least that FSMO role off of your remote server.

>

> > Thom

>

> > On Feb 12, 12:14 pm, Marc S <Ma...@discussions.microsoft.com> wrote:

> > > I am an IT Director that inherited a network from consultants:

> > > I have One site, listed as the default "Default-First-Site-Name" with 3

> > > Domain Controllers. 2 DCs are at local, 1 DC is remotely connected to a

> > > Disaster Recovery Site by a BOVPN. (Branch Office. No users at remote site,

> > > just 1 DC as a ready-hot site).

>

> > > We use subnet at the main office 192.168.10.0 and a subnet at the remote

> > > 192.168.11.0 that communicate thru the BOVPN. No connection issues.

>

> > > (1) Currently there are NO subnets listed in AD Sites and Services, and all

> > > communication and replication seem fine? Is this normal for a One Site

> > > shop???

>

> > > (2) Is there a reason I should add either of the subnets manually? Maybe

> > > just the local?

>

> > > (3) My only issue is that when I connect from my workstation thru Active

> > > Directory Users and Computers, I always to connect to the remote DC

> > > first...which seems like a DNS issue...and slow?