On Tue, November 7, 2017 12:41 am, Sorin Srbu wrote:
>> -----Original Message-----
>> From: CentOS [mailto:centos-bounces@xxxxxxxxxx] On Behalf Of Valeri
>> Galtsev
>> Sent: den 6 november 2017 16:31
>> To: CentOS mailing list <centos@xxxxxxxxxx>
>> Subject: Re: HP laptops with CentOS 7?
>>
>>
>> > Our department is slowly leaving all those ad hoc printer solutions
> where
>> > every senior or group have their own printer and are instead opting
>> for
> a
>> > "Eduprint" solution. Any printer problems will soon be somebody else's
>> > problem.
>>
>> Hm, I regret to hear you are outsourcing your IT tasks too...
>
> Nah, I have plenty of other stuff to do.
>
>
>> > I'm quite happy to leave all printing problems behind me.
>> > Printers seem to be a never-ending source of problems...
>> >
>>
>> Even though "printing is the darkest page of IT book", if you set them
>> up
>> right, you will rarely have any problems. Namely:
>>
>> 1. Configure all printer to not accept jobs (or talk to) any machines
>> except for your UNIX print server
>>
>> 2. On print server make sure to use protocols to talk to printers that
>> do
>> not time out and stop CUPS queue. E.g., jetdirect (port 9100) never
>> will.
>>
>> 3. On print server set some restrictions so to fend off those who
>> shouldn't print to your printers. Restricting in local firewall on print
>> server machine access to print ports to local subnets of your Department
>> is one of the measures.
>
> When I first started at this job almost twenty years ago fresh out of
> IT-school, I had an idea to use a Windows print server as this was what I
> knew.
> I wasn't trusted with the *nix farm yet then.
> Over the years I have tried at least once a year to get our
> Linux-computers
> to talk to our AD-connected Windows Servers, but haven't quite made it
> yet.
> I've also tried to get the AD-connected Windows-clients to talk to a Linux
> print server to no avail.
I never use AD for Windows, but as far as printing is concerned this
shouldn't matter.
To configure Windows (any of 2000 and higher, before 2000 you would need
to add something to Windows which I will not mention as it is irrelevant
now):
1. In services under printing check two boxes (which are not enabled by
default):
LPD
LPR
This will teach Windows to talk UNIX printing language.
2. to set up new printer after 1 is done: add printer, create new port,
local port (choose LPD - or is it LPR? - in drop down menu), in print
server give hostname (or IP) of UNIX print server, in queue field give
name of the queue; the rest of setup is usual, just choose correct printer
model
For the above one needs to have CUPS listening to LPD (port 515), in Linux
there is extra rpm for that. I found this the most robust setup, so I
still do it this way, which is almost for two decades....
The trick is to have Windows talk to UNIX print server its native language
(LPD) which Windows knows ;-)
Valeri
> Granted it's been awhile now since I tried.
> Maybe
> I'll give it another go. Both the Windows and Linux OS:es have developed
> quite a bit the last ten years...
>
> --
> //Sorin
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
>
++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
