Tuesday, July 27, 2010

Delayed write failure - tracking down the cause

We're being forced to migrate to newer and "better" versions of Windows Server.  Our brand new spiffy Windows 2003 file server is making me miserable.  First the permissions work slightly differently... which caused 40 minutes of down time as I watched all of them get reset. Now we get "delayed write failure" messages on our XP workstations.

It turns out that Microsoft decided that any task can be completed in 15 minutes flat... and built that timeout into the file server.  There is an easy way to disable it..

net config server /autodisconnect:-1

This tells it never to disconnect a user... which is as it should be.


No comments: