Bug#353879: open ports on the printer, please?
On Tue, 25 Apr 2006, John-Paul Stewart wrote:
> 21/tcp open ftp
> 23/tcp open telnet
> 80/tcp open http
> 280/tcp open http-mgmt
> 443/tcp open https
> 515/tcp open printer
> 631/tcp open ipp
> 9100/tcp open jetdirect
Heck of a printer server, that. Try talking IPP directly to it, it might
help. Note that this effectively means no hplip support, as hplip will want
to use the jetdirect protocol.
> I haven't had a chance to try that version yet. However, I did have
> occasion to try the printer with a Win2K system the other day. The
> Win2K drivers and utilities on the CD-ROM that shipped with the printer
> couldn't detect it over the network either. So it seems it is the
> printer itself, not the software.
Print out the setup page for the print server, and see if it is correctly
configured. These things have a lot of knobs, and if one is turned the
wrong way, it can behave rather strangely. Also, check for firmware
updates.
> I still find it odd that the printer works fine when configured in CUPS
> as a generic PostScript device using the LPD protocol, but not with the
> HP specific stuff. Oh well, there's not much that can be done about that!
Printer server oddities, apparently. Maybe the jetdirect channel ain't
really enabled, while the lpd one is.
> Thanks for your help, anyway. Sorry to have wasted your time on what is
> now clearly not a Debian bug.
No problem. I will keep this bug open for a small while yet, just in case
you find out more. We might want to forward something upstream, or to add
documentation about it.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: