An error occurred while reconnecting....

[Guest]

Small office network w
Files server running Small Busines server 2000 (latest updates)
and 24 workstations running 2000 pro (latest updates) (never are all
workstations running simultaneously).

Recently we've been getting errors frequently -

An error occurred while reconnecting M: to \\NAME\M
Microsoft Windows Network : The local device name is already in use.
This connection has not been restored.

Nothing has changed within network. Any suggestions as to what might be the
casue and what might resolve this would be greatly appreciated.

 

[Richard G. Harper]

This generally means that there was an error connecting during a previous
(or the current) session and as a result your mappings are toast. Best way
to handle this is to open a command prompt and type:

net use * /d

with caution - as it will disconnect ALL network mappings. Then either
restart the PC (if mappings are brought in as part of a logon script or
such) or re-map drives using whatever other process you use.

This is only an immediate fix - the permanent fix is to find out why the
mappings are being lost in the middle of a session and fix that. Could be a
flakey server or network card, bad switch or hub or such, or bad cabling, or
errors on the server causing the disconnect ...

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Guest]

Sorry for the delayed response:
The problem was resolved by upgrading a portion of the network to gigabit,
connecting the server and 4 users with the largest ACT databases (stored on
the server) on that portion of the network. Whether the problem was the
replaced switch or results of load/traffic I'm not sure but all's working
well.

Thanks again for taking the time to respond to the post!

This generally means that there was an error connecting during a previous
(or the current) session and as a result your mappings are toast. Best way
to handle this is to open a command prompt and type:

net use * /d

with caution - as it will disconnect ALL network mappings. Then either
restart the PC (if mappings are brought in as part of a logon script or
such) or re-map drives using whatever other process you use.

This is only an immediate fix - the permanent fix is to find out why the
mappings are being lost in the middle of a session and fix that. Could be a
flakey server or network card, bad switch or hub or such, or bad cabling, or
errors on the server causing the disconnect ...

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Small office network w
Files server running Small Busines server 2000 (latest updates)
and 24 workstations running 2000 pro (latest updates) (never are all
workstations running simultaneously).

Recently we've been getting errors frequently -

An error occurred while reconnecting M: to \\NAME\M
Microsoft Windows Network : The local device name is already in use.
This connection has not been restored.

Nothing has changed within network. Any suggestions as to what might be
the
casue and what might resolve this would be greatly appreciated.

 

[Richard G. Harper]

Glad to hear you got it worked out in the end.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Sorry for the delayed response:
The problem was resolved by upgrading a portion of the network to gigabit,
connecting the server and 4 users with the largest ACT databases (stored
on
the server) on that portion of the network. Whether the problem was the
replaced switch or results of load/traffic I'm not sure but all's working
well.

Thanks again for taking the time to respond to the post!

This generally means that there was an error connecting during a previous
(or the current) session and as a result your mappings are toast. Best
way
to handle this is to open a command prompt and type:

net use * /d

with caution - as it will disconnect ALL network mappings. Then either
restart the PC (if mappings are brought in as part of a logon script or
such) or re-map drives using whatever other process you use.

This is only an immediate fix - the permanent fix is to find out why the
mappings are being lost in the middle of a session and fix that. Could
be a
flakey server or network card, bad switch or hub or such, or bad cabling,
or
errors on the server causing the disconnect ...

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"(e-mail address removed)"
<[email protected]>
wrote in message

Small office network w
Files server running Small Busines server 2000 (latest updates)
and 24 workstations running 2000 pro (latest updates) (never are all
workstations running simultaneously).

Recently we've been getting errors frequently -

An error occurred while reconnecting M: to \\NAME\M
Microsoft Windows Network : The local device name is already in use.
This connection has not been restored.

Nothing has changed within network. Any suggestions as to what might
be
the
casue and what might resolve this would be greatly appreciated.