Reviewing all of the comments on this bug report to-date its looks like there are probably two issues:
1) A potential race condition between cups and samba which means that samba is unable to lookup the list of printers on startup. This is indicated by the following log messages in /var/log/samba/log.smbd: [2012/04/02 13:17:15.089590, 0] printing/print_cups.c:110(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused [2012/04/02 13:17:15.090587, 0] printing/print_cups.c:487(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL I think we can put in a conditional wait in the upstart configuration file for smbd to ensure that the cups daemon is in a running state before samba starts. 2) A change in behaviour which subsequently causes printing to fail with authentication issues (thats a premise - remains unproven IMHO). I've tried to reproduce this issue using a Windows XP Client -> Ubuntu 12.10 Server; however I was able to print successfully so we need to dig into this a bit further. It would be really helpful if the original bug report or anyone still seeing issues could increase the log verbosity by adding: log level = 3 to /etc/samba/smb.conf; any additional log information post restart for samba for both the server processes and the client connections would be really helpful. This second issue might be related to bug 990388 - but its hard to tell at this point in time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
