Don't use mapped drives. Mapped drives are a thing of the past, they date
back to the old DOS Clients and rubbing two sticks together to start a fire.
Using a network path is always better than a mapped drive. Mapped drives
have a timeout that disconnects after a period of inactivity. Nework paths
are a different animal and do not have this issue.
An application designed to run on a network should never need mapped drive.
But I am only shooting in the dark since I have no idea what App you are
running and how it was designed.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Tim Bott" <(E-Mail Removed)> wrote in message
news:48D612DD-0A33-42AE-B8FB-(E-Mail Removed)...
> Some employees who are accessing the central contact management program
> through a shared folder on our 2K3 server can't stand the fact that they
have
> to re-enter their passwords on the mapped drive to access it. They have
to
> do this once a day, usually, and it will work for the remainder of the
day.
> All users accessing this shared folder have their own local username and
> password on the server, and that is what they use to connect to the mapped
> drive on their local XP Pro machines.
>
> How do I set up the server or clients so that it keeps this connection
alive
> at all times?