Disconnected mapped drives in XP Pro
I have a strange problem with drive mappings. We run Windows XP with SP1 on all our PCs. We have drive mappings that go to a 2003 SP1 file server for all the users. Occasionally, a few times a month, users will turn on their PCs, try to open Outlook (which opens PST files stored on one of their drive mappings), but Outlook fails to open and gives them an error about not being able to open the set of folders, or expand the folder. If you go to My computer and look, the drive mappings show a status of disconnected. If you double-click on them, they re-connect without a problem and then if you open outlook, everything works great. So my question is, why does this happen, and not for everyone just a handful of people, and how can it be fixed? I have never experienced this issue, and I have a laptop which connects to various networks all the time docked and undocked, etc. Yet some of the PCs in the office who are always on the same network, exhibit this problem. The server is brand new with no errors or mis-configuration, all the desktop PCs are pretty much the same, same config, same software. Any way to fix this issue or find a way to work around it without having to manually double-click on each drive mapping every time this happens to re-connect manually?
Ahh, I forgot to mention, the /delete flag will let you remove the existing connections from your batch file.
ASKER
My company does not use logon scripts or batch files for mapping drives, because we have a complex environment, involving remote clients, Citric connected users, VPN users, etc. The servers are always on and are connected to a power protected system which maintains 100% uptime. The PCs are on this same network and are shutdown every night. There is no disconnection that I can find, and the server is not reporting any issues or errors or anything. This is more of a neusance than anything, and something I can't find an explanation for.
ASKER
I am familar with batch files, and have used them heavily in the past, just can't at this company.
It sounds like your configuration is a bit unusual.
For starters, is there any compelling reason why you have decided to avoid installing SP2 on the Windows XP machines? It was released 2½ years ago, and Microsoft no longer provides support to SP1 machines. That means you don't apply any type of operating system updates or patches, correct?
http://www.microsoft.com/windows/support/endofsupport.mspx
Additionally, Microsoft's official stance is that they do not support the use of PST files over a LAN connection, because it can be problematic...
http://support.microsoft.com/default.aspx?scid=kb;en-us;297019
For starters, is there any compelling reason why you have decided to avoid installing SP2 on the Windows XP machines? It was released 2½ years ago, and Microsoft no longer provides support to SP1 machines. That means you don't apply any type of operating system updates or patches, correct?
http://www.microsoft.com/windows/support/endofsupport.mspx
Additionally, Microsoft's official stance is that they do not support the use of PST files over a LAN connection, because it can be problematic...
http://support.microsoft.com/default.aspx?scid=kb;en-us;297019
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
MCP: I'm not sure how having a "complex environment" in any way precludes using scripts or batch files, but it really is the easiest solution, especially if you use any form of central management of domain computers, at least IMO. I understand every company is different and you obviously understand your situation far better than I do.
That aside, of the few times I've seen this happen on domain computers, it was usually due to:
1) The computer (laptop here) picking up a wireless internet signal and automatically connecting
2) The server restarting overnight due to patch upgrades
Sorry not to be of more help.
That aside, of the few times I've seen this happen on domain computers, it was usually due to:
1) The computer (laptop here) picking up a wireless internet signal and automatically connecting
2) The server restarting overnight due to patch upgrades
Sorry not to be of more help.
ASKER
SP1 is on the servers, not the XP machines, XP desktops are all SP2.
Sorry about that, but when you said "We run Windows XP with SP1 on all our PCs" in your original post, I took it at face value.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Apologies, I just noticed cjtraman posted the same one above. Let us know if that helps.
ASKER
Oops, I meant SP1 for the servers, not XP, sorry. I mis-typed it.
I'll try the above link and see if that helps.
I'll try the above link and see if that helps.
ASKER
I just used the link provided to disable the auto disconnect, I'll let then run a few days and see how it goes. It sounds reasonable as an explanation, but doesn't explaint why only a few users are affected and not everyone. Thanks for the link!
ASKER
So far so good, thanks for the link!
And yes, you can fix this issue by just removing and remapping your network drives every morning with a batch file:
net use driveletter: location will do what you're looking for on mapping it, e.g.
net use h: \\192.168.1.151\folder
You can also use the persistent flag as off if you want to have em redone whenever you log back in.