Dear list, To achieve the above I used ICE.TCP on SCO Openserver 5.0.x and it worked wonders. It comes with a application called ICELPD which listens to port 2346. When a user sends a print to the printer its executes a printer interface script, example printermodel.scr. The *.scr creates a file-file stores it in /usr/tmp. Client gets it via port 2346 and it prints locally. I've got the ICELP printing deamon for Linux working. My question is where do I place the script file. You could possibly call the script file a driver? In SUSE it asks for a ppd file and does not recognise *.scr. I've check in /usr/share/cups/model Perhaps someone can recommend something? Perhaps even a diffrent solution totally? I use the ICE.TCP printing solution for speed. Its very very fast. Check out www.jriver.com Thanks Fred
On Sunday 28 December 2003 22:01, fareed@iplex.co.zw wrote:
Dear list,
To achieve the above I used ICE.TCP on SCO Openserver 5.0.x and it worked wonders.
It comes with a application called ICELPD which listens to port 2346. When a user sends a print to the printer its executes a printer interface script, example printermodel.scr. The *.scr creates a file-file stores it in /usr/tmp. Client gets it via port 2346 and it prints locally.
I've got the ICELP printing deamon for Linux working. My question is where do I place the script file. You could possibly call the script file a driver? In SUSE it asks for a ppd file and does not recognise *.scr. I've check in /usr/share/cups/model
Perhaps someone can recommend something? Perhaps even a diffrent solution totally? I use the ICE.TCP printing solution for speed. Its very very fast. Check out www.jriver.com
Why pay for that? Cups works fine for this, across the room, across the campus, across the world.... From linux, windows, or any IPP client. -- _____________________________________ John Andersen
On Mon, 2003-12-29 at 21:23, John Andersen wrote:
On Sunday 28 December 2003 22:01, fareed@iplex.co.zw wrote:
Dear list,
To achieve the above I used ICE.TCP on SCO Openserver 5.0.x and it worked wonders.
It comes with a application called ICELPD which listens to port 2346. When a user sends a print to the printer its executes a printer interface script, example printermodel.scr. The *.scr creates a file-file stores it in /usr/tmp. Client gets it via port 2346 and it prints locally.
I've got the ICELP printing deamon for Linux working. My question is where do I place the script file. You could possibly call the script file a driver? In SUSE it asks for a ppd file and does not recognise *.scr. I've check in /usr/share/cups/model
Perhaps someone can recommend something? Perhaps even a diffrent solution totally? I use the ICE.TCP printing solution for speed. Its very very fast. Check out www.jriver.com
Why pay for that? Cups works fine for this, across the room, across the campus, across the world.... From linux, windows, or any IPP client.
I completely agree with John. CUPS works great! I can print from home to my office computer. (It's for when I work from home). Try it, it's really easy to setup....and I'm an idiot. Tom
Can anyone point me to a URL, book or otherwise, would like to know how to configure CUPS to print from a Windows PC. Thanks Fred -----Original Message----- From: Tom Nielsen [mailto:tom@neuro-logic.com] Sent: Tuesday, December 30, 2003 10:16 AM To: Suse Subject: Re: [SLE] TCP / IP Printing On Mon, 2003-12-29 at 21:23, John Andersen wrote:
On Sunday 28 December 2003 22:01, fareed@iplex.co.zw wrote:
Dear list,
To achieve the above I used ICE.TCP on SCO Openserver 5.0.x and it worked wonders.
It comes with a application called ICELPD which listens to port 2346. When a user sends a print to the printer its executes a printer interface script, example printermodel.scr. The *.scr creates a file-file stores it in /usr/tmp. Client gets it via port 2346 and it prints locally.
I've got the ICELP printing deamon for Linux working. My question is where do I place the script file. You could possibly call the script file a driver? In SUSE it asks for a ppd file and does not recognise *.scr. I've check in /usr/share/cups/model
Perhaps someone can recommend something? Perhaps even a diffrent solution totally? I use the ICE.TCP printing solution for speed. Its very very fast. Check out www.jriver.com
Why pay for that? Cups works fine for this, across the room, across the campus, across the world.... From linux, windows, or any IPP client.
I completely agree with John. CUPS works great! I can print from home to my office computer. (It's for when I work from home). Try it, it's really easy to setup....and I'm an idiot. Tom
PLEASE everyone, STOP top posting, it screws up the threads for the archives. Freds answer at the bottom. On Tue, 2003-12-30 at 11:08, fareed@iplex.co.zw wrote:
Can anyone point me to a URL, book or otherwise, would like to know how to configure CUPS to print from a Windows PC.
Thanks Fred
-----Original Message----- From: Tom Nielsen [mailto:tom@neuro-logic.com] Sent: Tuesday, December 30, 2003 10:16 AM To: Suse Subject: Re: [SLE] TCP / IP Printing
On Mon, 2003-12-29 at 21:23, John Andersen wrote:
On Sunday 28 December 2003 22:01, fareed@iplex.co.zw wrote:
Dear list,
To achieve the above I used ICE.TCP on SCO Openserver 5.0.x and it worked wonders.
It comes with a application called ICELPD which listens to port 2346. When a user sends a print to the printer its executes a printer interface script, example printermodel.scr. The *.scr creates a file-file stores it in /usr/tmp. Client gets it via port 2346 and it prints locally.
I've got the ICELP printing deamon for Linux working. My question is where do I place the script file. You could possibly call the script file a driver? In SUSE it asks for a ppd file and does not recognise *.scr. I've check in /usr/share/cups/model
Perhaps someone can recommend something? Perhaps even a diffrent solution totally? I use the ICE.TCP printing solution for speed. Its very very fast. Check out www.jriver.com
Why pay for that? Cups works fine for this, across the room, across the campus, across the world.... From linux, windows, or any IPP client.
I completely agree with John. CUPS works great! I can print from home to my office computer. (It's for when I work from home). Try it, it's really easy to setup....and I'm an idiot.
Tom
You will also need to install and configure samba in order to be able to use the printers on a linux machine. www.samba.org has a lot of documentation as well as www.cups.org. Ken -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Tuesday 30 December 2003 07:37, Kenneth Schneider wrote:
You will also need to install and configure samba in order to be able to use the printers on a linux machine. www.samba.org has a lot of documentation as well as www.cups.org.
Ken
I'm sorry Ken but that it just not true. And it hasn't been true for a long long time. All Win2k and later come with IPP print capability built in. You just configure it as a network printer and give http://yourlogin:password@your-linux-box:631/printers/printer-name as the printer url. For win98 you need to download the wpnpins.exe file to get the IPP drivers. Best to squirel these away, since MS announced the demise of Win98. Those drivers also work on win95. -- _____________________________________ John Andersen
On Tue, 2003-12-30 at 23:08, John Andersen wrote:
On Tuesday 30 December 2003 07:37, Kenneth Schneider wrote:
You will also need to install and configure samba in order to be able to use the printers on a linux machine. www.samba.org has a lot of documentation as well as www.cups.org.
Ken
I'm sorry Ken but that it just not true. And it hasn't been true for a long long time.
All Win2k and later come with IPP print capability built in. You just configure it as a network printer and give http://yourlogin:password@your-linux-box:631/printers/printer-name as the printer url.
If the printer has a network card like a HP Jetdirect you can also configure your computer to print directly the printer and bypasss the Samba server altogether. In the setup printer wizard choose local printer then create a new local port. Enter the IP address of the printer and Windows will attempt to detect which type of network interface the printer has. (I have never had it fail to detect a HP Jetdirect printer.) Choose the appropriate printer driver when prompted and you should be good to go.
For win98 you need to download the wpnpins.exe file to get the IPP drivers. Best to squirel these away, since MS announced the demise of Win98. Those drivers also work on win95.
HP also has a software product called Install Network Printer Wizard that will work with HP printers. They have version for Win95 that was last updated in Jan 2002 and a version for Win98 and later that was last updated Sept 2003. Goto this page http://welcome.hp.com/country/us/en/support.html and enter Install Network Printer Wizard in the search dialog box and it will take you right to it. HTH -- Chuck Stuettgen <cstuettgen@myrealbox.com> http://www.cfs-tech.homelinux.net
On Tuesday 30 December 2003 22:35, Chuck Stuettgen wrote:
On Tue, 2003-12-30 at 23:08, John Andersen wrote:
On Tuesday 30 December 2003 07:37, Kenneth Schneider wrote:
You will also need to install and configure samba in order to be able to use the printers on a linux machine. www.samba.org has a lot of documentation as well as www.cups.org.
Ken
I'm sorry Ken but that it just not true. And it hasn't been true for a long long time.
All Win2k and later come with IPP print capability built in. You just configure it as a network printer and give http://yourlogin:password@your-linux-box:631/printers/printer-name as the printer url.
If the printer has a network card like a HP Jetdirect you can also configure your computer to print directly the printer and bypasss the Samba server altogether.
But don't do that. If you have a linux server, use it as such rather than relying on a dumb print box to arbitrate concurrent access. Send it all thru cups. All of it. It will feed the jet-direct boxes one job at a time. This way you configure ALL stations to go thru the server, and when a jetdirect box needs replacement or a new one comes you only have ONE machine to re-configure not a whole office full. Printers are the bain of a sys-admin's existance, and the first and most effective step toward getting it to go smoothly is to send it all thru the server. -- _____________________________________ John Andersen
On Wed, 31 Dec 2003 19:02, John Andersen wrote:
On Tuesday 30 December 2003 22:35, Chuck Stuettgen wrote:
If the printer has a network card like a HP Jetdirect you can also configure your computer to print directly the printer and bypasss the Samba server altogether.
But don't do that. If you have a linux server, use it as such rather than relying on a dumb print box to arbitrate concurrent access.
Send it all thru cups. All of it.
I will second that especially with Windows. You are just inviting trouble. I have seen it over and over again where someone sets up the printer to control the queuing and they find print jobs drop out, pages missing and formatting problems. More problems than you can poke at stick at. Cups just works and works well and requires virtually no maintenance or administration once installed. -- Regards, Graham Smith ---------------------------------------------------------
/snip/
But don't do that. If you have a linux server, use it as such rather than relying on a dumb print box to arbitrate concurrent access.
Send it all thru cups. All of it.
I will second that especially with Windows. You are just inviting trouble. I have seen it over and over again where someone sets up the printer to control the queuing and they find print jobs drop out, pages missing and formatting problems. More problems than you can poke at stick at.
Cups just works and works well and requires virtually no maintenance or administration once installed.
I will put in with this one too. CUPS rocks! Does everything you need and most of what you want. You also have the ability to configure and control it from anywhere you want using a web browser. Almost all of the list questions on it have been taken care of quickly and there are only a few printers that have given people problems. Never gotten direct jet to work reliably or consistently. Besides, I'm lazy and cups gives me the power to manage all the printing on my home network from one location. Just tossing my .02 into the hat, will
will <deadwill@cryogen.com> writes:
CUPS rocks! Does everything you need and most of what you want.
I agree that CUPS is better than other printing solutions I know but the current version 1.1.x still doesn't support color calibration (e.g. via ICC profiles). CUPS 1.2 will support it but this version is not ready yet. -- A.M.
On 12/31/2003 10:14 PM, Alexandr Malusek wrote:
I agree that CUPS is better than other printing solutions I know but the current version 1.1.x still doesn't support color calibration (e.g. via ICC profiles). CUPS 1.2 will support it but this version is not ready yet.
joe@jmorris:~> rpm -q cups cups-1.1.20-0 joe@jmorris:~> cat /etc/SuSE-release SuSE Linux 8.2 (i586) VERSION = 8.2 Available today via suse-people via apt (I forget which directory it is on pub/people. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
On 01/01/2004 09:59 AM, Joe Morris (NTM) wrote:
On 12/31/2003 10:14 PM, Alexandr Malusek wrote:
CUPS 1.2 will support it but this version is not ready yet.
joe@jmorris:~> rpm -q cups cups-1.1.20-0
Looked again just as I was closing my xterm. 1.1.20 is NOT 1.2. Sorry. My mistake. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Op woensdag 31 december 2003 08:35, schreef Chuck Stuettgen:
All Win2k and later come with IPP print capability built in. You just configure it as a network printer and give http://yourlogin:password@your-linux-box:631/printers/printer-name as the printer url.
If the printer has a network card like a HP Jetdirect you can also configure your computer to print directly the printer and bypasss the Samba server altogether.
In the setup printer wizard choose local printer then create a new local port. Enter the IP address of the printer and Windows will attempt to detect which type of network interface the printer has. (I have never had it fail to detect a HP Jetdirect printer.) Choose the appropriate printer driver when prompted and you should be good to go.
For win98 you need to download the wpnpins.exe file to get the IPP drivers. Best to squirel these away, since MS announced the demise of Win98. Those drivers also work on win95.
Tried the above for a win98 box, but no go. From the win98 I can access the cups admin/printer/etc pages => the network connection is there. But when I use add printer -> select network printer and add: - ipp://192.168.4.3/ - http://lp:password@192.168.4.3/ - http://lp:password@192.168.4.3/printers/normal win98 says the box is offline :(( In win98 software configuration "windows internet printing protocol" is listed active. cupsd.conf file: LogLevel info Printcap /etc/cups/printcap User lp Group lp RunAsUser Yes Port 631 BrowseAddress 191.168.4.255 BrowseAllow 192.168.4.* <Location /> Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 127.0.0.2 Allow From 192.168.4.* Allow From @LOCAL </Location> <Location /admin> AuthType BasicDigest AuthClass Group AuthGroupName sys Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 192.168.4.* </Location> Who knows what must be done, to get this working? -- Richard Bos Without a home the journey is endless
On Thursday 01 January 2004 12:25, Richard Bos wrote:
- ipp://192.168.4.3/ - http://lp:password@192.168.4.3/ - http://lp:password@192.168.4.3/printers/normal
win98 says the box is offline :((
In win98 software configuration "windows internet printing protocol" is listed active.
cupsd.conf file: LogLevel info Printcap /etc/cups/printcap User lp Group lp RunAsUser Yes Port 631 <<<<<<<<<<<<----------- Right there !!!!! BrowseAddress 191.168.4.255 BrowseAllow 192.168.4.*
Try using http://lp:password@192.168.4.3:631/printers/normal -- _____________________________________ John Andersen
Op vrijdag 2 januari 2004 03:28, schreef John Andersen:
Try using http://lp:password@192.168.4.3:631/printers/normal
It seems that http://<printserver>:631/printers/normal, works. However, I had to update the win98 network settings. As it appears it could not resolve the printservers system name. I used ethereal to investigate it. ethereal also revealed that "lp:password" is not correctly handled, and should not be part of the url. -- Richard Bos Without a home the journey is endless
On Friday 02 January 2004 13:25, Richard Bos wrote:
It seems that http://<printserver>:631/printers/normal, works. However, I had to update the win98 network settings. As it appears it could not resolve the printservers system name. I used ethereal to investigate it. ethereal also revealed that "lp:password" is not correctly handled, and should not be part of the url.
Format is actually user:password@printserver:631/printers/printername And it's not strictly necessary to have the password in there anyway on a local network. You can just set up cups to ALLOW FROM the local net. -- _____________________________________ John Andersen
Op zaterdag 3 januari 2004 01:51, schreef John Andersen:
On Friday 02 January 2004 13:25, Richard Bos wrote:
It seems that http://<printserver>:631/printers/normal, works. However, I had to update the win98 network settings. As it appears it could not resolve the printservers system name. I used ethereal to investigate it. ethereal also revealed that "lp:password" is not correctly handled, and should not be part of the url.
Format is actually user:password@printserver:631/printers/printername
And it's not strictly necessary to have the password in there anyway on a local network. You can just set up cups to ALLOW FROM the local net.
John, win98 tried to resolve the system name "lp", which does not exist of course. It therefor stated that the printer was off line.... -- Richard Bos Without a home the journey is endless
On Wed, 2003-12-31 at 00:08, John Andersen wrote:
On Tuesday 30 December 2003 07:37, Kenneth Schneider wrote:
You will also need to install and configure samba in order to be able to use the printers on a linux machine. www.samba.org has a lot of documentation as well as www.cups.org.
Ken
I'm sorry Ken but that it just not true. And it hasn't been true for a long long time.
All Win2k and later come with IPP print capability built in. You just configure it as a network printer and give http://yourlogin:password@your-linux-box:631/printers/printer-name as the printer url.
Now that looks real secure, include your user name/password in a configuration setting. I think I will stick with using samba as it appears more secure. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
participants (10)
-
Alexandr Malusek -
Chuck Stuettgen -
fareed＠iplex.co.zw -
Graham Smith -
Joe Morris (NTM) -
John Andersen -
Kenneth Schneider -
Richard Bos -
Tom Nielsen -
will