Have a Windows Server 2003 R2 setup as a file/print server. We have 3 subnets on our LAN interface through two router ethernet ports. All clients on the main subnet were server is located have no problem at all when submitting print jobs to printers, this includes clients on the second subnet which is interfaced as the primary subnet on the second ethernet port.
However, clients on the third subnet which is interfaced as the secondary subnet on the same ethernet port as the second subnet have a priting issue.
When cleints on this subnet forward print jobs, the job is spooled then an error status is displayed on the print job window. These jobs will only be cleared after a continuos ping command is initiated to this particualr printers or the print spooling service is restarted.
It seems to me that the printer has to be kick started/awoken in order to accept any print jobs.
I have not a single clue as to what could be the possible cause as LAN connectivity to this devices aren’t an issue.
Please assist.