Could it be that the wireless connection isn't coming up quickly enough when
the systems are first started? I'd suggest using a batch file in the
Startup group like this:
NET USE <d:> \\servername\sharename /d
NET USE <d:> \\servername\sharename
with a pair of commands (disconnect, then reconnect) for each network drive.
Of course, you'll replace <d:> with the actual drive letter, and
\\servername\sharename with the actual path to the network share.
By the time the system gets to the Startup folder the network connection
should be fully active and the drive mappings should work.
--
Richard G. Harper ((E-Mail Removed)) MVP Win9x
* Please post all messages and replies in the newsgroup so that
* all may benefit. Private mail is usually not replied to.
* Help US Help YOU ...
http://www.dts-l.org/goodpost.htm
"Rick Heikn" <(E-Mail Removed)> wrote in message
news:031901c3cdb5$283480d0$(E-Mail Removed)...
> On my two laptops, both using WiFi connections, I am
> getting "Permanent Connection Not Available" errors for my
> networked drives at startup. Applications using those
> drives fail if I try to use them immediately. However, if
> I use Windows Explorer and click on the drives, the
> connections are resolved and the applications can then
> successfully use them. I suspect a startup sequencing
> problem of some sort, but have no idea how to fix it.
> Strangely enough, the laptops are using different OS
> (Win98SE and WinSXP) as well as different WiFi hardware.
> I tried adding the "Last Drive=Z" line (ref KB article
> 130077) but it had no effect. Any ideas?
>
> Thanks,
> Rick Hein
Similar Threads
Linear Mode
