An error occurred while reconnecting P: to \\File-server\data Microsoft Windows Network: The local

  • Thread starter Scott.Pichelman
  • Start date
S

Scott.Pichelman

Hi,

I've seen countless posts about this message and have not been able to
pinpoint the issue.

We have multiple Windows 2000 client workstations on a LAN within the
same subnet(203.57.228.X) as teh Windows 2003 server.
We authenticate to an NT4 PDC w/ a logon script(below) on the same
network.(203.57.228.X)

Logon script on PDC:

@if not "%ECHO%"=="" echo %ECHO%
set NETSW=/yes
if "%OS%"=="Windows_NT" set NETSW=/persistent:no %NETSW%
if exist x:*.* net use x: /delete
net use x: \\servername\sharename %NETSW%

net use h: /home
net use k: \\<server>\apps
net use n: \\<server>\notes
net use p: \\<server>\data
net use r: \\<server>\drawproj
net use y: \\<server>\ug



We have several network shares mapped to the 2003 server. One
particular share that is mapped on teh server Y:\\server\<share>
produces this error intermittently.

Usually users on the same network map drives to this Win 2003 server
SP1 and try to open/load files within Excel, Word or Unigraphics
programs then click on their save icon to re-save.
(Will the application create a new file or *.tmp on the mapped drive?)

Then, users get this error:

An error occurred while reconnecting P: to \\File-server\data
Microsoft Windows Network: The local device name is already in use.
This connection has not been restored.
OK

They click on the OK button. However, the file saves fine. I would
check on the mapped drive
and the saved file is there. So this error message doesn't block or
indicate that the file
was not saved.

This happens sporadically. Sometimes, I would not get any error
message and the file saves
fine. The problem occurs with any type of file that the user opens and
tries to save as another file.

Also, there is a RED X's on network shared drives/folders which go away
intermittently and
come back but do not cause issues - we can still access data?

Also, ther are no problems performing file operations on the mapped
drives (i.e. copy, cut,
delete).

There are no routers or switches between the client and servers.
So, no TTL's or timeouts with network devices.
We have a Samba WINS server on another network behind the Firewall -
but, would it interrupt NetBIOS/SMB or any user connectivity with
sharing? (137,138,139 or 445)

I tried setting a timeout to "-1" ion the 2003 file serving server:
net config server /autodisconnect:-1

OUTPUT:
Idle session time (min) -1

I've looked at MS technet, researched fixes, changed WINS server
variables and can't find anything concrete yet.

Any ideas?
Thanks for any resources or help!

SP
 
R

Richard G. Harper

Start by adding a disconnect to the script file for troublesome drives:

net use y: /d

before the mapping takes place.

Check for intermittent network errors - switches or cabling that are causing
dropouts.

--
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
 
S

Scott.Pichelman

Hi Richard,

Thanks for the quick response.

I ended up using net use y: /d and then remapping the drive with "net
use" y:\\<server>\ug /persistent:no.

Is "/persistent:no" OK to add in this case?

I am waiting for user input now...no reports after initial logins this
morning - see what happens.
Can check cabling in the fiber switch that the server is connected to
as well but would expect issue with other shares as well, right?.
We only have problems with "one" share on this server.(It is the D:
drive - root path on Windows 2003 server)
There is a problem with another share on another server that is on
another network.
Same situation, client and server on the same subnet/network(A linux
Samba fileserver that has a filesystem mount where only that share has
issues as well).
Else, like I mentioned: no routers or switches in the way of user
connectivity path.
Am I missing something else?

Thanks!

Scott
 
R

Richard G. Harper \(MVP Shell/User\)

Using /PERSISTENT:NO will work too. Follow my other suggestion to look for
intermittent network faults causing dropped connections.

--
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
 
S

Scott.Pichelman

Hi again,

Errors are back, but not as frequently?

What do you mean by check for "intermittent network faults causing
dropped connections."?

How can we check for network errors?
There are no entries in the event viewer logs that I can see?
How can we monitor? Research?
Any resources that you can help out with here?
Thanks!

Using /PERSISTENT:NO will work too. Follow my other suggestion to look for
intermittent network faults causing dropped connections.

--
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


Hi Richard,

Thanks for the quick response.

I ended up using net use y: /d and then remapping the drive with "net
use" y:\\<server>\ug /persistent:no.

Is "/persistent:no" OK to add in this case?

I am waiting for user input now...no reports after initial logins this
morning - see what happens.
Can check cabling in the fiber switch that the server is connected to
as well but would expect issue with other shares as well, right?.
We only have problems with "one" share on this server.(It is the D:
drive - root path on Windows 2003 server)
There is a problem with another share on another server that is on
another network.
Same situation, client and server on the same subnet/network(A linux
Samba fileserver that has a filesystem mount where only that share has
issues as well).
Else, like I mentioned: no routers or switches in the way of user
connectivity path.
Am I missing something else?

Thanks!

Scott
 
R

Richard G. Harper

I would be looking for physical problems with the network - bad switches or
hubs, bad cabling, bad routers, etc. rather than software problems. The
Event Viewer is of little help in these circumstances. Almost infallibly,
that particular error indicates that some event caused loss of connection to
the server in a previous session and the re-connection is being blocked for
that reason. So find out why things seem to drop out and lose their
connection and solve that problem or those problems.

--
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


Hi again,

Errors are back, but not as frequently?

What do you mean by check for "intermittent network faults causing
dropped connections."?

How can we check for network errors?
There are no entries in the event viewer logs that I can see?
How can we monitor? Research?
Any resources that you can help out with here?
Thanks!

Using /PERSISTENT:NO will work too. Follow my other suggestion to look
for
intermittent network faults causing dropped connections.

--
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


Hi Richard,

Thanks for the quick response.

I ended up using net use y: /d and then remapping the drive with "net
use" y:\\<server>\ug /persistent:no.

Is "/persistent:no" OK to add in this case?

I am waiting for user input now...no reports after initial logins this
morning - see what happens.
Can check cabling in the fiber switch that the server is connected to
as well but would expect issue with other shares as well, right?.
We only have problems with "one" share on this server.(It is the D:
drive - root path on Windows 2003 server)
There is a problem with another share on another server that is on
another network.
Same situation, client and server on the same subnet/network(A linux
Samba fileserver that has a filesystem mount where only that share has
issues as well).
Else, like I mentioned: no routers or switches in the way of user
connectivity path.
Am I missing something else?

Thanks!

Scott
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top