OK here's the scenario:

FMS8 on windows 2003, 2 NICs, one for all of our internal FM workload, and one that goes directly to our Apache Server for the web publishing engine(the one to our WPE is on it's own subnet with the Apache server so we shouldn't be getting any conflicts there)

when we try to use the FMS backup scheduler to do a backup at noon, about two thirds of the files come back as delayed write failure, but we run a nightly as well that runs to the same place on the server("night" folder instead of "noon") and that works just fine.

the backups run to a shared drive on a fairly new compaq Prolient server(windows)

Anybody have any idea as to why the noon ones would fail but the night ones would run fine? And then, how do we get the noon ones to run correctly?

all of the fixes I have found seem to say the issue that was a problem in windows server 2000 was fixed for windows server 2003.

The easiest solution is not to backup directly to a shared drive. Backup to the local hard disk and then use Windows OS scripting to zip the backup and move it to the shared drive. Much more reliable. Check out the downloads section on my website (www.connectingdata.com) for the backup white paper.

I have read your white paper, and it all makes sense, my question still remains: why do the noon ones fail while the night ones do not?

no idea. Busy network, failing hardware component somewhere. You'd need to do a lot of troubleshooting, system monitoring, event log checking...