Hi!
The path to your drivers is not relevant.
When you connect from windows to your samba server, you are mapped
(somehow) to a *nix user on the samba server.
This user needs access rights on the driver directory. That's the
important thing. You can check this basic settings by typing on your
Peter Van den Wildenbergh wrote:
Daniel L. Miller wrote:
Hi!
Trying to trace down a problem with printer sharing. I don't see
anything glaringly obvious with my smb.conf. I am using LDAP and CUPS.
Using a Windoze client, accessing a printer I receive the friendly
"Access denied, unable to
Michael Heydon wrote:
You are getting close :)
But not close enough yet...
It is a driver related issue, you can either install windows drivers
onto the samba server. This has the benefit of when ever you add the
printer to a client the drivers will be installed automagically.
That's the pa
Using a Windoze client, accessing a printer I receive the friendly
"Access denied, unable to connect". Checking the Samba logs, I find:
Alrighty then... I think I got it... almost (*)
changed in smb.conf section : [print$]
path = /usr/share/cups/drivers
# path = /var/lib/samba/printers
Peter Van den Wildenbergh wrote:
Daniel L. Miller wrote:
Hi!
Trying to trace down a problem with printer sharing. I don't see
anything glaringly obvious with my smb.conf. I am using LDAP and CUPS.
Using a Windoze client, accessing a printer I receive the friendly
"Access denied, unable to
Daniel L. Miller wrote:
Hi!
Trying to trace down a problem with printer sharing. I don't see
anything glaringly obvious with my smb.conf. I am using LDAP and CUPS.
Using a Windoze client, accessing a printer I receive the friendly
"Access denied, unable to connect". Checking the Samba log
