Slow start-up time when domain controller is not available.

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Hi.

I have a VPN-server that allows outside access to my network/domain.
The client computers outside my network are members of my domain, and they
logon to my domain using the "Log on using dial-up connection" option in the
windows logon box.
This works fine, except for clients try (and fail) to find the domain
controllers at start-up.
This results in the client having to time-out in the find domain controller
part of the start-up, and it takes some time.
Are there anyway that you can set the client to not look for the domain
until after the VPN-connection is dialled?

Regards Markussen

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

What OS is running on the client machines? When you say
startup what exactly do you mean?

"Markussen" <newsjunk@markussen.dk> wrote in message

> I have a VPN-server that allows outside access to my network/domain.
> The client computers outside my network are members of my domain, and
they
> logon to my domain using the "Log on using dial-up connection" option
in the
> windows logon box.
> This works fine, except for clients try (and fail) to find the domain
> controllers at start-up.
> This results in the client having to time-out in the find domain
controller
> part of the start-up, and it takes some time.
> Are there anyway that you can set the client to not look for the
domain
> until after the VPN-connection is dialled?

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

The clients are running Windows XP.
By start-up I mean period from when I press the powerbutton to the Windows Login screen
appers.

"Michael Giorgio - MS MVP" <Michael.Giorgio@NoSpam.mayerson.com> wrote in
<uugrlQZSEHA.1732@TK2MSFTNGP09.phx.gbl>:

>What OS is running on the client machines? When you say
>startup what exactly do you mean?
>
>"Markussen" <newsjunk@markussen.dk> wrote in message
>
>> I have a VPN-server that allows outside access to my network/domain.
>> The client computers outside my network are members of my domain, and
>> they logon to my domain using the "Log on using dial-up connection"
>> option in the windows logon box.
>> This works fine, except for clients try (and fail) to find the domain
>> controllers at start-up.
>> This results in the client having to time-out in the find domain controller
>> part of the start-up, and it takes some time.
>> Are there anyway that you can set the client to not look for the domain
>> until after the VPN-connection is dialled?
>
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Unless there are mapped drives reconnecting at logon
there shouldn't be any delay.
"Markus" <newsjunk@markussen.dk> wrote in message
> The clients are running Windows XP.
> By start-up I mean period from when I press the powerbutton to the
Windows Login screen
> appers.
>
> "Michael Giorgio - MS MVP" <Michael.Giorgio@NoSpam.mayerson.com> wrote
in
> <
>
> >What OS is running on the client machines? When you say
> >startup what exactly do you mean?