On Wednesday, 10 February 2021 23:03:18 GMT Dan Egli wrote: > On 2/10/2021 4:30 AM, Michael wrote:
> > This is how I understand the printing process ought to work in your use > > case: > > > > The Samba server, Athena, will use the MSWindows Network Printer > > identified as "Windows Printer via SAMBA" in its CUPS GUI. > > > > Printing jobs will be submitted from Athena's CUPS to the MSWindows PC & > > its attached printer, via the corresponding smb:// URI. CUPS which will > > use the Samba server on Athena to authenticate and send the data for > > printing to the MSWindows PC and its shared printer. > > > > The same process will need to be followed by Janus; i.e. the CUPS server > > on Janus will have to use the same smb:// URI to submit the data to be > > printed to Athena's Samba server and as long as authentication is > > successful Athena will forward it to the Windows PC. > > Forgive me, but if I use the SAME url, then it's not Athena acting as > the print server, it's the windows client that the printer is hooked up > to. Sorry, I meant to say on Janus use the smb://Athena/<printer> URI and see if Athena then forwards the request via the shared Samba printer service onward to the MSWindows PC. Of course if you try to print directly to the MSWindows PC with smb://IRIS/<printer> it will work, just as it works from Athena - but that's not what you're after. > I tried to use the LPD to print to Athena and have Athena print to > the printer via Samba. That's where I was running into problems. I > suppose I can try IPP. I don't know of a smb:// url would work goinf > from Janus (or anyone else) to Athena. After all, the printer isn't > connected to Athena. It's connected to the windows 10 home PC. I suppose > IPP might work if I configure that. As far as listening on 631, Athena's > cups was ALREADY listening on that port because that's where the web > interface is. the url I use to manage the printers is > https://athena:631. I guess that somehow Cups can tell the difference > between https, http, and ipp all coming on the same port. The ports listened to by CUPS are as follows: https://www.cups.org/doc/firewalls.html When the printer URI used is http, then the MIME type used by IPP will be "application/ipp" to transact printing commands. A browser will access the admin GUI over http also on port 631. LPD/LPR is limited in functionality and deprecated, although if it could be made to work for now there'd be no argument against using it. ;-) IPP is well supported, however, without trying it out I wouldn't know if it will work in your particular use case. In theory a shared CUPS server on Athena, plus its shared printer, should allow Janus to submit print jobs to it. The shared printer advertised by CUPS in Athena should pop up on Janus as an available printer via mDNS. > > The Samba configuration on Athena will deal with the settings for sharing > > the MSWindows printer. > > Okay, so basically you're saying that Athena would connect via > smb://windows/<PRINTER> and that Janus or other computers would connect > via smb://Athena/<PRINTER>? Okay, that may work. Yes, under this configuration scenario the printing service served by Samba on Athena is a shared Windows printer and would be accessed via the smb:// protocol. So, the Janus CUPS server will connect to the printer service provided by the Samba server on Athena. Again, without trying it out and troubleshooting it I wouldn't know if it'd work. > I'll have to do a bit > of digging because Athena and Janus are actually connected to an AD > Domain run by samba. In fact, Janus is the DC while Athena is the > location of the files/printers to be shared in the domain. As long as Janus (the Samba client) is authenticated to use Samba services being served by Athena, it /should/ work. You would need to configure firewalls accordingly to keep ports available, if you have firewalls enabled. Grant's comment about buying a printer is opportune, depending on the value of (your) time. The cost of printers and especially 2nd hand printers with so many companies going bust, should approximate zero. The expense of running a printer is in the overinflated ink price, which is a multiple of the upfront cost of buying the device. On the other hand, if cashflow itself is zero, options are understandably limited.
signature.asc
Description: This is a digitally signed message part.
