Every now and then, after not having been active on one of my network drives for some time (one hour or so), I get the error message stated in the subject when I try to connect to files on one of my network drives. Then I need to retry a few times, or just wait 10 to 20 seconds, and everything is fine again. Does anyone know how to solve this problem? Other network related things like Internet and email work fine all the time.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Error: drive not accessible / the network path was not found 1
- Thread starter gtog
- Start date
- Thread starter
- #2
-
1
- #3
Autodisconnect needs manual "fixing" in a Workgroup setting:
- Thread starter
- #4
- Thread starter
- #5
bcastner, it didn't help unfortunately. I also tried the registry settings suggested by the following website:
but that also didn't help.
Does anyone have other suggestions?
but that also didn't help.
Does anyone have other suggestions?
Your Winguides registry key is the same as discussed in my earlier link to the MS Knowledge Base. You need to be certain that the registry change is made on the computer hosting the share(s).
The red x is by design to save resources. The network drives are not connected until they need to be used. Some applications cannot handle the delay in reconnecting. If your application is having an issue, you may consider disabling autodisconnect per the intructions below.
Sometimes network drives still get disconnected even with autodisconnect disabled. Usually this is caused by third party software or drivers (a/v software, network card agents, etc).
IF you are using applications that cannot automatically reconnect network drives, you can disable the autodisconnect behavior on either the server or
client side by changing the following registry keys:
On the server:
HKLM\System\CCS\Services\LanManServer\Parameters\Autodisconnect=0x0000FFFF
Note: The preceding entry must be located on the computer that offers the share or shares.
The valid value range if you edit the LAN Autodisconnect parameter in the registry is 0 to 4294967295 0xffffffff). For a Windows 2000 Server in a Domain, running either as a domain controller or as a server, the maximum value is 65,535 (0xffff). Values set above this will be returned to 0xffff after policy refresh. Windows 2000 Servers in a Workgroup may be set to any value as indicated.
On the client:
HKLM\System\CCS\Services\LanManWorkstation\Parameters\KeepConn=65535
Value : KeepConn REG_DWORD 1 to 65535 seconds
Default: 600 (10 minutes)
The value of KeepConn specifies the maximum amount of ime that a connection can be left dormant.
Note:
Windows 2000 processes the KEEPCONN registry key differently than Microsoft Windows NT 4.0, and permits the connection to the target server to time out.
The red x is by design to save resources. The network drives are not connected until they need to be used. Some applications cannot handle the delay in reconnecting. If your application is having an issue, you may consider disabling autodisconnect per the intructions below.
Sometimes network drives still get disconnected even with autodisconnect disabled. Usually this is caused by third party software or drivers (a/v software, network card agents, etc).
IF you are using applications that cannot automatically reconnect network drives, you can disable the autodisconnect behavior on either the server or
client side by changing the following registry keys:
On the server:
HKLM\System\CCS\Services\LanManServer\Parameters\Autodisconnect=0x0000FFFF
Note: The preceding entry must be located on the computer that offers the share or shares.
The valid value range if you edit the LAN Autodisconnect parameter in the registry is 0 to 4294967295 0xffffffff). For a Windows 2000 Server in a Domain, running either as a domain controller or as a server, the maximum value is 65,535 (0xffff). Values set above this will be returned to 0xffff after policy refresh. Windows 2000 Servers in a Workgroup may be set to any value as indicated.
On the client:
HKLM\System\CCS\Services\LanManWorkstation\Parameters\KeepConn=65535
Value : KeepConn REG_DWORD 1 to 65535 seconds
Default: 600 (10 minutes)
The value of KeepConn specifies the maximum amount of ime that a connection can be left dormant.
Note:
Windows 2000 processes the KEEPCONN registry key differently than Microsoft Windows NT 4.0, and permits the connection to the target server to time out.
- Thread starter
- #7
OK, dropped.
But I have found issues in the cable plant, and what I always though were bullet-proof: a switch port, that can lead to this.
Check your autonegotiation settings for the workstation as well. I wrote all I know about the issue, a complicated one, in the first paragraph of FAQ: faq779-4017
Do not dismiss the notion it could be a bad NIC in the machine. In the last two years they seem, at times, to act like light-bulbs. You need to replace them every once in a while.
Best,
Bill Castner
But I have found issues in the cable plant, and what I always though were bullet-proof: a switch port, that can lead to this.
Check your autonegotiation settings for the workstation as well. I wrote all I know about the issue, a complicated one, in the first paragraph of FAQ: faq779-4017
Do not dismiss the notion it could be a bad NIC in the machine. In the last two years they seem, at times, to act like light-bulbs. You need to replace them every once in a while.
Best,
Bill Castner
- Thread starter
- #9
- Status
Similar threads
