Logon script not executed

[Bart]

Hi,

I have an XP client (for public use in a library) connected to a Windows
2000 domain controller.
A simple logon script maps a drive letter to a public user share,
used to print directly to file.

I enabled automatic logon with TweakUI.

When I boot the pc, automatic logon works fine.
(Because the password is cached from a previous logon).
However, the logon script is not executed and the drive isn't mapped to the
share.

When I logoff and logon manually, the logon script is executed.

I think this happens because the automatic logon is executed before the
network card is ready for connections (?)
Can I delay the automatic logon for a few seconds?

Any advice on this issue.?

Thanks.

Bart

 

[Pegasus \(MVP\)]

Hi,

I have an XP client (for public use in a library) connected to a Windows
2000 domain controller.
A simple logon script maps a drive letter to a public user share,
used to print directly to file.

I enabled automatic logon with TweakUI.

When I boot the pc, automatic logon works fine.
(Because the password is cached from a previous logon).
However, the logon script is not executed and the drive isn't mapped to the
share.

When I logoff and logon manually, the logon script is executed.

I think this happens because the automatic logon is executed before the
network card is ready for connections (?)
Can I delay the automatic logon for a few seconds?

Any advice on this issue.?

Thanks.

Bart

- Where exactly does your logon script reside?
- Does the logon script work when you disable automatic logon
(i.e. when you let the PC rest for a minute before entering
your password)?
- What type of network adapter do you use? CAT5? Wireless?

 

[Bart]

Thanks for you reply.


The logon script resides on the server.

When I logon manually the logon script is executed without any problems.

The network card is a Broadcom NetXTreme 57xx.
The NIC is connected to a Cisco switch using a CAT5 cable.

Bart

 

[Pegasus \(MVP\)]

The phenomenon you describe occurs sometimes with
wireless adapters. It is rather unusual to experience in
a hard-wired environment.

I don't think there is a way to delay the execution of the
logon script. However, you can walk around the problem
by doing placing a file (which I recommend you name
"netlogon.bat") into the all user's Startup folder of your
machine. It should have these lines:

@echo off
ping localhost -n x > nul
\\YourServer\NetLogon\netlogon.bat

Line 2 will delay execution of the server-based logon script
by x seconds.
Line3 will execute the server-based logon script. This means
that the script is still centrally controlled.