I am running a linux server (slackware flavor) and have a couple of printers attached to the network via jetdirect print servers. A couple of weeks ago, one of the printers stopped responding to print requests. Started the troubleshooting with the physical print server (170x) with HP, and they replaced the unit. Got the new unit, felt happy, plugged it in, and got the same problem.
Snooping the system, I get the following
with PING (DOS version):
Req. timed out
Req. timed out
Reply from XXX.XXX.161.32: Destination host unreachable
(above IP= gateway for my subnet, printer on
another (XXX.XXX.160.32)
Req. timed out
(Meanwhile, I can hit the other printer that is on the same part of the network as the problem printer.)
I don't see much via syslog (except that for a bit I had it hooked up on the wrong subnet...) or the messages log.
Anybody have any ideas what's going on here? If something went goofy with the network, I'd have thought it would have taken out the other printer as well.
One thing I've done that is probably totally unrelated is that I've tried to set up automatic printer driver download for our windows machines. This particular printer wasn't included in my rather aborted attempt at this (if anyone has any ideas on this, I'd appreciate it). Don't think it has anything to do with it, but it all happened roughly the same time (within a week or two).
Thanks in advance,
Hobbes
--"Order is for idiots, genius can handle chaos"
Snooping the system, I get the following
with PING (DOS version):
Req. timed out
Req. timed out
Reply from XXX.XXX.161.32: Destination host unreachable
(above IP= gateway for my subnet, printer on
another (XXX.XXX.160.32)
Req. timed out
(Meanwhile, I can hit the other printer that is on the same part of the network as the problem printer.)
I don't see much via syslog (except that for a bit I had it hooked up on the wrong subnet...) or the messages log.
Anybody have any ideas what's going on here? If something went goofy with the network, I'd have thought it would have taken out the other printer as well.
One thing I've done that is probably totally unrelated is that I've tried to set up automatic printer driver download for our windows machines. This particular printer wasn't included in my rather aborted attempt at this (if anyone has any ideas on this, I'd appreciate it). Don't think it has anything to do with it, but it all happened roughly the same time (within a week or two).
Thanks in advance,
Hobbes
--"Order is for idiots, genius can handle chaos"