[cups.general] Moving a working Suse Linux CUPS PC to a new subnet IP address

[Paul Ortman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul McIlfatrick wrote:
> A few days ago I posted to this newsgroup about not being able to
> access the http://printhost:631/ CUPS admin pages after we had
> moved our fully working Suse Linux PC to a new subnet IP address.
> Printing worked fine after the move.
>
> Today, I moved the PC back to its old IP address. We are again
> able to access the http://printhost:631/ CUPS admin pages and
> printing works!
>
> Our Suse Linux CUPS PC must be moved to the new subnet.
>
> Does anyone know what needs to be modified so that after the
> change of IP address for a CUPS PC the http://printhost:631/ CUPS
> admin pages are accessible?

Any number of issues might be involved.  Knowing nothing about your
setup I would do the following:

  1) Check if the machine is running a host firewall, and that it
     allows access to TCP port 631 from the right set of IPs.

  2) Check if the /etc/hosts.allow and /etc/hosts.deny are set up
     correctly to allow access.

  3) Check the <Location> ACLs generally found at the end of
     /etc/cups/cupsd.conf file.  This is where cups sets up its
     (possibly very fine grained) access control.  This is the most
     likely spot for something to be wrong, but check the above
     first to be sure they are correct.

  4) You are sure you can route to the new subnet correctly, right?

> Is this a CUPS issue or could it possibly be something to do with
> Apache 2?

Unless you're doing some crazy reverse proxy things, like I'm doing
;), I don't see how Apache 2 could possibly be getting in the way.

- --
Paul Ortman

PGP Key: 55602C81
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGyuWOfw8KGlVgLIERAoFOAKCAZVrWj+J4b796rcK2djo3A52plwCfQErP
XZ9Og3NsDvVC5f80kcVusr4=
=RaOO
-----END PGP SIGNATURE-----