Hello all, System background first: -Server = Mandrake-Linux 7.2, Kernel 2.2.17 (Distro Kernel), SAMBA 2.0.7 -Workstation1 = Win95 -Workstation2 = Win2000 Pro -Users and passwords entered in smbpasswd, workstation logins = Unix user/password pair, IP/NetBios entered in lmhosts, users placed in smbusers, working smb.conf -Each workstation uses identical drive/share mappings and each can successfully connect and map to the SAMBA server. Problem: When both computers try to connect to the SAMBA server, only occasionally will they successfully map the shares. More often than not, one or the other will not be able to connect at all. I've tried reading the docs, changing the smb.conf file, using SWAT, WEBMIN and configuring with vi and just when I think it's working well, I turn them both off for the night. The next day, I turn them both on and one of them won't map the shares. I've tried waiting for one of them to finish booting before booting the other one and it seems to make no difference. What am I doing wrong ? What can I do to fix the problem ? The computers sit next to each other so my kids can work nearby. Thanks in advance for any assistance -------------- Trent M. Gunnarson Privacy is a way of life nobody can afford to neglect.
Hi all: Please accept my apology as a newbie to samba and the list.
System background first:
-Server = Mandrake-Linux 7.0, Kernel 2.2.14-15 (Distro Kernel), SAMBA 2.0.6
-Workstation1 = Win95
-Workstation2 = Win98
-Workstation3 = Win98
-Users and passwords entered in smbpasswd, workstation logins = Unix
user/password pair, users placed in smbusers, working smb.conf
-Each workstation uses identical drive/share mappings and each can
successfully connect and map to the SAMBA server. (even at the same time!)
Problem: Unless (using SWAT). UNLESS I put the following in the share
area, users do not have the authority to write to their share.
this works: (share info follows:)
[mooer]
valid users = mooer
admin users = mooer ((
write list = mooer
invalid users = family
This DOESNT work:
[mooer]
valid users = mooer
admin users = mbruntel (me)
write list = mooer
invalid users = family
SO, essentially, unless I have each user's (home) share set that THEY are an
admin user, it doesn't work.
BTW, I am successfully using encryption, wins support, and successfully
using samba as the domain logon controller (I use NO NT [thank heavens...])
<Mitch Bruntel>