File Print Server

On four separate occasions over the past six weeks we've had a problem with our networked printers, simply put...the printers stop working. I want to emphasize this problem has caused no inconvenience for the public. Why? mainly because the fix is quick and easy. When the problem occurs we immediately call the Secretary of State's IT Department and either they or we boot the "file/print server". But the simplicity of the fix does not make the problem any less serious.

The first time we experienced the problem the SEC IT Department speculated that the memory in "print server" was full (booting empties the cache). Even though the problem has reoccurred three addition times since this hypothesis, memory over-load may still actually be the problem...but why? Why is the memory filling?, determining this is complex.

This morning our printers shut down again...This time a diagnosis of the server revealed a possible IP address conflict. Our MIS Director immediately resolved that issue.

I want to reiterate, this problem has not caused any interruption in our operation or inconvenience for users. I'll continue to keep you current on the issue.