Users on Server 2003 / Active Directory Can Not Access Shared Folders

My company recently switched our network over to Active Directory on
Windows Server 2003. Our client machines are all XP Pro. On our
network we have a machine with what we call Private Shares (folders
set up for access by an employee and their manager). Ever since
switching to AD, at least once a day some of our users lose access to
their shared folders. It is not the same users, it happens randomly.
The thing that does not make sense is that a user can be accessing the
folder all day long and then all of a sudden they try to get in and
receive a message that Access is Denied or You Do Not Have Permission
To Use This Resource. Having the user reboot their machine clears up
the issue, however, user having to reboot continuously is not a
feesible option here. Does anyone have any idea what could be causing
this? Any information is appreciated.

Can you ping the shared server when that happens?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> My company recently switched our network over to Active Directory on
> Windows Server 2003. Our client machines are all XP Pro. On our
> network we have a machine with what we call Private Shares (folders
> set up for access by an employee and their manager). Ever since
> switching to AD, at least once a day some of our users lose access to
> their shared folders. It is not the same users, it happens randomly.
> The thing that does not make sense is that a user can be accessing the
> folder all day long and then all of a sudden they try to get in and
> receive a message that Access is Denied or You Do Not Have Permission
> To Use This Resource. Having the user reboot their machine clears up
> the issue, however, user having to reboot continuously is not a
> feesible option here. Does anyone have any idea what could be causing
> this? Any information is appreciated.
>