• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Waiting for domain controller while on foreign nets

J
#1
Hi,

Scenario: Win2008 domain controllers and XP and win7pro clients.

The clients are used in three different network environments, at their
own office, at foreign domain network locations and at home. They are
only connected to our domain when being in their office.

We want these client computers ONLY to search / wait for response from
their default domain controller when connected to our office network. A
simple check of its leased IP address should tell windows if it
currently is connected to the office network and therefore should try to
connect to the DC.

How can we make these clients to be intelligent enough to not wait for
over 2 minutes searching for their default domain when they are *not
connected at all* or *connected to another subnet*?

I just feel it's not very user-friendly to wait for minutes for a domain
controller which one knows is not present on certain subnets, and I
hoped that win7 / win2008 finally had come up with something elegant to
improve this......

When connected to other networks than their office subnet:
Logging in takes 2min30sec and if they pull the network cable before
logging in it takes only 30 seconds..

Thanks for comments on this.

regards Tor
 

My Computer

D

Dusko Savatovic

#2
a) Instruct your mobile workers to log on without network connection (using
cached credentials). When they are logged on, they can connect to the
network, either wired or wireless.

b) Create local accounts on their computers. They can use local account when
they have no need and means to connect to their office network.

I'm using both options. When I want to use Outlook from my home, or some
other network, I use option "a". When I have no need for my office
connectivity, I use option "b".

And BTW, I'm using fingerprint scanner on Win 7. One finger for home,
another for office :-)


"Jake" <jake44@newsgroup> wrote in message
news:eKANVlJsKHA.4632@newsgroup

> Hi,
>
> Scenario: Win2008 domain controllers and XP and win7pro clients.
>
> The clients are used in three different network environments, at their
> own office, at foreign domain network locations and at home. They are
> only connected to our domain when being in their office.
>
> We want these client computers ONLY to search / wait for response from
> their default domain controller when connected to our office network. A
> simple check of its leased IP address should tell windows if it currently
> is connected to the office network and therefore should try to connect to
> the DC.
>
> How can we make these clients to be intelligent enough to not wait for
> over 2 minutes searching for their default domain when they are *not
> connected at all* or *connected to another subnet*?
>
> I just feel it's not very user-friendly to wait for minutes for a domain
> controller which one knows is not present on certain subnets, and I hoped
> that win7 / win2008 finally had come up with something elegant to improve
> this......
>
> When connected to other networks than their office subnet:
> Logging in takes 2min30sec and if they pull the network cable before
> logging in it takes only 30 seconds..
>
> Thanks for comments on this.
>
> regards Tor
>
 

My Computer

Users Who Are Viewing This Thread (Users: 1, Guests: 0)