From: Tom Callahan <callahant@tessco.com>
To: webstertrivium@trianglehead.org
Cc: linux-admin@vger.kernel.org
Subject: Re: SAMBA Privileges using cupsaddsmb
Date: Fri, 16 Dec 2005 10:56:39 -0500 [thread overview]
Message-ID: <43A2E3B7.4070305@tessco.com> (raw)
In-Reply-To: <43A1FC38.2030808@trianglehead.org>
try setting print$ to readonly=no, writable=yes and see what happens.
This would only be during the cupsaddsmb process. Then set it back to
normal.
Thanks,
Tom Callahan
TESSCO Technologies
(443)-506-6216
callahant@tessco.com
A real engineer only resorts to documentation when the keyboard dents on the forehead get too noticeable.
Kris Hollingsworth wrote:
> Hey all, I've been banging my head against the wall for the last day
> or two trying to get this working. I'm trying to get my Ubuntu Linux
> (Breezy Badger 5.10 release) to serve up print drivers to my windows
> box when trying to share the printer attached to it.
>
> I think I've got it almost there, I've just run into a problem with
> permissions on the smbclient commands in the cupsaddsmb.
>
> I've only been using linux for about a week, so any help on this would
> help me out immensely.
>
> /etc/samba/smb.conf
> ------------------------------------------
> [global]
> load printers = yes
> printing = cups
> printcap name = cups
>
> [printers]
> path = /var/spool/samba
> browseable = no
> public = yes
> guest ok = yes
> writable = no
> printable = yes
> printer admin = webster
>
> [print$]
> path = /etc/samba/drivers
> browseable = yes
> guest ok = no
> read only = yes
> ------------------------------------------
>
> I setup the samba user with:
> ------------------------
> smbpasswd -a webster
> ------------------------
>
> I used the command
> --------------------
> cupsaddsmb -a -v
> --------------------
>
> and the result was:
> ------------------------------------------------------------------------------------
>
> Password for webster required to access localhost via SAMBA:
> Running command: smbclient //localhost/print\$ -N
> -U'webster%[password]' -c 'mkdir W32X86;put /var/tmp/439fb7d81ff33
> W32X86/PSC-1300.ppd;put /usr/share/cups/drivers/ps5ui.dll
> W32X86/ps5ui.dll;put /usr/share/cups/drivers/pscript.hlp
> W32X86/pscript.hlp;put /usr/share/cups/drivers/pscript.ntf
> W32X86/pscript.ntf;put /usr/share/cups/drivers/pscript5.dll
> W32X86/pscript5.dll'
> Domain=[NARSHE] OS=[Unix] Server=[Samba 3.0.14a-Ubuntu]
> NT_STATUS_NETWORK_ACCESS_DENIED making remote directory \W32X86
> NT_STATUS_ACCESS_DENIED opening remote file \W32X86/PSC-1300.ppd
> NT_STATUS_ACCESS_DENIED opening remote file \W32X86/ps5ui.dll
> NT_STATUS_ACCESS_DENIED opening remote file \W32X86/pscript.hlp
> NT_STATUS_ACCESS_DENIED opening remote file \W32X86/pscript.ntf
> NT_STATUS_ACCESS_DENIED opening remote file \W32X86/pscript5.dll
> ------------------------------------------------------------------------------------
>
>
> I can do:
> ------------------------------------
> smbclient //localhost/print\$ -N -U'webster%[password]' -c
> ------------------------------------
> and browse around, ls the file list, etc. I just can't change anything.
>
> If anyone could help me with the NT_STATUS_ACCESS_DENIED errors, I
> would greatly appreciate it!
>
> -Kris
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2005-12-16 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 23:28 SAMBA Privileges using cupsaddsmb Kris Hollingsworth
2005-12-16 15:56 ` Tom Callahan [this message]
2005-12-16 16:01 ` Scott Taylor
-- strict thread matches above, loose matches on Subject: below --
2005-12-16 16:33 Scott Taylor
2005-12-14 7:09 K. Hollingsworth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43A2E3B7.4070305@tessco.com \
--to=callahant@tessco.com \
--cc=linux-admin@vger.kernel.org \
--cc=webstertrivium@trianglehead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.