Windows 2000 Logs on using cached credentials

[Mike]

I have a few Windows 2000 laptops that log on to a Windows 2003 domain by
connecting the laptop to an ethernet connection. Next they go home and use
cached credentials to logon. When they return to work they don't get a logon
script on their first logon. If they log off and then back on the logon
script runs correctly.

When they logon and it doesn't get the logon script, %logonserver% is set to
the local computer name, not the name of the DC. Could it possibly be
because the computer is still initializing the LAN connection, waiting for a
DHCP address, etc? Is there a way to set Windows to wait longer before
determining a DC is not available and switches to a cached logon?

Thanks,
Mike

 

[Robert L [MS-MVP]]

posting the result of the laptop ipconfig /all (first logon) here may help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.
I have a few Windows 2000 laptops that log on to a Windows 2003 domain by
connecting the laptop to an ethernet connection. Next they go home and use
cached credentials to logon. When they return to work they don't get a logon
script on their first logon. If they log off and then back on the logon
script runs correctly.

When they logon and it doesn't get the logon script, %logonserver% is set to
the local computer name, not the name of the DC. Could it possibly be
because the computer is still initializing the LAN connection, waiting for a
DHCP address, etc? Is there a way to set Windows to wait longer before
determining a DC is not available and switches to a cached logon?

Thanks,
Mike