Re: cups prints only on reboots -- solved (firewall present)
Firewall prevented new reserved addresses (10.55.1.* and 192.168.*.*),
although it still allowed former standard IP addresses on printers.
Rather than roll with my own iptables firewall script;
on this new computer, I had used the firewall "firestarter".
I had forgotten that I even installed a firewall,
which I had installed to maximize security and minimize my footprint on
our network (ducking and covering).
So that our administrators wouldn't pry my Linux computer from my
"cold dead fingers", I had added a firewall.
I was hoping to pre-empt any complaints about my use of Linux.
My firewall was more against our organization,
since our organization has its own firewall
against the internet universe,
so I had de facto two firewalls in series.
Network IP changes that tripped me up
came with numerous other computing changes as
our administrators moved away from Novell to Microsoft,
firming even more a Microsoft-centric base.
The needed correction was done to firestarter's firewall
configuration GUI by unclicking
"Block traffic from reserved addresses on public interfaces"
so I could use our printers that had IP addresses 10.55.1.*
I might have more quickly seen this problem,
since as my computer booted up,
accumulated/unprinted print jobs would suddenly print.
This happened because my booting computer must have started cupsys print services
before the firewall fully ran.
On Tue, May 08, 2007 at 03:35:16PM -0700, Andrew Sackville-West wrote:
> On Tue, May 08, 2007 at 04:27:47PM -0400, Jameson C. Burt wrote:
> > When I print a file (test file has only 4 characters),
> > CUPS does not print.
> > However, whenever I reboot, CUPS will print all jobs,
> > clearing the CUPS job queue.
> >
> > I can repeat this by creating new print jobs.
> >
> [...]
> >
> > Printing worked fine before our Microsoft administrators decided to
> --------------------------------- ^^^^^^^^^
>
> well, *there's* yer problem.... sheesh...
>
> change all printers from standard internet IP's (199.129.207.*)
> > to reserved addresses (10.55.1.*).
> > I changed my computers IP address and the printers' IP addresses.
> > Indeed, I eventually removed all printing packages and reinstalled them.
> >
> > It's possible our administrators also added filters,
> > but I get the following nmap results
> > PORT STATE SERVICE
> > 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
> > So the ports appear to be open,
> > and besides, Debian is printing when it reboots.
> >
> > I run Debian version
> > 4.0
> > with the following two packages installed
> > cupsys 1.2.7-4
> > cupsys-driver-gutenprint 5.0.0-3
> > and no *foomatic* packages.
> >
> > Any ideas, so I needn't reboot to print?
>
> well. first. have you tried restarting cups as an alternative to
> rebooting?
>
> /etc/init.d/cupsys restart
>
> this would tell us whether to look at cups or at some other part of
> the system.
Reply to: