We have a Brother HL-3170CDW colour LED printer connected to the network via Ethernet, with a static IP address assigned to it.
A Windows XP Professional PC (our print server) has this printer installed using a custom TCP/IP port, sharing it so that it is available for anyone on the network to access.
So far so good.
It works perfectly immediately after it has been installed on the print server.
Unfortunately, the status of the printer's print queue on the print server changes to "Offline" after the print server is rebooted (or after the print spooler is restarted).
The only possible workaround I have found so far is reinstalling the printer on the print server (which only solves the problem until the next reboot of the print server PC). We cannot reboot the print server, without having to reinstall this printer to restore printing capability (although connectivity at a lower level persists).
Other network printers installed on this PC do not have this problem- it is just happening with this particular printer.
Even after a reboot of the print server, it is still possible to access the printer's web interface over the network and to ping the printer. Nothing appears to be wrong with the printer itself- it seems to be an issue with the print server.
We need the print queue's status to always look like this, obviously:
Does anyone have any ideas what is happening here? How can I prevent the printer from showing as "Offline" under "Printers and Faxes" after the PC (or print spooler) is restarted?
So it turns out that the print queue is going into offline mode for some reason (after either a reboot or print spool restart). I never really noticed this option existed with printers before to be honest, and can't see what the point of it is.
Although this can be quickly worked around simply by selecting "Use Printer Online" from the context menu after each reboot (instead of reinstalling the printer as I previously stated), it is still an ongoing problem.
Any ideas would be much appreciated!