A lot of times the user simply hasn't physically connected to the LAN before they power on their notebooks. I see that a lot. In addition to what Darren said you should also check out the following articles: Cannot connect to domain controller and cannot apply Group Policy with Gigabit Ethernet devices <http://support.microsoft.com/default.aspx?scid=kb;en-us;326152> Group Policy application fails on a computer that is running Windows 2000, Windows XP Service Pack 1, or Windows XP Service Pack 2 <http://support.microsoft.com/kb/840669> Regards, //signed// Jamie R Nelson Systems Engineer Ingenium Corporation ________________________________ From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Thursday, May 17, 2007 9:34 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: net admins, have your laptop users experienced this.. I've seen this a lot. Unfortunately, there is no easy answer as its generally up to the network driver to do the right thing before the user logon processing occurs. One thing to check, are you disabling Fast Logon Optimization on these (assuming they are XP)? From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Washington, Booker Sent: Thursday, May 17, 2007 7:22 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] net admins, have your laptop users experienced this.. I have noticed that on occassion, my laptop users get the following errors when they log on, maybe after redocking: Could not execute the following script scriptname.bat. The system cannot find the file specified. And then just before that error in the log, I will see: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. Now, the user will continue to log on(maybe with cached credentials, etc). And they will even be able to access network resources where they have permissions, but when this error occurs at logon, obviously, any mapped drives that were scripted via batch file, or any other policies that are suppose to run are thwarted. I can't seem to figure out why it is so inconsistent. Some more environment information. These are IBM T40 laptops that use the IBM Access connections manager to control the NIC activity. It looks as though there is some kind of hiccup in the network connection that occurs at logon, but once the computer logs on, it will get the correct LAN ip address and network information (As opposed to connecting to our wireless network, which is the failover if the LAN connection is unavailable.) Any thoughts? .