I have a 5 machine network, all with 2000 Server. Three
of the machines have SP2. Two of the machines have SP4.
They are all connected using an USR WAP 2450 and each
have USR Wireless Adapters 2410. The two with SP4 will
not reconnect any mapped network drives when starting up.
They just display the "Restoring Network Connections"
dialog and then give "An error occurred while
connecting..." Once the system tray appears, you can see
the network connection icon for the USR adapter with an X
through it (indicating it is not connected) but quickly
after, it disappears (indicating it has finally connected
to the network.) Once you are at the desktop, you can
start up explorer and see any mapped drives with a red X
signifying that they are not connected. However, if you
click on any mapped drive, it will immediately show you
the contents of that drive and, hence, allow whatever
software that is utilizing that mapped drive to start.
This does not occur on the machines that have SP2. They
connect just fine. It seems that for whatever reason,
SP4's device startup protocol is not starting the
wireless adapter at the proper time as opposed to SP2,
which is starting it early enough so that when Windows is
trying to connect the mapped network drives the network
adapter is ready to roll. Any suggestions?

Get those machines with SP2 up to SP4 and ms03-039. Don't connect to the
internet before you've done that.
You might already been blasted.

--
Regards,

Marina
Microsoft SBS-MVP

"Russ" <(E-Mail Removed)> schreef in bericht
news:189901c3fbe9$720cf770$(E-Mail Removed)...
> I have a 5 machine network, all with 2000 Server. Three
> of the machines have SP2. Two of the machines have SP4.
> They are all connected using an USR WAP 2450 and each
> have USR Wireless Adapters 2410. The two with SP4 will
> not reconnect any mapped network drives when starting up.
> They just display the "Restoring Network Connections"
> dialog and then give "An error occurred while
> connecting..." Once the system tray appears, you can see
> the network connection icon for the USR adapter with an X
> through it (indicating it is not connected) but quickly
> after, it disappears (indicating it has finally connected
> to the network.) Once you are at the desktop, you can
> start up explorer and see any mapped drives with a red X
> signifying that they are not connected. However, if you
> click on any mapped drive, it will immediately show you
> the contents of that drive and, hence, allow whatever
> software that is utilizing that mapped drive to start.
> This does not occur on the machines that have SP2. They
> connect just fine. It seems that for whatever reason,
> SP4's device startup protocol is not starting the
> wireless adapter at the proper time as opposed to SP2,
> which is starting it early enough so that when Windows is
> trying to connect the mapped network drives the network
> adapter is ready to roll. Any suggestions?