-----Mensaje original-----
De: Jean Hendrickx [mailto:jhendrickx@cantv.net]
Enviado el: Jueves, 15 de Enero de 2004 12:32 a.m.
Para: 'SuSE Discussion'
Asunto: RE: [SLE] Windows and Linux printers
Alejo, thanks for your link, I now have a clear view. I want to
use the default (LPR?) printing system on SuSE 9.0; I don't want to
install CUPS. It's mandatory?
I'm replacing an old SCO Open Server with Advanced File & Print
Server; as I can recall, AF&PS neither need a smbclient nor additional
software. My only 'hurdle' at this time is the inability of Windows's
machine of LAN A (192.168.1.0) to see the other Windows machine (the LAN
B, 192.168.2.0) ...
Of course, I'll follow the indications supplied at article, but
I want to gather all the possible ways to solve this before I'll go to
the site.
Any comments will be welcome,
Jean H//
-----Mensaje original-----
De: alejo [mailto:alejofdf@hotmail.com]
Enviado el: Miércoles, 14 de Enero de 2004 03:32 p.m.
Para: Jean Hendrickx; SuSE Discussion; Jean Hendrickx (CANTV)
Asunto: Re: [SLE] Windows and Linux printers
Check this link
Printing via SMB (Samba) Share or Windows Share
http://portal.suse.com/sdb/en/2003/11/jsmeix_print-smb-90.html
I have also problems if you manage let me know
----- Original Message -----
From: "Jean Hendrickx"
I folks, have a nice new Year! In a Linux SuSE 9.0 LAN Iwe have 2
192.168.1.0 and 192.168.2.0; connected via router (and working) ... I'm using SaMBa to share file and printers. We can access the machines of other network (192.168.2.0). Now I want to use SaMBa to access the Windows' shared (SaMBa?) resources of 192.168.2.0 from 192.168.1.0; and I'm stuck on
networks: this
... :-(
Can anyone please give me a lead? I tryied using YAST printers setup, but I don't know how to get this working ...
Thanks in advance, Jean H//
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hello, On Jan 15 00:36 Jean Hendrickx wrote (shortened):
I want to use the default (LPR?) printing system on SuSE 9.0; I don't want to install CUPS. It's mandatory?
The default printing systen on SUSE LINUX 9.0 is CUPS. Only the CUPS library package is mandatory (see the Administration manual). There is a button in YaST (via [Change] and [Advanced]) to switch from CUPS to LPRng/lpdfilter and vice versa (see the Administration manual). Use this button. Don't do it manually - except you know exactly about the packages and the dependencies (see the Administration manual). To access a SMB printer share from LPRng/lpdfilter use YaST. For background information (in particular if you must make changings in the file /etc/lpdfilter/QUEUE/redirect) see http://portal.suse.com/sdb/en/2002/04/jsmeix_print-80-probleme.html#Samba Regrads Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
If the way to solve/handle this problem is using CUPS I'll do; my complain with CUPS was because I never can setup a [Texas?] Printronix (hammer) printer; I think CUPS doesn't handle raw printing well, but this happened some years ago and the things gets better. I don't know SuSE 9.0 uses CUPS as default printing system; this can easy a lot my job. Thanks again, Jean H// -----Mensaje original----- De: Johannes Meixner [mailto:jsmeix@suse.de] Enviado el: Jueves, 15 de Enero de 2004 04:52 a.m. Para: suse-linux-e@suse.com Asunto: RE: [SLE] Windows and Linux printers Hello, On Jan 15 00:36 Jean Hendrickx wrote (shortened):
I want to use the default (LPR?) printing system on SuSE 9.0; I don't want to install CUPS. It's mandatory?
The default printing systen on SUSE LINUX 9.0 is CUPS. Only the CUPS library package is mandatory (see the Administration manual). There is a button in YaST (via [Change] and [Advanced]) to switch from CUPS to LPRng/lpdfilter and vice versa (see the Administration manual). Use this button. Don't do it manually - except you know exactly about the packages and the dependencies (see the Administration manual). To access a SMB printer share from LPRng/lpdfilter use YaST. For background information (in particular if you must make changings in the file /etc/lpdfilter/QUEUE/redirect) see http://portal.suse.com/sdb/en/2002/04/jsmeix_print-80-probleme.html#Samb a Regrads Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Jean Hendrickx wrote:
If the way to solve/handle this problem is using CUPS I'll do; my complain with CUPS was because I never can setup a [Texas?] Printronix (hammer) printer; I think CUPS doesn't handle raw printing well, but this happened some years ago and the things gets better.
For a local raw printing queue to work, here's a thing to check: /etc/cups/lpoptions Dest printername raw=true
Hello, On Jan 15 07:47 Jean Hendrickx wrote (shortened):
If the way to solve/handle this problem is using CUPS I'll do;
Printing from Linux to a SMB printer share does not depend on the printing system. It works well for LPRng/lpdfilter and CUPS. For general printing in a Windows and Linux network (e.g. printing from Windows clients to a Linux print server) CUPS may offer the best way. For more information see http://www.linuxprinting.org/indexdoc.html HOWTO's and Hints Printing with Samba 3.0 (Traditional Printing Systems & CUPS)
I think CUPS doesn't handle raw printing well
CUPS handles raw printing well. It depends on what you mean with "raw": If "raw" means "100% raw" (i.e. no filtering at all) then the command lpadmin -p QUEUE -v DeviceURI -E creates a "100% raw" queue. This kind of queue can be set up with YaST when you select not to do any (local) filtering. Regarding filtering and network printing see the Administration manual for SUSE LINUX 9.0 But if "raw" means in fact "do only some trivial filtering" (e.g. adding a formfeed character at the end of each print job or do some trivial recoding of plain text) then you should set up the queue with a so called "System V style interface script" (see "man lpadmin"). This kind of queue cannot be set up with YaST because you must create the interface script manually (YaST cannot guess what this script should contain). For more and detailed information see http://portal.suse.com/sdb/en/2003/06/jsmeix_print-cups-filters.html
I don't know SuSE 9.0 uses CUPS as default printing system
CUPS is default since SuSE Linux 8.1 - see http://portal.suse.com/sdb/en/2002/09/jsmeix_print-einrichten-81.html Regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
Hello, I am not able to print in a Windows PC from another Linux PC I have installed suse 9 (I am not an expert on commands) I have: -one PC-1 with XP connected to a printer (Epson440 parallel). This printer is shares in a windows network perfectly -one PC-2 with Linux suse 9 (and XP) -one HUB -one router for ADSL -the network configuration was given to me by the phone company. Fixing IP, DNS primary secondary and gateway - I have intalled SAMBA client and server in PC-2 with linux. - I am able to see PC-1 files and PC-2 server (one to each other) - I am not able to print in Win PC-1 from Linux PC-2. - I follow intructions (or I think so) of this Suse link Printing via SMB (Samba) Share or Windows Share http://portal.suse.com/sdb/en/2003/11/jsmeix_print-smb-90.html I follow the test and works. (I am able to print "hello" via commands) echo -en "\rHello\r\f" | smbclient "//NetBIOS-hostname/share" -c "print -" -N BUT I am not able to print normally. I configure (my excuses because my Suse is in Spanish and perhaps Yast2 commands do no match exactly): I go to "Yast2/hardware/printers/new printer/smb" (I left in blank- workgroup, user, pasword) -Two posibilities: 1-I search machines (only find PC-2, the Linux one, and gateway adress) I use gateway one. I printers only find PC-2 (do not work test nor probe). 2-I use IP "PC-1 with XP". and printers find PC-1(Epson), looks better.(do not work test nor probe). -I think spooler is in CUPS mode 1-Each time I make changes in YAST2. Should I restart Linux? 2-Should I make something in Windows? 3-Any help will be welcome. (please remember I am not an expert on commands) Thanks very much for your Help/Support
Hello, On Jan 15 18:19 alejo wrote (shortened):
http://portal.suse.com/sdb/en/2003/11/jsmeix_print-smb-90.html
I follow the test and works. (I am able to print "hello" via commands) echo -en "\rHello\r\f" | smbclient "//NetBIOS-hostname/share" -c "print -" -N
Then it will work wih CUPS as well. All what matters is the correct DeviceURI.
I go to "Yast2/hardware/printers/new printer/smb" (I left in blank- workgroup, user, pasword) -Two posibilities: 1-I search machines ...
Why don't you follow the instructions regarding YaST in http://portal.suse.com/sdb/en/2003/11/jsmeix_print-smb-90.html Enter the exact NetBIOS-hostname and share from the smbclient command above manually. If this doesn't work check the DeviceURI for CUPS. Regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
With suse 9 Yast is very easy I am new with Linux and i manage to do it
Configure:
1-net (yast/hardware/net-card) (IP....)
2-samba.(yast/software/net/samba (2 modules)) and you will be able to see
windows files (also you must allow share files and printers in windows) (I
am Spanish perhaps Prgrams words are not exact).
----- Original Message -----
From: "Jean Hendrickx"
I folks, have a nice new Year! In a Linux SuSE 9.0 LAN Iwe have 2
192.168.1.0 and 192.168.2.0; connected via router (and working) ... I'm using SaMBa to share file and printers. We can access the machines of other network (192.168.2.0). Now I want to use SaMBa to access the Windows' shared (SaMBa?) resources of 192.168.2.0 from 192.168.1.0; and I'm stuck on
networks: this
... :-(
Can anyone please give me a lead? I tryied using YAST printers setup, but I don't know how to get this working ...
Thanks in advance, Jean H//
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Jean Hendrickx wrote:
Alejo, thanks for your link, I now have a clear view. I want to use the default (LPR?) printing system on SuSE 9.0; I don't want to install CUPS. It's mandatory?
There is no reason in the world to use other printing system than CUPS. CUPS can emulate LPR, if you need that. Focus on CUPS.
I'm replacing an old SCO Open Server with Advanced File & Print
I'm glad to help someone replace SCO :-)
software. My only 'hurdle' at this time is the inability of Windows's machine of LAN A (192.168.1.0) to see the other Windows machine (the LAN B, 192.168.2.0) ...
You need to have routing in place, be able to ping from machine in LAN A to machine in LAN B. Then you need one WINS server for both networks, and point all the Windows stations to use that one WINS server. That can be easily achieved with a DHCP server. option netbios-name-servers
Hi Silviu, thanks for your comments. I worked with SCO from the beginning (Xenix) and I'm glad to replace it too ;-) they are less smarter each day ... I explained in my previous post why I didn't like CUPS (didn't handle a Printronix printer). The routes are well defined, and I'm able to 'see' (ping) the other machines. I don't know _exactly_ what a WINS server does, and they are using fixed (static) IPs ... but of course, I'll do some tests. Thanks, Jean H//
Jean Hendrickx wrote:
Hi Silviu, thanks for your comments. I worked with SCO from the beginning (Xenix) and I'm glad to replace it too ;-) they are less smarter each day ... I explained in my previous post why I didn't like CUPS (didn't handle a Printronix printer).
The routes are well defined, and I'm able to 'see' (ping) the other machines. I don't know _exactly_ what a WINS server does, and they are using fixed (static) IPs ... but of course, I'll do some tests.
A WINS server does netbios name resolution for Windows machines. You can easily setup a WINS server with samba/linux. In /etc/samba/smb.conf wins support = yes. Then start the nmb service. Do not define more than a WINS server.
participants (4)
-
alejo -
Jean Hendrickx -
Johannes Meixner -
Silviu Marin-Caea