From: "m.roth@xxxxxxxxx" <m.roth@xxxxxxxxx> >> Yes, the CUPS Manual says: >> "Multiple Listen directives can be provided to >> listen on multiple addresses" > Well, did that... and no joy, from another box, I can still > telnet to the server on one of the virtual IPs, port 631. > I can't really play around much, here - this is a production > box, used by a lot of staff. Strange; I just created an alias on my PC, told cups to listen on my main IP, and it did... eth0 = 192.168.16.23 eth0:0 = 192.168.16.40 # grep Listen /etc/cups/cupsd.conf Listen localhost:631 Listen 192.168.16.23:631 Listen /var/run/cups/cups.sock # netstat -nltp | grep cupsd tcp 0 0 192.168.16.23:631 0.0.0.0:* LISTEN 18733/cupsd tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 18733/cupsd $ telnet 192.168.16.40 631 Trying 192.168.16.40... telnet: connect to address 192.168.16.40: Connection refused telnet: Unable to connect to remote host: Connection refused Guess you restarted cupsd... right? JD _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos