Looks fine to me, if you log in via ssh, do you see the two user entries in:
/etc/passwd
What are the permissions of /mnt/User2
ls -la /mnt/User2
I'm trying to set up some options in Samba server but I don't get User2 to work.
Only User1 and Public. What have I written wrong ? I'm on build 15962-mega
[Global]
server string = rt-n16
workgroup = workgroup
interfaces = br* <<<=== does this work with 15962-mega ?
bind interfaces only = Yes
map to guest = Bad User
smb passwd file = /var/samba/smbpasswd
private dir = /var/samba
passdb backend = smbpasswd
log file = /var/smbd.log
max log size = 1000
printing = none
load printers = No
usershare allow guests = Yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
[User1]
comment = User1 share
path = /mnt/User1
read only = No
guest ok = No
valid users = User1
[User2]
comment = User2 share
path = /mnt/User2
read only = No
guest ok = No
valid users = User2
[Public]
comment = Public Share
path = /mnt/public
read only = No
guest ok = Yes
guest only = Yes
Regards
kt_haddock
This in /etc/passwd :
user1:*:1000:1000:user1:/var:/bin/false
user2:*:1001:1001:user2:/var:/bin/false
root@NOD-E36-01:~# ls -la /mnt/User2
drwxr-xr-x 2 root root 16384 Jan 11 21:01 .
drwxr-xr-x 5 root root 16384 Jan 11 21:00 ..
-rwxr-xr-x 1 root root 12 Jan 11 17:28 user2.txt
That what I get
And this in Custom Configuration box:
[global]
server string = rt-n16
workgroup = workgroup							
interfaces = br*				
bind interfaces only = yes
map to guest = Bad User
smb passwd file = /var/samba/smbpasswd
private dir = /var/samba
passdb backend = smbpasswd
log file = /var/smbd.log
max log size = 1000
printing = none
load printers = no
usershare allow guests = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
[user1]
comment = user1 share
path = /mnt/user1
read only = no
guest ok = no
valid users = user1
[user2]
comment = user2 share
path = /mnt/user2
read only = no
guest ok = no
valid users = user2
[public]
comment = public Share
path = /mnt/public
read only = no
guest ok = yes
guest only = yes
root@NOD-E36-01:~# ls -la /mnt
drwxr-xr-x 5 root root 16384 Jan 11 21:00 .
drwxr-xr-x 16 root root 162 Dec 24 02:18 ..
drwxr-xr-x 2 root root 16384 Jan 11 21:01 public
drwxr-xr-x 2 root root 16384 Jan 11 21:01 user1
drwxr-xr-x 2 root root 16384 Jan 11 21:01 user2
root@NOD-E36-01:~# ls -la /mnt/user2
drwxr-xr-x 2 root root 16384 Jan 11 21:01 .
drwxr-xr-x 5 root root 16384 Jan 11 21:00 ..
-rwxr-xr-x 1 root root 12 Jan 11 17:28 user2.txt
I haven't mention I tested with FAT32 USB
Fat32:-) Add this line to your [user2] definition:
force user = root
e.g.:
[user2]
comment = user2 share
path = /mnt/user2
read only = no
guest ok = no
valid users = user2
force user = root
When I put "force user = root" to user2 then I get write acess to user2 I only testing with FAT32 I usually use Ext3 who is much faster.
I have found this in your older threed, can this be the problem ?
If you first connect to Share1 and then to Share2 Windows is still holding a
connection to Share1 and that is why Wikndows tells you that you cannot
connect multiple times with different users, see the error message:-)
So this is purely a windows problem, which can solved for example through a reboot.
Is there any other way to "relese" holding ?
regards
kt_haddock
It sometimes works if you disconnect the network share by rightclicking on the share.
The problem why you need force user = root is that by default samba accesses the drive as the specified user in case of fat32 dd-wrts default is to mount a fat32 as root without setting an umask so other users have rights.
In my previous builds I did mount a fat32 partition with umask, but as dd-wrt guys did not follow my way and since I want to comply with dd-wrt as much as possible I adopted dd-wrts way. The less differences I have the easier I can merge in their updates.
Okey
Is this only related to Fat32, with Ext3 I don't need to do put forced user in?
I have "force user = root" in user1, user2 and public then I get write access to them. Have I get this right ?
If I reboot Pc and try access my samba share public, then I have to give user and password to get access to public and user1 or 2 depend wich password I get
@Kong
I tested again. Put samba settings in custom configuration box and rebot PC I can't browse public folder I have to login with either user1 or user 2 login. after that I can use public but I still have to login to user1 or user 2.
What is the different between your build and that I'm testing with, 15962-mega ? Fat32 I knowing but more ?
Ragards
kt_haddock
I have tseted much more and It's working if I use Vista.
When I tested from my windows 7 ultimate x64 I have to set user/password to reach public folder. Using Ext3 filesystem
I have set:
HKLM\System\CCS\Services\LanmanWorkstation\Parameters
DWORD DomainCompatibilityMode = 1
DWORD DNSNameResolutionRequired = 0
Have set "Network security: LAN Manager authentication level" to "1"
I still get login "windows security" and "assign networkpassword"
If I just put ex: user: "a" password: "a" then I can reach public
>>> How to set a blank password to public ??? <<<
Now I'm out of ideas
Regards
kt_haddock

RSS

