boot problem with mapped drives

[Guest Lorne]

I have a W2000 SP4 machine on a peer to peer network, connected by wireless

card. there are 2 mapped drives to another machine.

 

When turned on the boot stops with a message unable to connect to a netwrork

drive, do you want to connect next time? I say yes and it boots OK, then I

execute a batch file that connects to the other machine (there is a

password) and all is fine.

 

However it is very annoying that the boot stops and will only complete with

manual intervention. The problem is that the wireless card is not

initialised early enough so when Windows tries to connect during boot the

network is not available. so I ask:

 

1. Is it possible to change the boot order so the network connections are

not made until after the wireless card is enabled? if not,

2. Is it possible to get windows to automatically select option to continue

the boot and keep the mapped drives avalable for the future? if not

3. If I creat a batch file with a line like "NET USE Z:

\\netcomputer\myfolder" and put it in the users stratup folder will it

execute after the wireless card is enabled and how do I automatically delete

the map when the user closes down so the unwanted message that it can't

connect does not show up.

[Guest Pegasus \(MVP\)]

Re: boot problem with mapped drives

 

 

"Lorne" <lorne_anderson@hotmail.com> wrote in message

news:es4wGb88IHA.1196@TK2MSFTNGP05.phx.gbl...

>I have a W2000 SP4 machine on a peer to peer network, connected by wireless

>card. there are 2 mapped drives to another machine.

>

> When turned on the boot stops with a message unable to connect to a

> netwrork drive, do you want to connect next time? I say yes and it boots

> OK, then I execute a batch file that connects to the other machine (there

> is a password) and all is fine.

>

> However it is very annoying that the boot stops and will only complete

> with manual intervention. The problem is that the wireless card is not

> initialised early enough so when Windows tries to connect during boot the

> network is not available. so I ask:

>

> 1. Is it possible to change the boot order so the network connections are

> not made until after the wireless card is enabled? if not,

> 2. Is it possible to get windows to automatically select option to

> continue the boot and keep the mapped drives avalable for the future? if

> not

> 3. If I creat a batch file with a line like "NET USE Z:

> \\netcomputer\myfolder" and put it in the users stratup folder will it

> execute after the wireless card is enabled and how do I automatically

> delete the map when the user closes down so the unwanted message that it

> can't connect does not show up.

 

You need three steps to do this:

1. Get Windows to stop remembered drives:

net use /persistent:no

2. Disconnect all remembered drives:

net use * /d /y

3. Arrange your startup connects, by placing this batch file

into your startup folder:

@echo off

ping localhost -n 30 > nul

net use z: \\netcomputer\MyShare

 

Adjust the delay, currently set 30 seconds, to suit your environment.

Note also that the "net use" command can't connect to a folder as

per your code but only to a share (or optionally to a folder within

this share).

[Guest Lorne]

Re: boot problem with mapped drives

 

"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message

news:OZgFMG98IHA.5404@TK2MSFTNGP04.phx.gbl...

>

>

> You need three steps to do this:

> 1. Get Windows to stop remembered drives:

> net use /persistent:no

> 2. Disconnect all remembered drives:

> net use * /d /y

> 3. Arrange your startup connects, by placing this batch file

> into your startup folder:

> @echo off

> ping localhost -n 30 > nul

> net use z: \\netcomputer\MyShare

>

> Adjust the delay, currently set 30 seconds, to suit your environment.

> Note also that the "net use" command can't connect to a folder as

> per your code but only to a share (or optionally to a folder within

> this share).

 

thanks for this - I was missing the persistent:no bit.

 

It seems to work without the ping localhost line as the wireless card is up

and working before any startup folder items get executed. Am I right that

this line was giving an extra 30 seconds for the system to get up and

running and I can safely discard it?

[Guest Pegasus \(MVP\)]

Re: boot problem with mapped drives

 

 

"Lorne" <lorne_anderson@hotmail.com> wrote in message

news:uwXbcAC9IHA.356@TK2MSFTNGP02.phx.gbl...

> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message

> news:OZgFMG98IHA.5404@TK2MSFTNGP04.phx.gbl...

>>

>>

>> You need three steps to do this:

>> 1. Get Windows to stop remembered drives:

>> net use /persistent:no

>> 2. Disconnect all remembered drives:

>> net use * /d /y

>> 3. Arrange your startup connects, by placing this batch file

>> into your startup folder:

>> @echo off

>> ping localhost -n 30 > nul

>> net use z: \\netcomputer\MyShare

>>

>> Adjust the delay, currently set 30 seconds, to suit your environment.

>> Note also that the "net use" command can't connect to a folder as

>> per your code but only to a share (or optionally to a folder within

>> this share).

>

> thanks for this - I was missing the persistent:no bit.

>

> It seems to work without the ping localhost line as the wireless card is

> up and working before any startup folder items get executed. Am I right

> that this line was giving an extra 30 seconds for the system to get up and

> running and I can safely discard it?

 

Yes.