I installed a new server: Windows 2003 Server, using Active Directory. Clients are all WinXP Pro. At each workstation, I mapped drive P: to point to the accounting data on the server. Everything was working fine. A few days later, I did the Symantec Client Security upgrade as a managed system with the Symantec Security Console. A day later they called me back to say that they were unable to access the accounting data. I went to their office and found that the Peachtree message was saying that drive P: was unavailable. Using Windows Explorer, I searched for drive P:, found it - and then Peachtree worked. This has happened several times on various workstations, and has shown up with other drive mappings that seem to be disconnected from the application's point of view, but you can explore the mapped drive, and then the application works again.
1) I don't know if it's related to the Symantec Client Security upgrade, but I wanted you to have all of the info that may be relevant.
2) In the drive map dialogue window, "Reconnect" is checked.
So, how do I make the drive mappings "stick?"
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!