Open File and User lockups

[paleogryph]

I maintain a NW5 SP6 server that has occasional problems that usually lead to rebooting the server as the only recourse. One user in particular (XP Pro) will sometimes open files on the server, and this will cause not only his pc to lock, but anyone else who tries to access files in that volume. If I try to delete his connection from the server using monitor, nothing happens, and it shows they are still logged in. Then it cascades into everyone who is logged in having problems, which at that point we usually reboot the server.

I changed the hdd, ram, nic and reloaded XP for that user and that seemed to fix those issues and everything has been fine for months.

However, today, another user who has never had problems was pasting into a Word file on the server when his W2k pc locked. He shutdown, and we saw those files still open on the server and we couldn't kill his connection. Then everyone else started having problems also, leading to a reboot of the server.

Another strange thing, the open files listed under this user showed the desktop.ini of that first user I mentioned, the one with XP. Why would this open file be listed under a different users open files?



>Think for yourself<
...or someone else will do it for you.

 

[tclowe123]

Have you tried to turn off the file caching at the local machince under the advanced settings tab and also on the server?

 

[spi200]

Hi

I Have not seen this problem, but make sure your on the latest client with its patch. We run client 4.83 sp2 with the 2e update added as well.


Regards


David

 

[TheLad]

The only time I have seen this problem is when File Caching is on (it is on as default) as already mentioned.

To switch File Caching off on the server, do to the console and type: SET FILE CACHING ENABLED = OFF

You will also have to add that command into the AUTOEXEC.NCF so when the server reboots it sets the setting to off

-----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------

 

[Jontmke]

HEHE, I was wondering when you would see this TheLad. You should have this response in a special file so you can cut and paste to save time. I was going to say this but did not want to steal your thunder.

Jon

There is much pleasure to be gained from useless knowledge. (Bertrand Russell)

 

[TheLad]

Unfortunately my cut and paste did not work, I should know this command off by heart but it is actually:

SET CLIENT FILE CACHING ENABLED = OFF

I know I always harp on about file caching but it is such a pain in the ar5e with it on, it's just not worth it!

Jontmke - ya cheeky sod

-----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------

 

[paleogryph]

Ok, I tentatively discovered the problem.

Last week I installed PopMessage (IM client) on several MS pc's to let users test it out. Everyday that those clients were in use was a day the server crashed. Strange but true. Clients are no longer in use, no more problems since then (5 days and counting)...



>Think for yourself<
...or someone else will do it for you.

 

[marvhuffaker]

Novell has a cool Instant Messenger bundled with GroupWise 6.5. You should take a look at it if you're installing instant messengers to use for corporate communication. It uses credentials from eDirectory, and you can SSLize it so everything is encrypted and secure. Plus the messenger server is on one of your servers, so nothing has to go out over the internet to pass messages. Very nice.

Marv

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com