Comment #5 works also for me with both server and client running Ubuntu
12.04. Without that directive it seems there's some privileges problems
with the nobody user (the default bad-user mapping)
Excerpt from server's smb.conf:
[global]
map to guest = bad user
## Printing ##
Comment #5 works for me as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/990388
Title:
acces denied samba printer shares after upgrade precise
To manage notifications about
Fix as described in askubuntu #7 worked for me. I copy it here for
reference with some adaptions, credits go to RobDavenport.
== Set up printer shared on a sambe network with authentication ==
Choose Add new printer in Printing, click open 'Network Printers',
select 'Windows Printer via
Adding 'use client driver = yes' worked for me also.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/990388
Title:
acces denied samba printer shares after upgrade precise
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/990388
The fix in Comment #5 worked for me; adding 'use client driver = yes'
under the [printers] section of /etc/samba/smb.conf
Same situation as OP: Ubuntu 11.10 upgrades to 12.04.
Windows client: Windows XP
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Could affected users who haven't already reported please report whether
the workaround of adding use client driver = no works for you, or if
it fails for you?
Assuming that use client driver = yes fixes the problem, it seems to
me that this is a question about how the Windows printer driver
Hallo,
Am 25.06.2012 14:46, schrieb Robie Basak:
Could affected users who haven't already reported please report whether
the workaround of adding use client driver = no works for you, or if
it fails for you?
Diese Konfigurationseinstellung use client driver = yes|no hatte ich
bis Precise
Can also be a Samba problem as a change in smb.conf solves the problem.
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
