Not connecting drives in Login Script

The common causes of problems like this are link speed negotiation problems or latency due to spanning tree setup in network switches. The user profile loads later than the account login, and by then the link has stabilized.

The link speed negotiation problem can usually be resolved by locking the speed and duplex on both ends of the connection. That's only practical if the device is always connected to the same switch port. If the switch port never has more than one Ethernet device connected to it (no hubs), then spanning tree setup can be disabled on the port at the switch end. For Cisco switches, this is called "portfast".  This Cisco article describes troubleshooting techniques for initial connection delays. If you don't have a Cisco switch, the details may not apply, but the ideas will.

Jim

Hello Jim,

Thank you for your feedback. Their are no switches or a router - Actually I have a Cisco 3002 VPN Concentrator at that remote location. Plus I do not understand that we have 1 Dell and 1 HP using the same Login Script, going through the same 3002, and I have such different results...

I also was just told that we have another location where we have 2 identical Dell Laptops, 1 maps and the other does not....even stranger since I can login with Login "A" on PC1 and it maps then use the same login on PC2 and it does not map the drives....

this is like the twilight zone....

Note that one configuration of the 3002 includes an eight port 10/100 switch, so speed/duplex mismatches are still possible. I haven't been able to find anything in Cisco's documentation on the 3002 that describes how to lock the port speed and duplex settings. As to why two identically configured Dell laptops act differently when logging in to the same account, yep, that's the twilight zone!

There's an XP group policy setting (described here) that synchronizes domain login with network startup. That might move the problem back out of the twilight zone.

Jim