I'm getting grief when trying to connect to bubba using my windows machines.
I want to map a drive for a particular user on each PC. But I keep getting Multiple connections by the same user denied type error messages.
Is it possible increase the number of times a user can be logged into a samba share.
New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
Multiple [Samba] connections by same user
-
- Posts: 53
- Joined: 11 Jun 2007, 17:12
- Location: East of England
-
- Posts: 53
- Joined: 11 Jun 2007, 17:12
- Location: East of England
I had previously set up a working Samba configuration on a Fedora Core machine. When I ordered the bubba I expected to have to set up Samba again on it somehow but I didn't expect that it would be as easy as it in fact turned out.
I set up accounts on bubba through the admin browser interface with the same user names and passwords as I use in Windows. Then I looked to understand what bubba did. Of course, bubba uses Samba too, so doing this created matching Samba-users on bubba as well. I then looked at the smb.conf file to see how that worked. When I was fairly confident that I understood it, I made some minor changes to the global section, left the Share Definitions section alone (because, though I haven't yet had cause to use them, this section must be available for the users' browsed files, I guess) and added my original shares in the Customised Shares section.
This is my smb.conf:
IIRC, the changes made in global were the workgroup, and server string and, possibly, map to guest.
Once this was done, I was able to copy my old shares' contents across verbatim and everything just worked. Well, that's not true, actually, because I still had to tweak certain Windows applications - go figure!
I hope this helps.
I set up accounts on bubba through the admin browser interface with the same user names and passwords as I use in Windows. Then I looked to understand what bubba did. Of course, bubba uses Samba too, so doing this created matching Samba-users on bubba as well. I then looked at the smb.conf file to see how that worked. When I was fairly confident that I understood it, I made some minor changes to the global section, left the Share Definitions section alone (because, though I haven't yet had cause to use them, this section must be available for the users' browsed files, I guess) and added my original shares in the Customised Shares section.
This is my smb.conf:
Code: Select all
[global]
workgroup = PRESSURIZED
server string = %h Miniserver
dns proxy = no
log file = /var/log/samba/log.all
max log size = 1000
syslog = 0
security = user
encrypt passwords = true
passdb backend = tdbsam guest
obey pam restrictions = yes
guest account = nobody
invalid users = root
map to guest = Bad User
socket options = TCP_NODELAY
preferred master = yes
load printers = yes
printcap name = cups
printing = cups
show add printer wizard = no
disable spoolss = Yes
#======================= Share Definitions =======================
[home]
comment = Home Directories
path = /home
browseable = yes
writable = yes
create mask = 0764
directory mask = 0775
public = no
guest ok = no
hide dotfiles = yes
user = @users
[storage]
comment = Common storage
writable = yes
guest ok = yes
public = yes
force group = users
force create mode= 0777
force directory mode = 0777
path = /var/samba/public
[printers]
comment = Attached printers
path = /var/spool/samba
browseable = no
guest ok = yes
printable = yes
use client driver = yes
#-------------------Customised Shares-------------------------------------
[My Network Documents]
comment = Private network documents
path = /home/shares/%U
valid users = %U
read only = no
[Shared Network Documents]
comment = Shared network documents
path = /home/shares/surname
valid users = adrian,angela
force group = surname
read only = no
[Guest]
comment = Guests' read-write share
path = /home/shares/guest
force user = adrian
force group = surname
guest ok = yes
read only = no
[Archives]
comment = Archived files
path = /home/shares/archives
valid users = adrian
read only = no
[Backups]
comment = Backups on Bubba
path = /home/backups
valid users = adrian
read only = no
[Logs]
comment = Bubba logs
path = /home/logs
valid users = adrian
read only = no
Once this was done, I was able to copy my old shares' contents across verbatim and everything just worked. Well, that's not true, actually, because I still had to tweak certain Windows applications - go figure!
I hope this helps.