Oddly, changing nothing but letting it sit overnight (longer than the entire
time I was setting it up and troubleshooting yesterday) lets Samba see the list
of CUPS printers now.
It still refuses to connect however.
When trying to right click connect two dialogs pop up:
Windows Printer Installation -> Connecting to printName on memberServer
(cancel)
Add Printer -> Connect to Printer ; Windows cannot connect to the printer.
No more connections can be made to this remote computer at this time because
there are already as many connections as the computer can accept.
.
Which is just completely strange as this member server was literally setup only
for this task and I'm the only one even trying to connect to it.
Nothing obvious is in Samba's logs on that system, and I can access the
testshare on that system immediately after.
Additional log levels and/or logs to check would be nice troubleshooting steps.
Cups modifications of note:
/etc/cups/cupsd.conf
...
ServerAlias *
Port 631
Listen /run/cups/cups.sock
Browsing Yes
BrowseLocalProtocols dnssd
...
Anyplace that mentioned:
@SYSTEM was searched and replaced by @SYSTEM lpadmin "@domain admins"
"@WINDOM\Domain Admins"
@OWNER was searched and replaced by @OWNER "@domain users"
"@WINDOM\Domain Users"
# echo This is what changed the Listen *:631 to just Port
# cupsctl --remote-admin --remote-any --share-printers
Ignoring all of the /admin sections...
<Location />
Order allow,deny
Allow all
</Location>
<Location /admin>
Order allow,deny
Allow all
</Location>
...
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs
Set-Job-Attributes Create-Job-Subscription Renew-Subscription
Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Sus
pend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job
CUPS-Get-Document>
Require user @OWNER @SYSTEM lpadmin "@domain users"
"@WINDOM\Domain Users" "@domain admins" "@WINDOM\Domain
Admins"
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class
CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM lpadmin "@domain admins"
"@WINDOM\Domain Admins"
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer
Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs
Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startu
p-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs
CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM lpadmin "@domain admins"
"@WINDOM\Domain Admins"
Order deny,allow
</Limit>
<Limit CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM lpadmin "@domain users"
"@WINDOM\Domain Users" "@domain admins" "@WINDOM\Domain
Admins"
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
... authenticated and Kerberos sections are similar
> -----Original Message-----
> From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Stefan
> Kania via samba
> Sent: Thursday, January 13, 2022 5:10 AM
> To: samba at lists.samba.org
> Subject: Re: [Samba] samba + cups troubleshooting?
>
> Did you share the printer in the cups-setting? Did you edit the file
> /etc/cups/cupsd.conf to set the right permission and change the variable
> "listen" to the IP-address of your printserver?
>
>
> Am 13.01.22 um 03:01 schrieb Michael Evans via samba:
> > Are samba + cups troubleshooting steps documented anywhere?
> >
> >
> >
> > I still haven't been able to get Debian 11's Samba
(4.13.13-Debian) to
> > share printers to Windows 10, not on an old (weak crypto) domain and
> > not on a new clean Samba 4.13 domain; but both of these do at least
> > initially list on \\memberserver\ the printernames (even though
connecting
> to them fails).
> >
> >
> >
> > This week's experiment: Arch Linux VM (rolling release) with Samba
4.15.3.
> > By every indication I can think to test this has joined the old
> > insecure domain successfully.
> >
You should take a look at my tutorial from last years sambaxp (is in English) : https://www.kania-online.de/veroeffentlichungen/ Am 13.01.22 um 23:48 schrieb Michael Evans:> Oddly, changing nothing but letting it sit overnight (longer than the entire time I was setting it up and troubleshooting yesterday) lets Samba see the list of CUPS printers now. > > It still refuses to connect however. > > When trying to right click connect two dialogs pop up: > > Windows Printer Installation -> Connecting to printName on memberServer (cancel) > > Add Printer -> Connect to Printer ; Windows cannot connect to the printer. No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. > > . > > Which is just completely strange as this member server was literally setup only for this task and I'm the only one even trying to connect to it. > > Nothing obvious is in Samba's logs on that system, and I can access the testshare on that system immediately after. > > Additional log levels and/or logs to check would be nice troubleshooting steps. > > Cups modifications of note: > > /etc/cups/cupsd.conf > ... > ServerAlias * > Port 631 > Listen /run/cups/cups.sock > Browsing Yes > BrowseLocalProtocols dnssd > ... > > Anyplace that mentioned: > @SYSTEM was searched and replaced by @SYSTEM lpadmin "@domain admins" "@WINDOM\Domain Admins" > > @OWNER was searched and replaced by @OWNER "@domain users" "@WINDOM\Domain Users" > > # echo This is what changed the Listen *:631 to just Port > # cupsctl --remote-admin --remote-any --share-printers > > Ignoring all of the /admin sections... > > <Location /> > Order allow,deny > Allow all > </Location> > <Location /admin> > Order allow,deny > Allow all > </Location> > ... > <Policy default> > JobPrivateAccess default > JobPrivateValues default > SubscriptionPrivateAccess default > SubscriptionPrivateValues default > <Limit Create-Job Print-Job Print-URI Validate-Job> > Order deny,allow > </Limit> > <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Sus > pend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document> > Require user @OWNER @SYSTEM lpadmin "@domain users" "@WINDOM\Domain Users" "@domain admins" "@WINDOM\Domain Admins" > Order deny,allow > </Limit> > <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices> > AuthType Default > Require user @SYSTEM lpadmin "@domain admins" "@WINDOM\Domain Admins" > Order deny,allow > </Limit> > <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startu > p-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs> > AuthType Default > Require user @SYSTEM lpadmin "@domain admins" "@WINDOM\Domain Admins" > Order deny,allow > </Limit> > <Limit CUPS-Authenticate-Job> > Require user @OWNER @SYSTEM lpadmin "@domain users" "@WINDOM\Domain Users" "@domain admins" "@WINDOM\Domain Admins" > Order deny,allow > </Limit> > <Limit All> > Order deny,allow > </Limit> > </Policy> > ... authenticated and Kerberos sections are similar > >> -----Original Message----- >> From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Stefan >> Kania via samba >> Sent: Thursday, January 13, 2022 5:10 AM >> To: samba at lists.samba.org >> Subject: Re: [Samba] samba + cups troubleshooting? >> >> Did you share the printer in the cups-setting? Did you edit the file >> /etc/cups/cupsd.conf to set the right permission and change the variable >> "listen" to the IP-address of your printserver? >> >> >> Am 13.01.22 um 03:01 schrieb Michael Evans via samba: >>> Are samba + cups troubleshooting steps documented anywhere? >>> >>> >>> >>> I still haven't been able to get Debian 11's Samba (4.13.13-Debian) to >>> share printers to Windows 10, not on an old (weak crypto) domain and >>> not on a new clean Samba 4.13 domain; but both of these do at least >>> initially list on \\memberserver\ the printernames (even though connecting >> to them fails). >>> >>> >>> >>> This week's experiment: Arch Linux VM (rolling release) with Samba 4.15.3. >>> By every indication I can think to test this has joined the old >>> insecure domain successfully. >>> > >-- Stefan Kania Landweg 13 25693 St. Michaelisdonn Signieren jeder E-Mail hilft Spam zu reduzieren und sch?tzt Ihre Privatsph?re. Ein kostenfreies Zertifikat erhalten Sie unter https://www.dgn.de/dgncert/index.html Download der root-Zertifikate: https://www.dgn.de/dgncert/downloads.html