Use the AD Sites Object.
Anything slower than a fully syncronous (same speed both ways) 10mbps link
is considered "slow". Some might argure that anything less than 100mbps is
"slow".
It is not all about bandwidth either it is about the link being over the
internet which will inevitablly at some point "go down". You want the LANs
to still be survivable in such a case. So have a local DC with DNS, DHCP &
WINS running at the local Site. This will keep local logins and local
authentication functioning if the links drops out.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Lewej" <(E-Mail Removed)> wrote in message
news:F5838E96-122C-44C5-8FB0-(E-Mail Removed)...
> Hi All
> We are opening a branch office and have ordered a 2MB leased line at each
> site and an MPLPS network that links them together.
> The leased line suppliers think that I do not need to set up seperate
> 'sites', and that DNS, dhcp and authentication can be done over the WAN
> link
> without too much bandwidth being hogged.
> I also use an IT support company, and they tell me using WAN link for dns,
> dhcp and authentication would have an adverse effect on the WAN link
> speed -
> and recommend against it. They think I should set up two sites, and so
> have
> inter-site replication which is a more efficient use of bandwidth.
> Given out computer needs are failry light and standard (MS Office, Email,
> an
> ERP which would only be accessed from one site only, and some file
> storage) I
> am not sure.
> I realise this is quite an open ended question too, but has anyone any
> opinions on this please
> TIA
> Lewej