Originally Posted by
Morbius1
Did you ever create a user on the Ubuntu server for her and then add her to the samba password database? If you did the share you created will not allow write access.
That HowTo has you:
** Create a directory at /srv/samba/share
** Change ownership to nobody:nogroup
** What's not stated explicitly is the permissions are automatically set to 755.
** Then he has you create the share:
If you ever create a share that requires credentials or in the case of a Windows client ever create a Linux user for that Windows user and give her a samba password then they are no longer "nobody". They are somebody and they will no longer have write access.
It's a bad HowTo which is why I stated earlier that they either need to take it down or open it up to peer review so that it can be fixed. There are a hundred ways to fix it but one of the easiest ways is to add one line to the share definition:
Then restart samba:
Code:
sudo service smbd restart
thanks for being patient with me!!
yes: she does have a log-on for the Ubuntu computer -- and for Windows
Code:
# (smbusers)
# ubuntuuserid = "WindowsUserID"
jennifer = "Jennifer"
i think i added her with smbpassword -- how do i check that ? pdbedit shows she does have a user id
when she logs onto Windows -- she does not see the *nix box under networks
i just re-checked this this morning: although my windows logon finds the *nix box -- hers does not
~~~
I agree with you on the how-to for Samba. one of the thngs i've noticed about Ubuntu/Linux is it's importatn to have documentation for the exact version that is being used.
~~~
my original thinking on Samba was that I would (1) create a Ubuntu User ID for her and then allow her to connect to that from her Windows machine. access should then be the same as if she logged onto the Ubuntu machine directly .
Amendment:
I think I found the problem : in the Windows computer I turned "Network Discovery" on in the Control Panel in the Home Networks section using her logon. Now she has access.
This is the reason why that Howto document needs to be peer reviewed: information is missing/inaccurate. at this point it appears the problem is the how-to document rather than the software.
Bookmarks