Printing Problems - SAMBA, CUPS and YaST2
Hello, everyone. I am almost to the end of transferring everything from my old server to my new one, but am having a great deal of difficulty getting Samba to allow my Windows 2000 clients to print. Firstly, the old server is a SuSE 7.3 Pro box, the new one is SuSE 8.1 Pro. With the old server I had no problems running a laser printer off lp0, and an inkjet of usb0, all set up with YaST1 and lpr. Since then, I have a new inkjet (HP DJ960C) and got rid of the laser printer. All I need to do is hook the inkjet up to lp0, and share it out through Samba to my W2K machines. Using YaST2, I have set up the printer on lp0 using CUPS. It was auto-detected, and four queues were set up; greyscale, colour, hi-res colour and photo. Each of these queues works just fine for local printing. Each of these queues show up when I browse the server from my W2K boxes, and I am able to map my printers to them. However, when I open the printer, I see the following error in the title bar: Access denied, unable to connect Also, I have yet to find where to set up a raw queue in YaST2 which is the one I'll want to use as my share, as the print jobs will be processed using the local driver on the W2K machines, and then sent to the queue on the server for printing. I have been trying to work this out for two weeks, and have finally had to hook the printer back up to my W2K laptop just to be able to print something out. Does anyone have any ideas how to get this working ? Thanks, Stuart.
Using YaST2, I have set up the printer on lp0 using CUPS. It was auto-detected, and four queues were set up; greyscale, colour, hi-res colour and photo. Each of these queues works just fine for local printing. Each of these queues show up when I browse the server from my W2K boxes, and I am able to map my printers to them. However, when I open the printer, I see the following error in the title bar:
Access denied, unable to connect
Also, I have yet to find where to set up a raw queue in YaST2 which is the one I'll want to use as my share, as the print jobs will be processed using the local driver on the W2K machines, and then sent to the queue on the server for printing.
I have been trying to work this out for two weeks, and have finally had to hook the printer back up to my W2K laptop just to be able to print something out. Does anyone have any ideas how to get this working ?
Thanks, Stuart. What does your printer section of your smb.conf file look like? What is
snip the authentication method that you are using? You might have posted the anwser to the latter question but I'm trying to play catch up here. -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
Hello, Marshall. As requested, here is the smb.conf file. The server is acting as a PDC for validating logins. I edited out the other shares as they are working just fine. The only change I made to this section was to make it writeable as an attempt to make it work. Everything else is the default AFAIK. Bye for now, Stuart. -----Original Message----- From: Marshall Heartley [mailto:heartley@earthlink.net] Sent: Friday, December 06, 2002 04:47 To: SuSE Linux List Subject: Re: [SLE] Printing Problems - SAMBA, CUPS and YaST2 snip
Using YaST2, I have set up the printer on lp0 using CUPS. It was auto-detected, and four queues were set up; greyscale, colour, hi-res
colour > and photo. Each of these queues works just fine for local printing. Each > of these queues show up when I browse the server from my W2K boxes, and I am > able to map my printers to them. However, when I open the printer, I see > the following error in the title bar: > > Access denied, unable to connect > > Also, I have yet to find where to set up a raw queue in YaST2 which is the > one I'll want to use as my share, as the print jobs will be processed using > the local driver on the W2K machines, and then sent to the queue on the > server for printing. > > I have been trying to work this out for two weeks, and have finally had to > hook the printer back up to my W2K laptop just to be able to print something > out. Does anyone have any ideas how to get this working ? > > Thanks, > Stuart. What does your printer section of your smb.conf file look like? What is the authentication method that you are using? You might have posted the anwser to the latter question but I'm trying to play catch up here.
On Fri, 2002-12-06 at 09:54, Stuart Powell wrote:
Hello, Marshall.
As requested, here is the smb.conf file. The server is acting as a PDC for validating logins. I edited out the other shares as they are working just fine. The only change I made to this section was to make it writeable as an attempt to make it work. Everything else is the default AFAIK.
Bye for now, Stuart.
I can't seem to see the file :-( Can you cat and pste it into the email? Thanks, -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
Hello, Marshall. Sorry for the delay; my mother-in-law passed away this week, so I haven't been able to check my mail for a couple of days. Here is the text of the-strangely-disappearing-smb.conf-file. # Samba config file created using SWAT # from 0.0.0.0 (0.0.0.0) # Date: 2002/11/16 16:26:49 # Global parameters [global] workgroup = HOMEWG netbios name = SERVER1 encrypt passwords = Yes map to guest = Bad User time server = Yes unix extensions = Yes socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY printcap name = CUPS character set = ISO8859-15 domain admin group = @ntadmin logon script = logon.bat logon path = \\server1\profiles\%U logon drive = U: logon home = \\server1\%U domain logons = Yes os level = 64 preferred master = True domain master = True wins support = Yes kernel oplocks = No printing = cups veto files = /*.eml/*.nws/riched20.dll/*.{*}/ [profiles] comment = Network Profiles Service path = /var/lib/samba/profiles/%U read only = No create mask = 0600 directory mask = 0700 nt acl support = No browseable = No [homes] comment = Home Directories valid users = %S read only = No create mask = 0640 directory mask = 0750 browseable = No [printers] create mask = 0600 browseable = No comment = All Printers writeable = yes printable = Yes path = /var/tmp [netlogon] comment = Netlogon path = /var/lib/samba/netlogon write list = @ntadmin [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 -----Original Message----- From: Marshall Heartley [mailto:heartley@earthlink.net] Sent: Friday, December 06, 2002 19:24 To: SuSE Linux List Subject: RE: [SLE] Printing Problems - SAMBA, CUPS and YaST2 On Fri, 2002-12-06 at 09:54, Stuart Powell wrote:
Hello, Marshall.
As requested, here is the smb.conf file. The server is acting as a PDC for validating logins. I edited out the other shares as they are working just fine. The only change I made to this section was to make it writeable as an attempt to make it work. Everything else is the default AFAIK.
Bye for now, Stuart.
I can't seem to see the file :-( Can you cat and pste it into the email? Thanks, -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible." -- 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
On Sun, 2002-12-08 at 20:41, Stuart Powell wrote:
Hello, Marshall.
Sorry for the delay; my mother-in-law passed away this week, so I haven't been able to check my mail for a couple of days.
No Problem. My wife had an ablation so my hands were busy too!
Here is the text of the-strangely-disappearing-smb.conf-file.
# Samba config file created using SWAT # from 0.0.0.0 (0.0.0.0) # Date: 2002/11/16 16:26:49
# Global parameters [global] workgroup = HOMEWG netbios name = SERVER1 encrypt passwords = Yes map to guest = Bad User time server = Yes unix extensions = Yes socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY printcap name = CUPS character set = ISO8859-15 domain admin group = @ntadmin logon script = logon.bat logon path = \\server1\profiles\%U logon drive = U: logon home = \\server1\%U domain logons = Yes os level = 64 preferred master = True domain master = True wins support = Yes kernel oplocks = No printing = cups veto files = /*.eml/*.nws/riched20.dll/*.{*}/ snip [printers] create mask = 0600 browseable = No comment = All Printers writeable = yes printable = Yes path = /var/tmp
[netlogon] comment = Netlogon path = /var/lib/samba/netlogon write list = @ntadmin
[print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 snip
The above seem to be ok. Can the users write to the specified directioy and does it exist. The one that I'm referring to is the path statement in the printers section. The printer does not need ot be writeable but they suggest that the printer be a read only. What does the output of the testparm tell you? Run the command as root. Installed also with SuSE's version of samba is the html version of Using Samba. A little old but you may want to read the section on printing to see if there is any tips in there. Let us know what testparm says and we will go from there. -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
participants (2)
-
Marshall Heartley -
Stuart Powell