I had this problem with IBM T40's, T60's and so on. I dont know if it was just IBM laptops since it was an IBM shop thats all we had. I found the problem came when a user would un-dock (putting the computer to sleep before the un-dock or after), use another network such as wireless at home and come back into the office *without restarting.* This seemed to only occur when the computer was put to sleep. When ever their computer was powered off and then docked and booted the problem did not occur. One thing I did was set up profiles in the IBM access connections software but it seemed to complicated for the users (HR people!!) to switch between network profiles. I ended up writing a small script that flushed and re-registered DNS as well as renewing the IP information and either had the user run it when they returned to the office or put it in their startup and required them to log off and back on. Hope this helps! On 5/17/07, Darren Mar-Elia <darren@xxxxxxxxxx> wrote:
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? .