Discussion Locked

Win2k Pro - net drives disconnect immed.

0 helpful
25 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

When a windows 2000 professional workstation logs onto the windows 2000 server, the login script runs, but when you go into my computer, all the network drive mappings have red x's in them indicated they are disconnected. This happens immediately upon login. If you click on the drives, they reconnect and stay connected for the rest of the day.
Any ideas?

25 replies

by dklippert

Try running one of these commands at the workstation. Hopefully one of them should work.

"net config server /autodisconnect:-1"

"net config server /autodisconnect:65535"

"net use J:\\servername\sharename /persistent:yes "

by dklippert

I don't want to make any assumptions. Have you looked at this article?
Type the Q number in the search box at technet.microsoft.com.

How the Autodisconnect Works in Windows NT

Q138365

by yasirs

Hi,

When u mapped these drives did u check the "reconnect and logon option" ? if u did it should reconnect easily with out hassle. Also the user name and account should have the ability to use the over the net share.

Now for the other probs that might be if u login before the PCs where the mapped drives are located you will not be able to reconect to them at that instance or if your network is slow it will require a bit more time to reconise that you have a network share on the network etc.

to disconnect always press ALT+CTRL+DEL keys b4 leaving its the safest way.

by slogmeister

The drives are being mapped from a logon script. Reconnect at logon is not an option. Besides, the drives are being connected and then immediately disconnected. I see red X's. If I click on the drive, it comes right up, but things like Outlook, can't handle it.

by legj1

Windows 2000 will disconnect LAN sessions when not in use. This setting is found in the registry...and yours must be set very low to "X out" that quickly. Check it out:

You can find the LAN Autodisconnect parameter in the registry under the subtree
HKEY_LOCAL_MACHINE under the subkey:

\System\CurrentControlSet\Services\LanmanServer\Parameters

Purpose: The function is to disconnect idle sessions after a set number of
minutes. The number of minutes can be set at a command promptusing the Net
Config Server command. For example, to set the Autodisconnect value to 30
minutes:

Net Config Server /autodisconnect:30

The valid value range is -1 to 65535 minutes at the command line.

To disable Autodisconnect set itto: -1

by slogmeister

I already did that. It didn't work. I was REALLY hoping it would, but that's why I posted this question, because it didn't. Thanks, tho.

by estebandelatorre

It's a setting that's speeds up the login time connection by not mapping the drives letters until they are needed.
This feature start in win95, under microsoft client/properties, you have the chance to perform a fast login option and a (slow) login & restore network connections.
Once you refresh the tree, all the connections will be ready to use.

Hope it helps!!!

by slogmeister

Ok, what about in Windows 2000? This problem only seems to manifest when I'm using Win 2k pro to a Win 2k server.

by ann777

Actually, answer #1 is correct, but it needs to be done on the server, not the workstation:

Q297684

To resolve this behavior, use a command to change the default time-out period on the Windows NT Server 4.0 or Windows 2000 Server: At a command prompt, type: net config server /autodisconnect:30 .

The valid value range to configure this setting from a command line is from -1 through 65,535 minutes. To disable Autodisconnect, set it to -1 .

NOTE : This step must not be confused with the remote access Autodisconnect parameter that is turned off if you set it to a value of zero (0).

If you set Autodisconnect to zero (0), this setting is not turned off and after a few seconds of idle time very fast disconnections can occur.
For additional information about increasing the default time-out period, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Q138365 How the Autodisconnect Works in Windows NT

Q128167 Server Service Configuration and Tuning

by slogmeister

Ok, a couple of things:

1) It is definitely only Win 2k to Win 2k
2) Sometimes they disappear again
3) Only applications have a problem accessing the disconnected drives. Exploring to them works fine, even with the red x.
4) I've tried the autodisconnect thing, and it doesn't work.
5) What nitwit at Microsoft would think up such a moronic thing as autodisconnect anyway? Ok, that's rhetorical.

Thanks for all the input. I haven't given up yet.

- Jason

by maxwell edison

I have a couple of thoughts on this issue. And, I've experienced myself as well. Look at this link:

http://www.uwgb.edu/helpdesk/docs/rollout2000/Windows2000Changes.pdf

(REMOVE SPACES from the pasted URL)

It states that this is simply a characteristic of Windows 2000 - that the red X will appear until the networked drive is accessed and/or if that networked drive hasn't been accessed for a while. (Whatever "a while" is?) And, I have indeed seen that this is the case in many (but not all) installations.

Another report: "The Red X – If you have not accessed a network drive in a significant period of time, you may see a Red X over the drive icon when you open Windows Explorer. To re-establish this network connection, simply double-click on the icon."

See at:

http://www.iup.edu/helpdesk/service/pc/software/w2kpro/differences.shtm

However, I had this happening on one of my workstations until I stumbled upon something interesting. I had installed a network cat5 cable static surge supressor. This was one of those in-line devices manufactured by APC. When the device was removed, the problem went away. On the other Windows 2000 installations where the network cable was routed through a more traditional protection source (through the UPS, for example) the problem never appeared in the first place.

Interesting indeed.

Maxwell

by maxwell edison

.
.
Another interesting possibility:

"Fallacious red X - Windows 2000's My Computer may display a drive letter created with Subst as a disconnected network drive marked with a red letter X, although you can in fact access the drive (see Q269163)."

See at:

http://iwsun4.infoworld.com/articles/op/xml/01/05/28/010528oplivingston.xml

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q269163

Another link that discusses the issue:

http://www.unf.edu/compserv/helpdesk/w2k/(REMOVE SPACES from the pasted URLs.)

By the way, I've also seen where the problem went away once Service Pack 2 was installed.

Good luck,

Maxwell

by ysamala

check the lmhosts file in c:/winnt/system32/drivers/etc/
it shud have ur network drive mappings and also their ip's else u will have this problem.
good luck

by trent.mitchell

Have you tried deleting the mapped drives then remapping them in the log in script ? I tried that worked for me.

net use w: /delete
net use w: //server/files

Good luck.

by slogmeister

I forgot I still had this question open. I don't work for the company that had this problem, so I really don't care anymore.

This discussion is closed to new replies.