| Author |
Win XP Pro mapped drives disconnect
|
|
| goalie13 2004-04-12, 7:02 pm |
| I have another issue I could use some help on. I have 2 XP Pro boxes on a W2K AD domain. I have mapped a drive to a share but after a long time idle (like over night), they disconnect. They never get the red X, just say disconnected in "My Computer". If I click on them and try to reconnect the drives, the computer hangs. If it does not hang, it takes much longer than it should to connect and I get this error message: "could not connect, the device name is already in use".
I have tried to "shut off" Autodisconnect in the registry and also unchecked the box for the NIC that says "Turn off this device to save power" for both the server and the clients.
I have seen this exact issue unresolved using Google. I could write a batch file to disconnect the drive and then reconnect it at a later time as a "work around" but I prefer not to. I would like to know if anyone has had this problem and solved it.
Thanks in advance for any ideas.
 | |
| jkhnwspec 2004-04-13, 2:02 pm |
| Have you seen this article? I realize it does not list XP as one of the OSes, but it might help. Do the users of these systems have any group policy in effect that might be limiting their connection time? | |
| Tekmazter 2004-04-13, 3:22 pm |
| Just in case you do not realize, you need to change the AUTODISCONNECT on the SERVER that is sharing out the resources, not the workstation.
Modifying the workstation side only changes the autodisconnect for machines connecting to it. Not the other way around. | |
| goalie13 2004-04-13, 7:21 pm |
| I had seen that MS article. I set the auotdisconnect time to ffffff. I didn't use the "net use" way, I went into the registry. There is no group policy applied to these accounts that would disconnect an idle session. Thanks for the suggestion though.
I had changed the autodisconnect time on the server. The only reason I changed it on the WS only because changing the disconnect time on the server didn't solve the problem. Thanks anyway.
As I posted before, I'm not the only one having this issue. As of today, I haven't had either WS disconnect this week, but it's still early. | |
| jkhnwspec 2004-04-13, 10:08 pm |
| quote:
Originally posted by goalie13
I had seen that MS article. I set the auotdisconnect time to ffffff. I didn't use the "net use" way, I went into the registry. There is no group policy applied to these accounts that would disconnect an idle session. Thanks for the suggestion though.
I had changed the autodisconnect time on the server. The only reason I changed it on the WS only because changing the disconnect time on the server didn't solve the problem. Thanks anyway.
As I posted before, I'm not the only one having this issue. As of today, I haven't had either WS disconnect this week, but it's still early.
At least it seems like you are making some progress. Keep us posted. | |
| goalie13 2004-04-14, 7:49 pm |
| I finally ended up writing a batch file to disconnect the drive in the evening and reconnect it in the morning before everyone comes to work. This seems to have done the trick.
I would like to know why this is happening or if some setting somewhere within XP or W2K server needs to be changed, but I will live with what works.
Thanks for your help and suggestions. | |
| jkhnwspec 2004-04-15, 6:22 pm |
| quote:
Originally posted by goalie13
I finally ended up writing a batch file to disconnect the drive in the evening and reconnect it in the morning before everyone comes to work. This seems to have done the trick.
I would like to know why this is happening or if some setting somewhere within XP or W2K server needs to be changed, but I will live with what works.
Thanks for your help and suggestions.
Good to see you posted on the solution you found; even if it wasn't the desired solution you sought. Keep looking for it, you are bound to stumble on it someday. |
|
|
|