Please check the following:- 

 

1)       Permission on /var/lib/samba/driver folder. 

a.       start --> run --> //servername/print$   (in windows client machine)

b.       please make sure you have permission to create file and folders on
drivers/WX3286/3

If you have then the permission is fine. Else please check the permission on
the driver folder.

 

2)       Add the following on the smb.conf file so that you can upload the 

[print$]

Write list = Administrator, xyz

3)       try to upload the drivers on the cups server  by doing the
following:-

a.       start --> run --> //servername

b.       click on printers and faxes 

c.       right click on your printer 

d.       Click advance tab and upload the driver.

 

I had similar problems and I fixed it with above steps.

 

Hope this will be some help.

 

Thanks

 

Rajeev

 

 

  _____  

 

 

From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf
Of Riyaz Mirza
Sent: Wednesday, February 14, 2007 10:43 AM
To: [email protected]
Subject: Re: [dubailug] Printer woes

 

Did you login as Administrator in windows client, you need to.

Akshay Lamba <[EMAIL PROTECTED]> wrote: 

Hi All,

I'm sure this has been done multitude of times, somehow I don't seem to 
be able to get it though. I have setup a print server (well basically 
just sharing a printer) on a ubuntu box. While the printer works just 
fine on the ubuntu machine, and I have shared it using samba (pretty 
much just used the defaults in smb.conf). However, when I access the 
printer from a windows client, it is able to open the share just fine 
(post authentication), I am able to "connect" the printer to the windows 
box, however, it then gives me a authentication failure error. So a 
print does not go through.

Any pointers would be appreciated.

Best,
Akshay

 

  

  _____  

Have a burning question? Go to Yahoo!
<http://answers.yahoo.com/;_ylc=X3oDMTFvbGNhMGE3BF9TAzM5NjU0NTEwOARfcwMzOTY1
NDUxMDMEc2VjA21haWxfdGFnbGluZQRzbGsDbWFpbF90YWcx>  Answers and get answers
from real people who know.

 

Reply via email to