Samba Unable To Connect To CUPS Server Localhost:631

I'm running into an annoying issue with samba. I don't have any printers installed, and probably won't. However smbd complains to no end in /var/log/errors.log about not being able to connect to a cups server:

samba Unable to connect to CUPS server localhost:631

At this time the samba binary should be used for either: 'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the rpc proxy with 'dcerpc endpoint servers = remote'. You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks.

Note that "browsing" at the print server is a different thing from "browsing" at a remote networked host. On the print server, cupsd provides the DNS-SD protocol support which the avahi-daemon broadcasts. The cups-browsed service is unnecessary on the print server, unless also broadcasting the old CUPS protocol, or the print server is also "browsing" for other networked printers. On the remote networked host, the cups-browsed service is required to "browse" for network broadcasts of print services, and running cups-browsed will also automatically start cupsd.

The cups.service service will be automatically started when a USB printer is plugged in, however this may not be the case for other connection types. If cups.service is not running, avahi-daemon does not broadcast the print services, so in that case the systemd unit service file must be modified to start on boot, and then the service must again be "enabled/installed" with the new dependency. To do this, edit the service file [Install] section to add a WantedBy=default.target dependency, and then enable and start the cups.service service.

Open up the web interface to the server, select the Administration tab, look under the Server heading, and enable the "Share printers connected to this system" option. Save your change by clicking on the Change Settings button. The server will automatically restart.

Once the server is set up as described in #Printer sharing, it can also be configured so that it can be remotely administered. Add the allowed hosts to the block in /etc/cups/cupsd.conf, using the same syntax as described in #Sharing via Internet Printing Protocol. Note that three levels of access can be granted:

Kerberos can be used to authenticate users accessing a remote CUPS server. This assumes that your machine has a keytab and it will need a ticket for "HTTP". Instead of using :631 you must use :631 - encryption is required for auth (hence https) and the full hostname is needed so that Kerberos/Negotiate can work. In addition, the server must be configured in /etc/cups/cupsd.conf to use a DefaultAuthType of Negotiate.

When my laptop boots network is not yet configured since NM didnt start it yet. Samba however tries to start since it is in S20 on rc2-5.d but it fails immediately because no network is configured yet. Running - sudo /etc/init.d/samba restart - is fine.In the log file I can find the following pair of errors:[2009/04/18 11:22:48, 0] lib/interface.c:load_interfaces(540) WARNING: no network interfaces found[2009/04/18 11:22:49, 0] smbd/server.c:open_sockets_smbd(548) open_sockets_smbd: No sockets available to bind to.

If this solution makes sense I would recommend that it would be added to Ubuntu samba server package.Here is the script I wrote:#!/bin/sh -e# Script to dispatch NetworkManager events## Runs ifupdown scripts when NetworkManager fiddles with interfaces.

Apr 26 14:10:07 fringe init: smbd main process (1222) killed by ABRT signalApr 26 14:10:07 fringe init: smbd main process ended, respawningApr 26 14:10:07 fringe smbd[1233]: [2010/04/26 14:10:07, 0] printing/print_cups.c:103(cups_connect)Apr 26 14:10:07 fringe smbd[1233]: Unable to connect to CUPS server localhost:631 - Connection refusedApr 26 14:10:07 fringe smbd[1234]: [2010/04/26 14:10:07, 0] printing/print_cups.c:103(cups_connect)Apr 26 14:10:07 fringe smbd[1234]: Unable to connect to CUPS server localhost:631 - Connection refusedApr 26 14:10:07 fringe smbd[1232]: [2010/04/26 14:10:07, 0] lib/interface.c:550(load_interfaces)Apr 26 14:10:07 fringe smbd[1232]: WARNING: no network interfaces foundApr 26 14:10:07 fringe smbd[1232]: [2010/04/26 14:10:07, 0] smbd/server.c:1115(main)Apr 26 14:10:07 fringe smbd[1232]: standard input is not a socket, assuming -D optionApr 26 14:10:07 fringe smbd[1232]: [2010/04/26 14:10:07, 0] smbd/server.c:616(open_sockets_smbd)Apr 26 14:10:07 fringe smbd[1232]: open_sockets_smbd: No sockets available to bind to.Apr 26 14:10:07 fringe smbd[1232]: [2010/04/26 14:10:07, 0] smbd/server.c:837(exit_server_common)Apr 26 14:10:07 fringe smbd[1232]: ===============================================================Apr 26 14:10:07 fringe smbd[1232]: [2010/04/26 14:10:07, 0] smbd/server.c:839(exit_server_common)Apr 26 14:10:07 fringe smbd[1232]: Abnormal server exit: open_sockets_smbd() failedApr 26 14:10:07 fringe smbd[1232]: [2010/04/26 14:10:07, 0] smbd/server.c:840(exit_server_common)Apr 26 14:10:07 fringe smbd[1232]: ===============================================================Apr 26 14:10:07 fringe smbd[1232]: [2010/04/26 14:10:07, 0] lib/util.c:1584(log_stack_trace)Apr 26 14:10:07 fringe smbd[1232]: BACKTRACE: 6 stack frames:Apr 26 14:10:07 fringe smbd[1232]: #0 smbd(log_stack_trace+0x1a) [0x7f7c7d2de7aa]Apr 26 14:10:07 fringe smbd[1232]: #1 smbd(+0x5a9cc0) [0x7f7c7d56dcc0]Apr 26 14:10:07 fringe smbd[1232]: #2 smbd(+0x5a9e91) [0x7f7c7d56de91]Apr 26 14:10:07 fringe smbd[1232]: #3 smbd(main+0x90d) [0x7f7c7d56ebed]Apr 26 14:10:07 fringe smbd[1232]: #4 /lib/libc.so.6(__libc_start_main+0xfd) [0x7f7c79a6cc4d]Apr 26 14:10:07 fringe smbd[1232]: #5 smbd(+0xc0a49) [0x7f7c7d084a49]Apr 26 14:10:07 fringe smbd[1232]: [2010/04/26 14:10:07, 0] lib/fault.c:326(dump_core)Apr 26 14:10:07 fringe smbd[1232]: dumping core in /var/log/samba/cores/smbdApr 26 14:10:07 fringe smbd[1232]:Apr 26 14:10:07 fringe init: smbd main process (1232) killed by ABRT signalApr 26 14:10:07 fringe init: smbd main process ended, respawningApr 26 14:10:07 fringe smbd[1240]: [2010/04/26 14:10:07, 0] printing/print_cups.c:103(cups_connect)Apr 26 14:10:07 fringe smbd[1240]: Unable to connect to CUPS server localhost:631 - Connection r...

By default, the CUPS web interface is only available at localhost:631. If you are running Ubuntu server edition, you may also want to make CUPS listen on all available network interface, so that you will be able to access the CUPS web interface from other computers. Find the following line.

Anyone know how to force the protocol to ipp or ipps for a client. We upgraded to ubuntu20.04 and the cups clients are not getting all the printers from our print servers (ubuntu stations that share out printers and work for ubuntu18.04 clients).

Oct 18 14:58:06 server7b logger: Rotating smbaudit logs 0 Oct 18 14:58:20 server7b logger: Rotating smbaudit logs 0 Oct 18 14:58:20 server7b sshd[16623]: Did not receive identification string from 192.168.124.107 Oct 18 14:58:23 server7b logger: Rotating smbaudit logs 0 Oct 18 14:59:32 server7b logger: Rotating smbaudit logs 0 Oct 18 14:59:41 server7b logger: Rotating smbaudit logs 0 Oct 18 15:00:08 server7b logger: Rotating smbaudit logs 0 Oct 18 15:03:10 server7b smbd[16680]: [2016/10/18 15:03:10.216770, 0] printing/print_cups.c:151(cups_connect) Oct 18 15:03:10 server7b smbd[16680]: Unable to connect to CUPS server localhost:631 - Connection refused Oct 18 15:03:10 server7b smbd[2329]: [2016/10/18 15:03:10.229434, 0] printing/print_cups.c:528(cups_async_callback) Oct 18 15:03:10 server7b smbd[2329]: failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL Oct 18 15:06:35 server7b sshd[16692]: Accepted password for root from 192.168.124.126 port 54803 ssh2 Oct 18 15:16:10 server7b smbd[16747]: [2016/10/18 15:16:10.748625, 0] printing/print_cups.c:151(cups_connect) Oct 18 15:16:10 server7b smbd[16747]: Unable to connect to CUPS server localhost:631 - Connection refused Oct 18 15:16:10 server7b smbd[2329]: [2016/10/18 15:16:10.748988, 0] printing/print_cups.c:528(cups_async_callback) Oct 18 15:16:10 server7b smbd[2329]: failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL Oct 18 15:29:11 server7b smbd[17225]: [2016/10/18 15:29:11.449404, 0] printing/print_cups.c:151(cups_connect) Oct 18 15:29:11 server7b smbd[17225]: Unable to connect to CUPS server localhost:631 - Connection refused Oct 18 15:29:11 server7b smbd[2329]: [2016/10/18 15:29:11.456000, 0] printing/print_cups.c:528(cups_async_callback) Oct 18 15:29:11 server7b smbd[2329]: failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL Oct 18 15:42:12 server7b smbd[17833]: [2016/10/18 15:42:12.081606, 0] printing/print_cups.c:151(cups_connect) Oct 18 15:42:12 server7b smbd[17833]: Unable to connect to CUPS server localhost:631 - Connection refused Oct 18 15:42:12 server7b smbd[2329]: [2016/10/18 15:42:12.170144, 0] printing/print_cups.c:528(cups_async_callback) Oct 18 15:42:12 server7b smbd[2329]: failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL Oct 18 15:42:13 server7b logger: Rotating smbaudit logs 0 Oct 18 15:42:14 server7b logger: Rotating smbaudit logs 0 Oct 18 15:42:26 server7b logger: Rotating smbaudit logs 0 Oct 18 15:42:46 server7b logger: Rotating smbaudit logs 0

I have a home file server on which I have recently reinstalled the OS. I replaced Ubuntu Server 10.04.2 32-bit with 10.04.3 64-bit due to hardware upgrades. I've copied my previous Samba configuration over, recreated the share user, and made sure the permissions for the shared directories, on another disk, were still intact. I have an XP and a Win7 machine. Both can see the file server, but neither can access the shares. If I go to \\Server on a Windows machine, it prompts for a user/pass and appears to accept the connection. If I go to \\Server\Share next, it asks for a user/pass again, and will not authenticate.