LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Samba + CUPS "Access denied, unable to connect" error (http://www.linuxquestions.org/questions/linux-networking-3/samba-cups-access-denied-unable-to-connect-error-322874/)

lirik 05-12-2005 05:14 PM

Samba + CUPS "Access denied, unable to connect" error
 
I was setting up printer sharing to Windows machines on my home network via Samba yesterday, and got following bizarre problem -- I can print from Windows fine but printer status on Windows box reads "Access denied, unable to connect" instead of Ready or Printing or whatever. Effectively there is no access to the printer queue for some reason. I was googling for quite some time, and it seems many people having the same problem but very few solutions were offered. At the end I came across this page which solved my problem. So I am posting it here in case if other linux users have the same problem.

Quoting the page linked above:

I managed to get that fixed by adding the line use client driver = yes to the [printers] section of /etc/samba/smb.conf.

Also as Colin points out it is important to activate raw octet-stream mime type in CUPS.

One questions bugs me though -- why "use client driver = yes" solved the problem with printer queue accessibility from Windows? On a side note, my Mac printed through Samba perfectly without this option and was able to read a queue as far as I remember.

Hope this post will save someone a bit of time.

Cheers.

tuxrules 05-16-2005 03:31 PM

Hey I have the same problem and I had already done what you mentioned in the post since a long time but I still get the "Unable to Connect" error. I don't know what's the problem. I have a dual-boot desktop (mostly run linux) and a printer connected to it. I also have a laptop (also a dual-boot) from where I am trying to print. One amazing thing is that I am unable to print via windows on laptop but if I boot in Linux I can print just fine. I don't know what the problem is?

Tux

lirik 05-17-2005 04:12 AM

tuxrules, if you really can't print from windows, then you problem may lie elsewhere. Since the problem I had was different -- I was able to print, but could not access printer queue status.

When you are printing from linux are you printing over Samba as well? Or is it just plain CUPS? I am quite a newbie in Samba administration and can't really recommend anything apart from regular 1. run testparm 2. take a look into samba logs 3. if above steps do not help, increase logging verbosity and examine logs again

Cheers.

tuxrules 05-17-2005 08:31 AM

I am trying to print from my laptop (via a wireless network) to the printer attached my desktop. Now my desktop mostly runs on linux with samba on. My laptop (also dual boot with Linux) with windows on can access files on my desktop via samba but cannot print. However, when i turn on linux on my laptop its prints perfects via samba. I've checked error logs and I've also done what you said in your post. I am kinda thinking it may be a permission question with cups. I am kinda thinking of making a group which contains all the users who can print via samba and then adding that group via chown to cups.

I am not sure if this is good idea.

Tux,

philiplawlor 05-19-2005 03:50 PM

Just add this line to your printer section of smb.conf:

use client driver = Yes

Reference:http://lists.freebsd.org/pipermail/f...ry/030676.html

It worked for my fedora fc3

tuxrules 05-19-2005 08:44 PM

Hi philiplawlor,
Thanks for the input. However I've already done what you suggested but to no avail. I followed the article your referred and doesnt seem to do the trick for me.

Here's my smb.conf
Code:

# Samba config file created using SWAT

# Global parameters
[global]
        workgroup = KUIPERBELT
        server string = Samba Server on K2
        guest account = No
        log file = /var/log/samba/%m.log
        max log size = 0
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        ldap ssl = no
        valid users = user1,user2
        admin users = user1
        write list = user1, user2
        hosts allow = xxx.xx.

[homes]
        comment = Home Directories
        read only = No

[Baroda]
        comment = LexmarkX63
        path = /var/spool/samba
        read only = No
        guest ok = Yes
        printable = Yes
        printer name = Baroda
        use client driver = Yes

Hope to crack this mystery :)

hyjalsoul 08-14-2007 03:37 PM

Thanks,guys,this is a great solution,I just met this problem today and I solved it with your help! Cheers!

dthibeau 03-22-2008 10:54 AM

Windows Printing to Linux Deskjet
 
When I first saw this I thought I might have found my solution. However, I still can't print from my Windows Laptop to a Linux-based HP Deskjet printer. The error in the log says:

smbd/nttrans.c:call_nt_transact_ioctl(2463)
call_nt_transact_ioctl(0x280004): Currently not implemented.
printing/print_cups.c:cups_job_submit(656)
Unable to print file to DESKJET_895C - clitent-error-document-format-not-supported

The document was the Windows Test Page. Any thoughts?

LordJimFr 07-13-2011 08:02 AM

use client driver = yes

ghabre 09-21-2011 05:02 PM

Linux FC 15 + Virtual Box with Virtualized XP
 
Thanks Pal! With such an strange configuration I could print over the Virtual Network on my Virtual XP Box to my Samba printer!!

masodo 10-13-2011 02:09 PM

Having already applied the "use client driver = yes" line to my smb.conf I was a bit disappointed to discover this topic did nothing to resolve my "access denied" error when trying to print to the (CentOS-6/cups/samba) shared DELL 3110cn printer on my network.

I could print fine from the Linux Server with Dell's PS drivers but no joy when attempting to print from XP machines - until I took my clue from "use client driver = yes" . . .

I have been successfully printing to this printer for years when it was served via a Win2000 server but I used the DELL PCL drivers. However, when I installed it to print to the Linux Server I chose the PS drivers (since it seemed to work so well for CUPS) - bad move - once I reinstalled the network printer using the PCL drivers. . . It Worked Perfectly!


All times are GMT -5. The time now is 08:06 PM.