Sites

  • Thread starter Thread starter Redleg6
  • Start date Start date
R

Redleg6

Guest
I need to start my site problem over.

I help adminster a Win2003 domain in a hospital. Recently we installed 10
workstations in a subclinic 60 miles away. The clinic connects to the
hospital with a T1 direct WAN link.

The tech who set this up, now gone, placed a router at the subclinic and the
router routes to the hospital for one network and the default gateway is to
another router connecting to the Internet. The network at the clinic is. of
course, different from the network the hospital uses. The route to the
hospital is used for certain medical applications and the Internet is used
for an accounting and billing application(different from what the hospital
uses).

Originally it was intended that the workstation at the subclinic would be
part of our domain so I could manage updates and we could more easilty
assist them using remote access and remote desktop. There were a lot of
problems when the first started up so my boss took them off the domain.
There is no domain controller at the subclinic and none is a planned.

These workstations need to be in our domain, IMHO. The issue is how. Should
I configure a separate site, even if there is no domain controller, or
should I just add them to the site the hospital uses?
 
Re: Sites

Redleg,
There is no value in adding a Site. For location-aware services the clients
will need to find a service at the main site regardless.
There's a couple of things to consider.
1) Setting the slow link policies to reflect the line speed and what you
want to happen. You might want the clients to always obtain policy, or never
obtain policy etc. You can make the clients work as though they are
connected to the network but slow, or not connected to the network at all.
2) DNS. To operate on the domain the clients need to have the main site DC
as their DNS service. This creates a dependency on the link, and possibly a
slow response but it is necessary to operate in the domain. If they don't
operate as part of the domain you may as well disjoin them.
Hope that helps,
Anthony,
http://www.airdesk.com


"Redleg6" <redleg6@community.nospam> wrote in message
news:eVSOtMjJJHA.456@TK2MSFTNGP06.phx.gbl...
> I need to start my site problem over.
>
> I help adminster a Win2003 domain in a hospital. Recently we installed 10
> workstations in a subclinic 60 miles away. The clinic connects to the
> hospital with a T1 direct WAN link.
>
> The tech who set this up, now gone, placed a router at the subclinic and
> the router routes to the hospital for one network and the default gateway
> is to another router connecting to the Internet. The network at the clinic
> is. of course, different from the network the hospital uses. The route to
> the hospital is used for certain medical applications and the Internet is
> used for an accounting and billing application(different from what the
> hospital uses).
>
> Originally it was intended that the workstation at the subclinic would be
> part of our domain so I could manage updates and we could more easilty
> assist them using remote access and remote desktop. There were a lot of
> problems when the first started up so my boss took them off the domain.
> There is no domain controller at the subclinic and none is a planned.
>
> These workstations need to be in our domain, IMHO. The issue is how.
> Should I configure a separate site, even if there is no domain controller,
> or should I just add them to the site the hospital uses?
>
>
>
 
Re: Sites

You didn't specifically ask this, but:

> The tech who set this up, now gone, placed a router at the subclinic and
> the router routes to the hospital for one network and the default gateway
> is to another router connecting to the Internet.

The WAN Routers are the functional equivalent of a LAN Router. The LAN
Routers should always be the Default Gateway of the Hosts they "serve". The
"Internet" should never be the Default Gateway of individual Hosts on the
LAN. This is because the LAN's routing decisions need to be made by the LAN
Routers and will involved a carefully thought out pattern of Default
Gateways that eventually lead to the Internet Routers. The rest of the LAN
Segments should be handled either by Static Routes on the LAN Routers or by
using Dynamic Routing Protocols (RIP, IGRP, etc) among the LAN Routers.

--
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.
-----------------------------------------------------
 
RE: Sites

Hi,

Thanks for using our newsgroup.

I agree with Anthony. As we know, sites should reflect our real network and
correspond to subnet. By dividing into different sites, the clients with
different subnets will locate the DC with the same subnet as clients.
However, If there is only one DC in your network, we don't need to split an
additional site, because all clients will locate this DC to logon and
authenticate.

For your scenario, you should ensure clients in the different subnet can
access DC. Moreover, If DNS server is AD-integrated, you should configure
all clients' DNS points to DC. However, in this case, clients may
experience slow logon when they first logon to Domain. If for Windows XP
clients, you can enable "Fast logon optimization" group policy. When Fast
Logon Optimization is enabled, all user logons are cached. The users will
use cached credential to authenticate to accelerate logon process.

About how to enable or disable Fast Logon Optimization:
======
Description of the Windows XP Professional Fast Logon Optimization feature
http://support.microsoft.com/kb/305293/en-us

If anything is unclear, please post back.



Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
--->From: "Redleg6" <redleg6@community.nospam>
--->Subject: Sites
--->Date: Sat, 4 Oct 2008 09:08:45 -0600
--->Lines: 26
--->X-Priority: 3
--->X-MSMail-Priority: Normal
--->X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
--->X-RFC2646: Format=Flowed; Original
--->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
--->Message-ID: <eVSOtMjJJHA.456@TK2MSFTNGP06.phx.gbl>
--->Newsgroups: microsoft.public.windows.server.general
--->NNTP-Posting-Host: pppoe1076.ka.centurytel.net 64.91.57.60
--->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.general:45764
--->X-Tomcat-NG: microsoft.public.windows.server.general
--->
--->I need to start my site problem over.
--->
--->I help adminster a Win2003 domain in a hospital. Recently we installed
10
--->workstations in a subclinic 60 miles away. The clinic connects to the
--->hospital with a T1 direct WAN link.
--->
--->The tech who set this up, now gone, placed a router at the subclinic
and the
--->router routes to the hospital for one network and the default gateway
is to
--->another router connecting to the Internet. The network at the clinic
is. of
--->course, different from the network the hospital uses. The route to the
--->hospital is used for certain medical applications and the Internet is
used
--->for an accounting and billing application(different from what the
hospital
--->uses).
--->
--->Originally it was intended that the workstation at the subclinic would
be
--->part of our domain so I could manage updates and we could more easilty
--->assist them using remote access and remote desktop. There were a lot of
--->problems when the first started up so my boss took them off the domain.
--->There is no domain controller at the subclinic and none is a planned.
--->
--->These workstations need to be in our domain, IMHO. The issue is how.
Should
--->I configure a separate site, even if there is no domain controller, or
--->should I just add them to the site the hospital uses?
--->
--->
--->
--->
 
Back
Top