Re: OT:Accesing network drives from the command prompt

On Thu, 15 Jun 2006 09:00:23 +0000, frag wrote:

catman wrote:

On Mon, 12 Jun 2006 21:24:03 +0100, Rope wrote:

Jeremy spoke:
If I start the PC and , without accessing the drive via explorer,
type >> in at the command prompt:

N:

it fails to see the drive. After the drive has been accessed by
explorer, the N: comand works fine.

The network drive is defined as "reconnect at logon".

I have a client with a Win2003 server and XP-Pro clients, and on 2
of the machines this same behaviour is evident - on re-start the
icons pointing to stuff on P: drive are default - and won't work.
Fire up explorer and click on P: and everything is fine.

this is on 2 machines - identical to the rest in every way,
including permissions etc. on the server.

So, basically, norrafukinclue.

Having thought about this, my suggestion would be:
Unmap the network drives
edit login script to include net use commands
that should work under any cicumstances

HTH

It will.

Windows "Reconnect on Startup" is a lie, it should be "Reconnect when
accessed by Explorer".

I think mapping drives with "Reconnect on Startup" in Explorer doesn't
use the "net /persistent" behaviour, it flags the shares in the
registry and does it on the fly.

Anything else that uses the Windows Explorer APIs works fine, its just
the DOS command prompt/batch files that don't reconnect them.

Which is damn annoying and customers hit this problem all the time.

Coo, worked out from first principles. Cheers

--
Catman MIB#14 SKoGA#6 TEAR#4 BOTAFOF#38 Apostle#21 COSOC#3
Tyger, Tyger Burning Bright (Remove rust to reply)
Alfa 116 Giulietta 3.0l (Really) Sprint 1.7 75 TS 156 TS S2
Triumph Speed Triple: Black with extra black bits
www.cuore-sportivo.co.uk

.