Network path not found on botup...

[Bruno]

Hi, Hoping someone has the answer to this:

I have a Win2K pro workstation that is basically an unattended machine whihc
performs it's daily tasks...

When there is a power failure this computer, along with others (such as the
server) go down and come back up when the power returns.

Unfortunately, the server takes longer to come up than the win2K system, and
the 2K system produces an error dialog:

An error occurred while connecting to (server sharename)
Microsoft Windows Network - The network path was not found
Continue restoring connections?

Unfortunately the computer waits at this prompt indefinitely, and fails to
get on to it's tasks.

Does anyone know how to switch this prompt off?
(my Win98 machines do not wait this way - They will go on their merry way,
and start using the share when it becomes available...)

 

[Pegasus \(MVP\)]

Hi, Hoping someone has the answer to this:

I have a Win2K pro workstation that is basically an unattended machine whihc
performs it's daily tasks...

When there is a power failure this computer, along with others (such as the
server) go down and come back up when the power returns.

Unfortunately, the server takes longer to come up than the win2K system, and
the 2K system produces an error dialog:

An error occurred while connecting to (server sharename)
Microsoft Windows Network - The network path was not found
Continue restoring connections?

Unfortunately the computer waits at this prompt indefinitely, and fails to
get on to it's tasks.

Does anyone know how to switch this prompt off?
(my Win98 machines do not wait this way - They will go on their merry way,
and start using the share when it becomes available...)

Instead of relying on remembered connections, you need
to seize control and make these connections in a logon
script. It could look likes so:

@echo off
net use /persistent:no
net use * /del /yes

:Again
ping SomeServer | find /y "bytes=" && goto Next
echo %time:~0,5% Waiting for the server to become available . . .
ping localhost -n 60 > nul
goto Again

:Next
net use q: \\SomeServer\SomeShare

 

[Bruno]

Instead of relying on remembered connections, you need
to seize control and make these connections in a logon
script. It could look likes so:

@echo off
net use /persistent:no
net use * /del /yes

:Again
ping SomeServer | find /y "bytes=" && goto Next
echo %time:~0,5% Waiting for the server to become available . . .
ping localhost -n 60 > nul
goto Again

:Next
net use q: \\SomeServer\SomeShare

Good point - Put it in a script and forget about the fixed connections.
That should do the trick, thanks.