On 08/02/21 05:40, Dan Egli wrote: > Hey folks, I'm a bit lost on this, so I hope you can help me out.
Dunno how much help I'll be ... > > I have a computer I want to act as the central print server for a > network. It would spool all jobs for all printers, and send them out to > the actual computers the printers are connected to, or to the printer > itself in the event of a printer directly connected to the network. To > start with, I have setup the server and added the printer connected to a > Windows 10 Home computer to it. Is this wise? Windows 10 Home is rather castrated - networking is a PITA because it assumes you won't ... After a bit of work, I managed to get it > so I can print a test page from cups and it comes out on the printer. > But when I try to connect another computer to the printer via the print > server, the other computer never sends it out. Just says the printer is > busy. This is typical. In my linux setup, the printer is always busy. Stuff still prints fine, though. > > How can I set this up correctly? To describe exactly what I'm trying to > do, let's just use four computers in this example. A is the central > print server. B is the windows client with the printer. C and D are > linux machines. What I want is if either C or D print something, they > both send it to A, and then A sends it to B. > I'd try moving the printer to A, or configuring C & D to print directly to B. I dunno how you set up smbprint, but that should send straight to a shared printer on B no problem. Cheers, Wol
