Displaying 3 results from an estimated 3 matches for "udvhome".
Did you mean:
dvhome
2019 Feb 22
2
lookup_name_smbconf for <user> failed
.../samba/smb.conf.%h' ?
>
On the old system all servers uses the same smb.conf and then all the uniq
shares are defined in smb.conf.<hostname>
The content can then be seen with this command
# grep -v "#" smb.conf.$(hostname -s)
[global]
server string = Samba %v paa %L(%h): udvhome
[homes]
comment = Home Directories
browseable = no
writable = yes
read only = no
create mask = 0775
If any interest my smb.conf is now:
[global]
log level = 3
unix charset = UTF8
dos charset = ISO-8859-1
workgroup = ACME.DOM
realm = ACME.COM...
2019 Feb 22
0
lookup_name_smbconf for <user> failed
...the old system all servers uses the same smb.conf and then all the
> uniq shares are defined in smb.conf.<hostname>
>
> The content can then be seen with this command
>
> # grep -v "#" smb.conf.$(hostname -s)
> [global]
> server string = Samba %v paa %L(%h): udvhome
> [homes]
> comment = Home Directories
> browseable = no
> writable = yes
> read only = no
> create mask = 0775
>
> If any interest my smb.conf is now:
>
> [global]
> log level = 3
> unix charset = UTF8
> dos charset =...
2019 Feb 22
2
lookup_name_smbconf for <user> failed
Hi
I have a Red Hat 7.6 server with samba-4.8.3 which report
lookup_name_smbconf failed when running "smbclient -L" from another console
on the same server. smbclient works fine on an old server running Suse and
samba version 3 and thew the
user.
Any ideas of where to look or what to try?
I got this in the logfile:
# grep "^ " /var/log/samba/log.172.23.10.25
init_oplocks: