Bootup stalls on "Network path not found"

[Clueless in Seattle]

I have two old hand-me-down computers connected together in a
peer-to-peer network.

Everything worked fine for a few days, but now every morning when I
boot up, the first computer stalls on a message like this:

Restoring Network Connections
----------------------------------------------
...The network path was not found

Well, that's not too surprising, since I can only start one computer at
a time, and so the second computer is not up and running yet..

But how can I get Win 2K to automatically just skip trying to restore
the connection and proceed with the boot-up and let me manually restore
the connection once I boot up the second computer?

I've tried checking the box for "Do not try to restore the connection
in the future," but the next morning it does the same darned thing all
over again.

What is so irksome about this behavior is that it didn't used to happen
in the first few days that I had the computers networked. The only
change I can think of is that I mapped all of the drives on the second
computer a few days ago. Could that be a clue?

Will in Seattle
a.k.a. "Clueless"

 

[Pegasus \(MVP\)]

I have two old hand-me-down computers connected together in a
peer-to-peer network.

Everything worked fine for a few days, but now every morning when I
boot up, the first computer stalls on a message like this:

Restoring Network Connections
----------------------------------------------
...The network path was not found

Well, that's not too surprising, since I can only start one computer at
a time, and so the second computer is not up and running yet..

But how can I get Win 2K to automatically just skip trying to restore
the connection and proceed with the boot-up and let me manually restore
the connection once I boot up the second computer?

I've tried checking the box for "Do not try to restore the connection
in the future," but the next morning it does the same darned thing all
over again.

What is so irksome about this behavior is that it didn't used to happen
in the first few days that I had the computers networked. The only
change I can think of is that I mapped all of the drives on the second
computer a few days ago. Could that be a clue?

Will in Seattle
a.k.a. "Clueless"

Instead of relying on remembered connections, seize control
and make the connections in a startup batch file. Here is an
example:

@echo off
net use /persistent:no
ping SomePC -n 1 | find /i "bytes=" > nul || goto :eof
net use s: \\SomePC\SomeShare

Now place this batch file into the All Users\Startup folder
to make it run at logon time. You should have no further
problems!