Samba and the pain of having all your teeth kicked in.
by dravur from LinuxQuestions.org on (#5EJ17)
Im back with another Samba issue. Yes, Apparently, I am a glutton for punishment.
Having failed with the earlier Samba issue, I spun up a new Redhat 8 system on Azure. I then found a site on the internet that showed how to set up a basic Samba and I followed it religiously. I have not signed this into Redhat yet as I am just testing this one for samba compatibility before I transfer everything from old server to new.
However, after setting up Samba, i can see the shares, but not access them. the share is /u right off the root and the permissions are set to 777 and owner is set to ccas:ccas which is a user and an smb user.
content of the smb.conf is.
[global]
workgroup = SAMBA
security = user
passdb backend = tdbsam
log file = /var/log/samba/log.%m
log level = 2
printing = cups
printcap name = cups
load printers = yes
cups options = raw
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = Yes
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775
[u]
comment = Linux Directories
path = /u
public = yes
writeable = yes
create mask = 775
directory mask = 775
force create mode = 775
force directory mode = 775
force user = ccas
force group = ccas
The users are added using the smbpasswd -a etc andI can see the /u filesystem yet cannot open it. I also cannot open the home or the user filesystem. It is puzzling.
Here is the log file final chunk
[2021/02/23 15:33:14.348007, 2] ../../source3/smbd/service.c:1131(close_cnum)
b-0936 (ipv4:<IP ADDRESS>:41759) closed connection to service <username>
[2021/02/23 15:33:14.348076, 2] ../../source3/smbd/service.c:1131(close_cnum)
b-0936 (ipv4:<IP ADDRESS>:41759) closed connection to service u
[2021/02/23 15:33:14.348110, 2] ../../source3/smbd/service.c:1131(close_cnum)
b-0936 (ipv4:<IP ADDRESS>:41759) closed connection to service shawn.shipley
[2021/02/23 15:33:29.309439, 1] ../../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
Failed to fetch record!
[2021/02/23 15:33:29.309490, 1] ../../source3/smbd/server_reload.c:64(delete_and_reload_printers)
pcap cache not loaded
[2021/02/23 15:33:31.745862, 1] ../../source3/param/loadparm.c:2495(lp_idmap_range)
idmap range not specified for domain '*'
[2021/02/23 15:33:31.748625, 2] ../../source3/smbd/service.c:851(make_connection_snum)
b-0936 (ipv4:<IP ADDRESS>:33304) connect to service u initially as user ccas (uid=1003, gid=1003) (pid 705605)
B-0936 is my PC name.
Any ideas why it lets me browse to he see the shares, but once there, it doesnt let me into the share? that idmap range up there looks mighty suspicious.
Having failed with the earlier Samba issue, I spun up a new Redhat 8 system on Azure. I then found a site on the internet that showed how to set up a basic Samba and I followed it religiously. I have not signed this into Redhat yet as I am just testing this one for samba compatibility before I transfer everything from old server to new.
However, after setting up Samba, i can see the shares, but not access them. the share is /u right off the root and the permissions are set to 777 and owner is set to ccas:ccas which is a user and an smb user.
content of the smb.conf is.
[global]
workgroup = SAMBA
security = user
passdb backend = tdbsam
log file = /var/log/samba/log.%m
log level = 2
printing = cups
printcap name = cups
load printers = yes
cups options = raw
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = Yes
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775
[u]
comment = Linux Directories
path = /u
public = yes
writeable = yes
create mask = 775
directory mask = 775
force create mode = 775
force directory mode = 775
force user = ccas
force group = ccas
The users are added using the smbpasswd -a etc andI can see the /u filesystem yet cannot open it. I also cannot open the home or the user filesystem. It is puzzling.
Here is the log file final chunk
[2021/02/23 15:33:14.348007, 2] ../../source3/smbd/service.c:1131(close_cnum)
b-0936 (ipv4:<IP ADDRESS>:41759) closed connection to service <username>
[2021/02/23 15:33:14.348076, 2] ../../source3/smbd/service.c:1131(close_cnum)
b-0936 (ipv4:<IP ADDRESS>:41759) closed connection to service u
[2021/02/23 15:33:14.348110, 2] ../../source3/smbd/service.c:1131(close_cnum)
b-0936 (ipv4:<IP ADDRESS>:41759) closed connection to service shawn.shipley
[2021/02/23 15:33:29.309439, 1] ../../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
Failed to fetch record!
[2021/02/23 15:33:29.309490, 1] ../../source3/smbd/server_reload.c:64(delete_and_reload_printers)
pcap cache not loaded
[2021/02/23 15:33:31.745862, 1] ../../source3/param/loadparm.c:2495(lp_idmap_range)
idmap range not specified for domain '*'
[2021/02/23 15:33:31.748625, 2] ../../source3/smbd/service.c:851(make_connection_snum)
b-0936 (ipv4:<IP ADDRESS>:33304) connect to service u initially as user ccas (uid=1003, gid=1003) (pid 705605)
B-0936 is my PC name.
Any ideas why it lets me browse to he see the shares, but once there, it doesnt let me into the share? that idmap range up there looks mighty suspicious.