XP client keeps files open on nework

[Dan W]

I have one XP(SP1) client that frequently causes this problem: After
using a file from a Win2000 server shared drive, the user at this
client closes the file normally. There are no errors when the file is
closed and everything appears normal at the client, however the server
still shows the file as open by that client: no one else on the
network can access or delete the file (not even the user that the
server says has the file open) until I go into Computer Management at
the server and close the file myself.

This only happens from one XP machine. I have many other XP(SP1) boxes
that never cause this problem.

This happens from many different applications from this one machine -
Word, Outlook, and even non-MS applications - so I don't believe it's
an issue with an application.

Any suggestions?

 

[Kevin]

This is only the beginning of your problems. I'm looking through the group
right now to see if there is a solution but anyone that is using Windows XP
on a Windows 2000 network beware you in for huge problems. Here is what I'm
seeing and Microsoft sucks at try to resolve this. It has already cost me
$250 and the issues comes right back.

1) Users will start to have problems saving files. SP1 for some reason
locks the files on the server for read only mode. The only thing the person
can do is save the file to a new file name. Then go back literally one
second later and delete the file, of which they now for some reason have
access to!
2) Computers will have numerous USERENV errors in there logs. Symptoms are
the logon scripts takes for ever to run (if it does) policies take upwards
of 15-30 minutes to apply (if ever) and no this is not just for remote
users. I'm on a two computer network and it took me 30 minutes to log into
my server this morning.
3) Users that have persistent drive mappings will see a red X on there drive
and when they try to click on the drive it may or may not connect to the
server.
4) Users that access Micro$oft Exchange my see that their cached
information (user name, domain and password) disappear on them.
5) They wont be able to print to network printers because they might not be
getting signed onto the server.
6) Domain policies error out or do not apply at all.

If anyone sees similar problems let me know I have tried everything and
thought this was a done deal two weeks ago and BAMM everything started again
two days ago. Now of course Micro$oft wants another 250 from me to resolve
this, I think not!!

Kevin