Losing network connections (red x's in file explorer)
Easy 300 points if appropriate solution is found before Friday. Thank you in advance!
Situation:
I have five computers connected via a 3COM 16 port 10/100 hub. 4 computers each have a shared folder which the 5th computer connects. In other words, only the 5th computer connects to each of the shared folders on the other 4 computers. Hardware/software wise, all 5 computers are identical.
OS: Windows 2000 Pro SP4, Supermicro Dual Xeon boards, 512mb memory
Problem: After 15 minutes of inactivity, the network connect to each of the 4 computers is lost. This can be observed from file explorer where each connection displays a red "x" beside the drive letter. By clicking on each one, the connection is immediately re-established again. This is a problem because the 5th computer has a program that needs to retreive data from each of the 4 computers (C++ program that opens a database on each). This program fails because it can no longer see the drives.
I've tried the suggestion: [HKEY_LOCAL_MACHINE\SYSTEM
"autodisconnect"=dword:fff
Considerations:
- as a 'bandaid' solution I could create a keep-alive problem that shells out and performs a dir every 14 minutes or so
Is there another solution?
Any thoughts?
Situation:
I have five computers connected via a 3COM 16 port 10/100 hub. 4 computers each have a shared folder which the 5th computer connects. In other words, only the 5th computer connects to each of the shared folders on the other 4 computers. Hardware/software wise, all 5 computers are identical.
OS: Windows 2000 Pro SP4, Supermicro Dual Xeon boards, 512mb memory
Problem: After 15 minutes of inactivity, the network connect to each of the 4 computers is lost. This can be observed from file explorer where each connection displays a red "x" beside the drive letter. By clicking on each one, the connection is immediately re-established again. This is a problem because the 5th computer has a program that needs to retreive data from each of the 4 computers (C++ program that opens a database on each). This program fails because it can no longer see the drives.
I've tried the suggestion: [HKEY_LOCAL_MACHINE\SYSTEM
"autodisconnect"=dword:fff
Considerations:
- as a 'bandaid' solution I could create a keep-alive problem that shells out and performs a dir every 14 minutes or so
Is there another solution?
Any thoughts?
ASKER
HUB has been changed and I neglected to note that this problem is occuring on another identical system; although I haven't actually had a chance to see this one yet.
In addition, it seems that the problem began from first day (they are all new).
In addition, it seems that the problem began from first day (they are all new).
To change the default time-out period for the autodisconnect feature of the Server service, open a command prompt, type the following line, and then press ENTER
net config server /autodisconnect:number
where number is the number of minutes that you want the server to wait before it disconnects a mapped network drive. The maximum value for this command is 65,535.
To turn off the autodisconnect feature, open a command prompt, type the following line, and then press ENTER:
net config server /autodisconnect:-1
net config server /autodisconnect:number
where number is the number of minutes that you want the server to wait before it disconnects a mapped network drive. The maximum value for this command is 65,535.
To turn off the autodisconnect feature, open a command prompt, type the following line, and then press ENTER:
net config server /autodisconnect:-1
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you tried to specify a UNC path instead of using a mapped drive?
try to extend the time not to disable autodisconnect
ASKER
f_umar: - I had already stated that I've tried "net config server /autodisconnect" - I had originally attempted using 65535
Nzarth: Good idea, I'll check
oBdA: That will not make a difference in this situation
Nzarth: Good idea, I'll check
oBdA: That will not make a difference in this situation
Look in your device manager select your network card there is a tab for power management on this tab there is a check box for "Allow computer to turn off this device to save power" if checked uncheck this box. and make the the one "Allow this device to bring the computer out of standby" is checked.
when a network connection goes to "sleep" in w2k it should wake up if the box is called by another on the network... if the hardware is be powered off, IE the network card.. Windows does not know to wake it up.
The autodissconnect is for saving bandwidth and just "sleeps" the connection.
if the os is putting the device to sleep for power savings the setting for autodisconnect will have no affect on it. When you activate the hardware by clicking on the drive.. the OS powers it up... it does not know to do that on incoming requests.. so they are ignored.
Make sure your hardware is awake all the time and the autodisconnect should not be an issue.
I hit shares on computers that have been in-active for sometimes days and the connections are asleep.. and they respond.. so not sure the autodisconnect is what your problem is.
when a network connection goes to "sleep" in w2k it should wake up if the box is called by another on the network... if the hardware is be powered off, IE the network card.. Windows does not know to wake it up.
The autodissconnect is for saving bandwidth and just "sleeps" the connection.
if the os is putting the device to sleep for power savings the setting for autodisconnect will have no affect on it. When you activate the hardware by clicking on the drive.. the OS powers it up... it does not know to do that on incoming requests.. so they are ignored.
Make sure your hardware is awake all the time and the autodisconnect should not be an issue.
I hit shares on computers that have been in-active for sometimes days and the connections are asleep.. and they respond.. so not sure the autodisconnect is what your problem is.
Why won't UNC path not make a difference?
Make sure you make the power changes to all of the machines.
Make sure you make the power changes to all of the machines.
averyb
The UNC path would not make a difference if the NIC is powered down... it is an incoming request that can't be seen.
The UNC path would not make a difference if the NIC is powered down... it is an incoming request that can't be seen.
ASKER
Thank you to everyone and especially Nzarth for seeing through to the most obviously and simple solution. Clearly an beautiful example of Occam's Razor!
With power management turned off, everything looks good (well so far anyway!) Now I'll go slap myself with a wet noodle.
Thank you again!
SDC
With power management turned off, everything looks good (well so far anyway!) Now I'll go slap myself with a wet noodle.
Thank you again!
SDC
ASKER
>I hit shares on computers that have been in-active for sometimes days and the connections are asleep.. and they
> respond.. so not sure the autodisconnect is what your problem is.
They sure do, that is, from within File Explorer but in my situation, the software was attempting to write to a shared folder. The software erroneously believed that the network share was down and failed its write process.
> respond.. so not sure the autodisconnect is what your problem is.
They sure do, that is, from within File Explorer but in my situation, the software was attempting to write to a shared folder. The software erroneously believed that the network share was down and failed its write process.
Do you have a spare one?