From: Mark Nienberg on
willem.botha(a)adticket.de wrote:

> I connect my Linux clients with a fstab entry:
> //192.168.1.127/sharefiles /mnt/fileserver cifs
> credentials=/home/.auth,rw,soft 0 0

Here is an example from my server:
//192.168.254.35/projects /mnt/engin cifs
noperm,uid=enginuser,gid=Engineers,credentials=/root/creds 0 0

Does that help?
--
Mark Nienberg
Sent from an invalid address. Please reply to the group.

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Gary Dale on
Willem P. Botha wrote:
>> OK. So now try removing the credentials entirely. Also, set the log
>> level in smb.conf to 10 and restart it. Then connect from the command
>> line (as root) using -o username=fileserver,domain=....
>>
>> See if you get an error message and also check the logs.
>>
>>
> OK, first off, no matter what I do, I have to provide a password... or
> else I can't connect. Regardless if I add a domain or not. The security
> is set to user level, so this is what I think should happen...or am I
> wrong?
>
Yes. I just don't enter passwords in a command. Let the program prompt
you for it.

> Log level 10 is Crazy man... :-O
>
> If I give the password, then it connects fine. The log file said :
> connecting to <service> initially as fileserver(gid uid pid)....
>
> if I unmount the service the log file also response with a connection
> closed..
>
> So it is allowing me to connect no problem, but still the problem is
> that the files on the share, is mapped to my local user-list, so Samba
> is not actually giving me any error.
> When I try to copy a file on this share, the log file does nothing !
>
> It seems my local machine is preventing this from happening, not samba.
> It seems to figure out that the uid and gid for the remote folder is set
> to something else than the current user, and thus preventing me from
> writing to this service.
>
> The remote machine provides me a folder with write access for uid=501
> and gid=501
>
> The local machine sees a folder with write access for uid=501,gid=501
> My current user is uid=503, hence the permission denied.
>
> My problem is not the connection.. it's writing files. Still I am lost
> at how to map the remote uid to the local uid, or the authenticated
> user..??
Have you tried connecting as your user account and letting the force
user in smb.conf do its work? When your Windows clients connect, they
are using their own ids and that is working. Why are you doing it
differently for Linux?

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Willem P. Botha on
> Have you tried connecting as your user account and letting the force
> user in smb.conf do its work? When your Windows clients connect, they
> are using their own ids and that is working. Why are you doing it
> differently for Linux?
>
Now that is the weird thing, The windows clients are also connecting
with the same details. There is now domain controller on this network.
Everybody connect to a DHCP server that the Router manages, and thus I
have a browse master war in my network, but that is another problem.

So far I can figure, the windows clients don't have the same gid's as
Linux, and thus don't have the same problem. I am just not sure how
windows figures that it should use the login user to save files.

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Gary Dale on
Willem P. Botha wrote:
>> Have you tried connecting as your user account and letting the force
>> user in smb.conf do its work? When your Windows clients connect, they
>> are using their own ids and that is working. Why are you doing it
>> differently for Linux?
>>
>>
> Now that is the weird thing, The windows clients are also connecting
> with the same details. There is now domain controller on this network.
> Everybody connect to a DHCP server that the Router manages, and thus I
> have a browse master war in my network, but that is another problem.
>
> So far I can figure, the windows clients don't have the same gid's as
> Linux, and thus don't have the same problem. I am just not sure how
> windows figures that it should use the login user to save files.
>
>
You're using username "fileserver" to connect the share on Windows?

After giving it some more thought, I still cannot figure out what you
are trying to do. If you want to give everyone write access to the
files, why not just set the permissions to a+rwx and forget about all
this "force user" stuff? I suspect that turning off "guest" access and
opening it up to anyone who can provide connection privileges will work
better.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Willem P. Botha on

> Here is an example from my server:
> //192.168.254.35/projects /mnt/engin cifs
> noperm,uid=enginuser,gid=Engineers,credentials=/root/creds 0 0
>
> Does that help?

The param noperm seems to do the trick :D

I left the uid and gid out, and even though my permissions in my KDE
browsers is still false, it allows me to delete and copy files to the
share..

I guess this is the default behaviour of Windows then.

Thanks a million Mark :D

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba