Error while reconnecting on server.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am running a small network in my home office: 1 W2K Server w/ 2 W2K hardwire clients. The hard drives on the machines are mapped as follows
on the server - machine 1 mapped as F, machine 2 mapped as
on machine 1 - server not mapped, machine 2 mapped as
on machine 2 - server mapped as G, machine 1 mapped as

For the last 3 weeks or so the following has been occurring. In "My Computer" or the Windows Explorer on the Server, there is a red "X" on top of "G". When I double click this entry I receive "An error occurred while reconnecting to G: \\machine2\C:machine2 Microsoft Windows Network: The local device is already in use. This connection has not been restored." This error will repeat a few times and then the connection will be OK. Note: the red "X" may also appear over "F" but I have never gotten the error message

My questions are
1. Why does the red "X" appear in the first place
2. How can I fix this, it is preventing Veritas Backup Exec from backing up machine 2 overnight.
 
The default timeout is 15 minutes. From a command prompt on the server side
net config server /autodisconnect:-1
for no disconnect.

Setting this from the command line may turn off auto tuning for the server
service. So a better solution is to navigate to
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

and set the Reg_DWord hex value of
"autodisconnect"=ffffffff

If "autodisconnect" doesn't exist, Add it.

(note; ffffffff = aprox. 8171 years)


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect.


:
| I am running a small network in my home office: 1 W2K Server w/ 2 W2K
hardwire clients. The hard drives on the machines are mapped as follows:
| on the server - machine 1 mapped as F, machine 2 mapped as G
| on machine 1 - server not mapped, machine 2 mapped as G
| on machine 2 - server mapped as G, machine 1 mapped as F
|
| For the last 3 weeks or so the following has been occurring. In "My
Computer" or the Windows Explorer on the Server, there is a red "X" on top
of "G". When I double click this entry I receive "An error occurred while
reconnecting to G: \\machine2\C:machine2 Microsoft Windows Network: The
local device is already in use. This connection has not been restored."
This error will repeat a few times and then the connection will be OK.
Note: the red "X" may also appear over "F" but I have never gotten the error
message.
|
| My questions are:
| 1. Why does the red "X" appear in the first place?
| 2. How can I fix this, it is preventing Veritas Backup Exec from backing
up machine 2 overnight.
 
Dave

I have changed the registry on my server. Thanks for the solution. I still, however, have a question. Why was I getting the error on only one of the two clients attached to my network

MRB
 
What I proposed was more of a work-around rather than the fix. Possibly one
of these applies.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;319075
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q273151
http://support.microsoft.com/?kbid=303339

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect.


:
| Dave,
|
| I have changed the registry on my server. Thanks for the solution. I
still, however, have a question. Why was I getting the error on only one of
the two clients attached to my network?
|
| MRB
 
The work-around works, it is preventing the clients and the server from auto-disconnecting from one another

On the other hand, none of the Articles referenced are applicable. The core question here is really, once a disconnect occurs what is going on in machine 2 that generates an error when the server attempts to reconnect? And yet, because the work-around prevents disconnection, it doesn't really matter. I'm just curious

MRB
 
Back
Top