Windows Forum

Ask something
Discussion Locked

Network Connection Timeout

0 helpful
7 replies

by briantruitt

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a client who always seems to have their network connections timeout, i.e. red X on Network drives in My Computer. This isn't the normal you have a red X, but can still connect, but rather a working in an application and can't save work to anetwork drive because of the connection to that shared directory has timed out. This doesn't happen to everyone in their 50 user environment, but it does happen to random users in random locations throughout their building. They basically have oneserver running Windows NT 4.0 and we have done all of the little KB tricks and tips for this problem both on the server side and client side. Hopefully, someone out there has run into this before and has a really good tested answer. Thanks ahead of time.

7 replies

by joseph moore

To clarify why I said use -1 for a value, here is a quote from Technet article 138365:

"The valid value range is -1 to 65535 minutes at the command line. To disable Autodisconnect set it to -1.

Setting Autodisconnect to 0 does not turn it off and results in very fast disconnects, within a few seconds of idle time. (However, the RAS Autodisconnect parameter is turned off if you set it to a value of 0.)

If you configure the Autodisconnect option to -1 at the command prompt, Autodisconnect is set to the upper value in the registry. This is approximately 8,171 years (not tested), which should be long enough to be the equivalent of turning Autodisconnect off."

So, using -1 will disable the Autodisconnect feature until the year 10174AD. That should be good enough.

by briantruitt

Sorry it has taken me so long to get back to you gentlemen. We are currently testing both answers out at our clients location. Within two days we should have our results. Thanks for all of your help.

This discussion is closed to new replies.