We have been running a Win2000 active directory network
for 2+ years on Win2000 enterprise edition servers.
Currently we run SP3.

We have recently added XP clients running XP professional
to the network They work well with one exception. When a
file is accessed on the network server a file lock is set
on the server to say this file is in use.

When the file is closed by the client the file lock is not
released. Only when the User logs of the network is the
file lock released. It does not seem to matter if the file
lock is read, change or full control. Once the file lock
exists the system behaves as expected eg cannot delete
files with locks in existance. Change locks stop other
users opening file for modification.

Can anyone suggest why locks opened by new XP clients are
not released. Do I need to run something on the servers to
cope with the new clients.

814112 Files on Network Shares Open Slowly or Read-Only or You Receive an
Error
http://support.microsoft.com/?id=814112

810907 Error Messages When You Open or Copy Network Files on Windows XP SP1
http://support.microsoft.com/?id=810907

If those don't work, there could be 3rd-party software holding the file
locks.

--
Doug Allen
Windows 2000 MCSE
Microsoft Enterprise NT4/Win2k/XP/Win2k3 Setup Support

This posting is provided "AS IS" with no warranties, and confers no rights.


"Darren Ellis" <(E-Mail Removed)> wrote in message
news:06dd01c3a416$fceb7130$(E-Mail Removed)...
> We have been running a Win2000 active directory network
> for 2+ years on Win2000 enterprise edition servers.
> Currently we run SP3.
>
> We have recently added XP clients running XP professional
> to the network They work well with one exception. When a
> file is accessed on the network server a file lock is set
> on the server to say this file is in use.
>
> When the file is closed by the client the file lock is not
> released. Only when the User logs of the network is the
> file lock released. It does not seem to matter if the file
> lock is read, change or full control. Once the file lock
> exists the system behaves as expected eg cannot delete
> files with locks in existance. Change locks stop other
> users opening file for modification.
>
> Can anyone suggest why locks opened by new XP clients are
> not released. Do I need to run something on the servers to
> cope with the new clients.