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