We had to replace a failing server at a remote location. It is a DC, SQL, and Print Server. Everything is working great. It also has 3 Print queues installed for 2 Xerox Phaser 4400n and 1 Xerox 8200n. Everyone was printing the day after we replaced the server.
Then I had to make a change to the NIC configuration(disable TOE) becuase of a bug in the broadcom firmware. The next morning nobody was able to print. It seems all jobs start to spool and then just stop(example 72.4kb/155kb) and then the printer says offline and the printer panel itself is frozen. If we stop the spooler the printer panels respond again. This happens to all 3 printers. I tried changing the drivers to generic and the same thing happens. we moved the queues to a different server and used the same drivers and it is working fine but this is not a good perm solution.
We reenabled TOE and ran this command(Netsh int ip set chimney DISABLED)(because of this article: http://support.microsoft.com/kb/942861) and reboot and the print problems remain.
We don’t understand why printing was working fine for a day and stopped working the next day. Also we don’t see how this change we made could have possibly affected printing.
Any ideas or suggestions. Disk space on the spooler folder is not a problem. Permissions are all correct. There are no errors in the event log whatsoever. Jobs start to spool then stop, then the printer says offline and we get a communications errors.