Discussion Locked

Windows 2000 Pro on a Windows NT 4.0 Dom

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Running Windows 2000 Pro SP2 on a Windows NT 4.0 Server SP6a network and mapped drives keep showing an X through the drive. Before installing SP2 on the W2K Pro, it would give an error that the drive was busy or in use. As it stands now, we are only running TCP/IP on the Domain and it doesn't seem to affect anything, but the X continues to show up. Has anyone encountered this problem and know what I can do to fix this problem? I have searched Technet, time and time again with no luck.

5 replies

by saihib

This happens when users fail to log off before a certain amount of time has elapsed. It's a policy setting. For example, where I work, after 8 hours of inactivity on a machine that a user is logged on to, the connection (mapped drives) is terminated, resulting in the red Xs you see in My Computer. It's harmeless. Double-clicking on the mapped drive restores the connection. If you want to stop seeing red Xs either tell your users to make sure they log off or change the policy.

by coucha

I thought I answered this the last time I logged in and answered the guy below you. Guess I can only answer one at a time. Anyway, I do not have a policy running on my network, although by default W2K applies a policy of after 15 minutes of inactivity, disconnect. I changed that to 480 minutes, but still after a short time an X pops up on the drive. I know it doesn't hurt anything, more of a nuisance than anything, but I would like to stop this from happening to avoid people from asking, "why does this show up?". When the X is present, it slows down windows explorer on people. Since you gave me sort of what I was looking for I am giving you the points, but I would still like to get a better answer.

by tweested

This is a comment not an answer:

We're seeing the exact same problem in the same setting with a few more protocols thrown into the mix. But, in addition, the x'ed drive when selected often does not reconnect. Yet, 10 minutes later, the drive is connected again with no X. Yes, it's driving me buggy too!

by coucha

If you are in a mixed environment, which I am in also using IPX and IP, but the IPX is not bound to Clients for Microsoft Networks. This may help you a little, if you are running Novell with IPX and NT with IP - right click on My Network Places andgo to properties. Highlight Local Area Connection and go to the Advanced Menu above and select Advanced Settings... This gives you the opportunity to select your bindings with the protocols being used. It has helped me by delaying the "X" from showing up sooner. Installing Service Pack 2 seemed to help too. Hope that helped you!

This discussion is closed to new replies.