# This might need tweaking when using external authentication schemes # Un-comment the following parameter to make sure that only "username" # By default, \\server\username shares can be connected to by anyone with group=rw permissions, set next parameter to 0775. # Directory creation mask is set to 0700 for security reasons. # create files with group=rw permissions, set next parameter to 0775. # File creation mask is set to 0700 for security reasons. # next parameter to 'no' if you want to be able to write to them. # By default, the home directories are exported read-only. # user's home directory as \\server\username # to enable the default home directory shares. # Un-comment the following (and tweak the other settings below to suit) Smb.conf Share Definitions: #= Share Definitions = # /boot was on /dev/md0 during curtin installation # / was on /dev/md2 during curtin installation # that works even if disks are added and removed. # device this may be used with UUID= as a more robust way to name devices # Use 'blkid' to print the universally unique identifier for a Per the suggestion of in the comments, the output of cat /etc/netplan/*.yaml: # This is the network config written by 'subiquity'įstab contents: # /etc/fstab: static file system information. Incidentally, Samba appears to be running and Webmin reports that the folder share is active. At the moment, I really don't know where to go poking next to figure out what's causing this delay (or why the file server isn't visible to Win10 clients).
I've also noticed several of the "NXDOMAIN / potential DVE2018-0001 violation" errors interspersed in /var/log/syslog. I suspect it's maybe a DHCP or DNS-related issue. It takes about two minutes for the last message to clear. A start job is running for Wait for Network to be Configured (XX / no limit) Reached target Host and Network Name Lookups. Starting Wait for Network to be Configured. The boot time messages: Reached target Network (Pre). Recently, our network got reconfigured and afterward, I encountered a very long boot time due to network configuration issues and, after booting, no longer able to access the samba file share from a Win10 client.
I've been trying to sort out two problems that I suspect are interrelated.
0 kommentar(er)
