Problem reconnecting mapped LAN drive at logon 1

[ottman2]

I have a shared folder on a NT 4.0 Server running Sp6. I have several workstation that are mapped to this drive. Originally mapped using Windows Explorer and I had checked "reconnect at logon". When each person boots up, they get a error at log on "An error ocurred while connecting H:" "The network name cannot be found". This happens before their logon script completes. The mapping of the h: drive is not part of the logon script. After the logging in completes, ther person can open Windows Explorer, the h: drive will have red x on the icon. The person can click on the h drive and the red x goes away and everything is fine. All workstation are running Windows NT 4.0 sp6.

I wanted to avoid putting in the mapping of drive in their logon script.

 

[rocketbabe]

I'm having the same problem. I thought there was a command you could use to delay the mappings until all the other startup services started...thereby preventing the "network name cannot be found" error.

Anyone have any ideas?

 

[bradje]

Perhaps a small batch file, to run at startup, with the SLEEP command used (NTRESKIT) for say 30 seconds

eg
sleep30
net use H: \\server\share /persistent:no