Why does login script fails to map all network drives

[Guest computer1]

Why does login script fails to map all network drives? I found that by

logging off and on all the drives are mapped. Has anyone come across this

issue? Is there an issue with the domain controller? Any suggestions. Thanks.

[Guest Terry R.]

Re: Why does login script fails to map all network drives

 

The date and time was 8/26/2008 7:56 AM, and on a whim, computer1

pounded out on the keyboard:

> Why does login script fails to map all network drives? I found that by

> logging off and on all the drives are mapped. Has anyone come across this

> issue? Is there an issue with the domain controller? Any suggestions. Thanks.

 

The only time I see that is if the network connections are not fully

enabled at login. You may want to try setting a group policy to wait

for the network, under

Computer Configuration

Administrative Templates

System

Logon

Enable "Always wait for the network..."

 

--

Terry R.

 

***Reply Note***

Anti-spam measures are included in my email address.

Delete NOSPAM from the email address after clicking Reply.

[Guest Pegasus \(MVP\)]

Re: Why does login script fails to map all network drives

 

 

"computer1" <computer1@discussions.microsoft.com> wrote in message

news:52DB8F6B-C161-422F-BC66-D911824DE274@microsoft.com...

> Why does login script fails to map all network drives? I found that by

> logging off and on all the drives are mapped. Has anyone come across this

> issue? Is there an issue with the domain controller? Any suggestions.

> Thanks.

 

Give yourself some eyes and modify your logon script like so:

@echo on

net use S: \\YourServer\SomeShare

net use T: ...

net use

pause

 

What output do you see from the commands that attempt to map the problem

shares?