Setting up sites in Sites and Services

Hi,

We have a multi domain multi site 2003 forest and experiencing a lot of
event ID’s 1865 and 1311.

Our organization is administered by many System Administrators and all of
them have different opinions on the best way to setup Sites and Services. My
understanding is there are two ways in which Sites and Services could and
should be setup:

1 Create multiple sites place a DC within the site and assign the subnets
that belong to that site in Sites and Services.

2 Create a site but have no local DC located in the site and assign the
subnet that belongs to this site to a different well connected site.

Option 1 will cause replication traffic.
Option 2 will cause logon traffic to the remote site that is assigned the
client PC subnets.

OK

Here comes the interesting bit that I’m confused about.

We have a site that has a local DC and when we set it up as Option 1 it
immediately complains of 1865 and 1311 errors. If within Sites and Services
we say that the local DC is no longer on site but is now located in a
different site and assign the subnets to this different site the errors go
away. Although the DC is still physically located in the old site.

I don’t think this is a good way to go forward but I am struggling to find
any evidence due to the fact the errors go away, so I am faced with System
Admins saying we need to do the same type of setup with any other sites that
are experiencing the same event ID errors.

Finally there are more than one DC in the site that is now pretending to
contain the remote DC as well so I’m thinking this is going to be performing
Intra-Site Replication when really it should be doing Inter-Site
Replication. The two sites are connected by a 2 meg WAN link.

Any thoughts are much appreciated.

Hello Paul,

AD sites and services configure always with the physical sites and the belonging
subnets, if a DC is there or not. If you move a DC in the subnet it must
also have the correct ip addressing for that subnet.

See here about best practise for AD sites and services:
http://technet.microsoft.com/en-us/l.../cc755768.aspx

Have a look here about 1865:
http://technet.microsoft.com/en-us/l...48(WS.10).aspx

1311:
http://technet.microsoft.com/en-us/l...93(WS.10).aspx

Additional make sure that all DC's are registered correct in the DNS zones,
that they are not multihomed or run RRAS.

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


> Hi,
>
> We have a multi domain multi site 2003 forest and experiencing a lot
> of event ID's 1865 and 1311.
>
> Our organization is administered by many System Administrators and all
> of them have different opinions on the best way to setup Sites and
> Services. My understanding is there are two ways in which Sites and
> Services could and should be setup:
>
> 1 Create multiple sites place a DC within the site and assign the
> subnets that belong to that site in Sites and Services.
>
> 2 Create a site but have no local DC located in the site and assign
> the subnet that belongs to this site to a different well connected
> site.
>
> Option 1 will cause replication traffic.
> Option 2 will cause logon traffic to the remote site that is assigned
> the
> client PC subnets.
> OK
>
> Here comes the interesting bit that I'm confused about.
>
> We have a site that has a local DC and when we set it up as Option 1
> it immediately complains of 1865 and 1311 errors. If within Sites and
> Services we say that the local DC is no longer on site but is now
> located in a different site and assign the subnets to this different
> site the errors go away. Although the DC is still physically located
> in the old site.
>
> I don't think this is a good way to go forward but I am struggling to
> find any evidence due to the fact the errors go away, so I am faced
> with System Admins saying we need to do the same type of setup with
> any other sites that are experiencing the same event ID errors.
>
> Finally there are more than one DC in the site that is now pretending
> to contain the remote DC as well so I'm thinking this is going to be
> performing Intra-Site Replication when really it should be doing
> Inter-Site Replication. The two sites are connected by a 2 meg WAN
> link.
>
> Any thoughts are much appreciated.
>

"Paul" <Paul@discussions.microsoft.com> wrote in message news:4C8B3101-5289-41A0-BDAF-2C4DCDACDBE9@microsoft.com...
> Hi,
>
> We have a multi domain multi site 2003 forest and experiencing a lot of
> event ID’s 1865 and 1311.
>
> Our organization is administered by many System Administrators and all of
> them have different opinions on the best way to setup Sites and Services. My
> understanding is there are two ways in which Sites and Services could and
> should be setup:
>
> 1 Create multiple sites place a DC within the site and assign the subnets
> that belong to that site in Sites and Services.
>
> 2 Create a site but have no local DC located in the site and assign the
> subnet that belongs to this site to a different well connected site.
>
> Option 1 will cause replication traffic.
> Option 2 will cause logon traffic to the remote site that is assigned the
> client PC subnets.
>
> OK
>
> Here comes the interesting bit that I’m confused about.
>
> We have a site that has a local DC and when we set it up as Option 1 it
> immediately complains of 1865 and 1311 errors. If within Sites and Services
> we say that the local DC is no longer on site but is now located in a
> different site and assign the subnets to this different site the errors go
> away. Although the DC is still physically located in the old site.
>
> I don’t think this is a good way to go forward but I am struggling to find
> any evidence due to the fact the errors go away, so I am faced with System
> Admins saying we need to do the same type of setup with any other sites that
> are experiencing the same event ID errors.
>
> Finally there are more than one DC in the site that is now pretending to
> contain the remote DC as well so I’m thinking this is going to be performing
> Intra-Site Replication when really it should be doing Inter-Site
> Replication. The two sites are connected by a 2 meg WAN link.
>
> Any thoughts are much appreciated.
>

It sounds like a networking issue that would cause these events.

Keep in mind, Your option 1 and 2, and really these are not options, but it is the way it is done, is how Sites are created. Subnets objects are created and associated to a physical location/site. You can have multiple subnets per site. The DC must be physically moved to the Site. If you have any sites that do not have DCs, but do have clients, and you want to control which DCs they log in to, then create a subnet object for that site, and associated it with a Site with the DCs that you want them to log in to. So that would cover your option 2, which is really not an "option" rather just an extension of your Option 1.

Once you moved the DCs into their respect Sites, run:
ipconfig /registerdns
net stop netlogon
net start netlogon

Replication traffic is reduced between sites in the fact that replication traffic is compressed. But it will increase a bit of traffic for GC replication. Keep in mind, if you only have one domain, make sure that ALL domain controllers are GC. If more than one domain, make sure the IM role is not sitting on a GC.

Make sure that you do not use the ISP's DNS addresses anywhere in any machine other than a forwarder in DNS properties. That will cause these errors as well.

If you have any multihomed DCs, that will cause this error, because now it will be part of multiple Sites, and DCs can't do that.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@mvps.RemoveThisPart.org

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay