public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: reader@newsguy.com
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  [samba] No write to linux shares
Date: Fri, 25 Aug 2006 11:39:53 -0500	[thread overview]
Message-ID: <877j0w3h2e.fsf@newsguy.com> (raw)

I've posted this here because I know the advice on the samba list will
be to update to samba-3.0.23b  from previous posts there, however it
appears there is no ebuild for that in todays sync and I'm not
conversant enough with doing my own to update that way.

Further I'm guessing several people here are running samba-3.0.23a
without this write problem... so rather than argue with developers on
samba list who will just tell me to update and see if problem is still
there, I'm asking for help here from any savvy samba users running the
current build available on portage.

I'm able to see and navigate to the linux shares from a winxp box, but
not able to write to the share.  I've defined the share to have write
abiltity like this in smb.conf:

 [smWinBk]
   comment = ""
   valid users = reader Harry
   path = /anex2/win_bk/
   writeable = yes
   guest ok = yes


The log from an attempt to write to the above share shows there is no
write priviledge:

(I'm not sure where the log actually starts for this attempt but will
include a few lines showing the Write=no- (Samba logs are basically
unintelligable far as I can tell))

The line  of note is marked off with asterisks and I've included one
before and after.  Following the write info line, and dozens of lines
further along we finally see the denial, also marked off with
asterisks. 

I've opened a text file named AlienSkin.txt and attempted to alter its
contents using a winxp editor and working from a winxp box.

Can anyone here tell me what might be causing the write failure?  I
see no evidence of authentication or password problems so guessing
that isn't an issue here.

============================

[2006/08/25 11:04:42, 3] smbd/dosmode.c:unix_mode(147)
  unix_mode(AlienSkin.txt) returning 0744

***
[2006/08/25 11:04:42, 2] smbd/open.c:open_file(352)
  Harry opened file AlienSkin.txt read=Yes write=No (numopen=1)
***

[2006/08/25 11:04:42, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(167)
  linux_set_kernel_oplock: got kernel oplock on file AlienSkin.txt, dev = 308, inode = 3989, file_id = 1

 [...] snipped about 65 lines

[2006/08/25 11:04:48, 3] smbd/dosmode.c:unix_mode(147)
  unix_mode(AlienSkin.txt) returning 0744

*****
[2006/08/25 11:04:48, 3] smbd/open.c:open_file(278)
  Error opening file AlienSkin.txt (Permission denied) (local_flags=2) (flags=2)
[2006/08/25 11:04:48, 3] smbd/error.c:unix_error_packet(90)
  unix_error_packet: error string = Permission denied
****

[2006/08/25 11:04:48, 3] smbd/error.c:error_packet(146)
  error packet at smbd/trans2.c(2682) cmd=162 (SMBntcreateX) NT_STATUS_ACCESS_DENIED





-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2006-08-25 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25 16:39 reader [this message]
2006-08-25 22:49 ` [gentoo-user] [samba] No write to linux shares Ryan Tandy
     [not found] ` <8146fc8a0608251046m44f750c5mcd6b79606b69eea7@mail.gmail.com>
2006-08-26  3:09   ` [gentoo-user] " reader

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=877j0w3h2e.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox