Hannnes Posted May 19 Share Posted May 19 A few weeks ago I started having issues with connecting to my SMB shares. I first noticed the issue on VLC on my Android phone, and thought that the issue was on the client side. But then I noticed that I couldn't connect from either Linux or Windows on my PC. On Windows diagnostics tells me that the SMB port is not open, something that nmap and netstat confirms (Output attached below). As far as I understand port 445 is the port that SMB uses, but it's not present in any of the outputs. I can access the same share using NFS without issues. I have tried rebooting the server several times, and i have run chkdsk on the boot USB and that did not report any issues. How should I proceed with the troubleshooting? The diagnostics output is attached as well. Thank you! nmap output: ❯ nmap 10.150.0.4 Starting Nmap 7.95 ( https://nmap.org ) at 2024-05-19 14:45 CEST Nmap scan report for nginx.hultergard.com (10.150.0.4) Host is up (0.00015s latency). Not shown: 989 closed tcp ports (conn-refused) PORT STATE SERVICE 22/tcp open ssh 80/tcp open http 81/tcp open hosts2-ns 111/tcp open rpcbind 443/tcp open https 2049/tcp open nfs 3000/tcp open ppp 3001/tcp open nessus 5432/tcp open postgresql 5900/tcp open vnc 8080/tcp open http-proxy Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds Netstat output: root@Tower:~# sudo netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:6767 0.0.0.0:* LISTEN 1987/docker-proxy tcp 0 0 0.0.0.0:7878 0.0.0.0:* LISTEN 12522/docker-proxy tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 9225/dnsmasq tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 9420/docker-proxy tcp 0 0 0.0.0.0:8096 0.0.0.0:* LISTEN 11398/docker-proxy tcp 0 0 0.0.0.0:8118 0.0.0.0:* LISTEN 7583/docker-proxy tcp 0 0 0.0.0.0:8112 0.0.0.0:* LISTEN 7604/docker-proxy tcp 0 0 0.0.0.0:5055 0.0.0.0:* LISTEN 10015/docker-proxy tcp 0 0 0.0.0.0:5700 0.0.0.0:* LISTEN 9388/qemu-system-x8 tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 9388/qemu-system-x8 tcp 0 0 0.0.0.0:55081 0.0.0.0:* LISTEN 3418/rpc.statd tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 4566/wsdd2 tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 4566/wsdd2 tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN 6080/docker-proxy tcp 0 0 0.0.0.0:43917 0.0.0.0:* LISTEN 3437/rpc.mountd tcp 0 0 0.0.0.0:43921 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:3001 0.0.0.0:* LISTEN 10392/docker-proxy tcp 0 0 10.150.0.4:1180 0.0.0.0:* LISTEN 3619/nginx: master tcp 0 0 127.0.0.1:11443 0.0.0.0:* LISTEN 3619/nginx: master tcp 0 0 10.253.0.1:2049 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 4566/wsdd2 tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 4566/wsdd2 tcp 0 0 10.150.0.4:22 0.0.0.0:* LISTEN 3214/sshd: /usr/sbi tcp 0 0 127.0.0.1:2049 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:44399 0.0.0.0:* LISTEN 3437/rpc.mountd tcp 0 0 0.0.0.0:8920 0.0.0.0:* LISTEN 11375/docker-proxy tcp 0 0 0.0.0.0:8989 0.0.0.0:* LISTEN 13927/docker-proxy tcp 0 0 127.0.0.1:1180 0.0.0.0:* LISTEN 3619/nginx: master tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 5100/nginx: master tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 5100/nginx: master tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 3414/rpcbind tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 5100/nginx: master tcp 0 0 10.253.0.1:22 0.0.0.0:* LISTEN 3214/sshd: /usr/sbi tcp 0 0 0.0.0.0:34349 0.0.0.0:* LISTEN 3437/rpc.mountd tcp 0 0 0.0.0.0:58946 0.0.0.0:* LISTEN 7517/docker-proxy tcp 0 0 10.150.0.4:2049 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:16509 0.0.0.0:* LISTEN 9092/libvirtd tcp 0 0 10.253.0.1:1180 0.0.0.0:* LISTEN 3619/nginx: master tcp 0 0 0.0.0.0:58846 0.0.0.0:* LISTEN 7560/docker-proxy tcp 0 0 0.0.0.0:9696 0.0.0.0:* LISTEN 15087/docker-proxy tcp6 0 0 :::6767 :::* LISTEN 1992/docker-proxy tcp6 0 0 :::7878 :::* LISTEN 12529/docker-proxy tcp6 0 0 :::8080 :::* LISTEN 9429/docker-proxy tcp6 0 0 :::8096 :::* LISTEN 11405/docker-proxy tcp6 0 0 :::8118 :::* LISTEN 7590/docker-proxy tcp6 0 0 :::8112 :::* LISTEN 7611/docker-proxy tcp6 0 0 :::5055 :::* LISTEN 10022/docker-proxy tcp6 0 0 :::38511 :::* LISTEN - tcp6 0 0 :::5432 :::* LISTEN 6088/docker-proxy tcp6 0 0 :::35535 :::* LISTEN 3437/rpc.mountd tcp6 0 0 :::3001 :::* LISTEN 10398/docker-proxy tcp6 0 0 :::3000 :::* LISTEN 5106/node tcp6 0 0 :::36855 :::* LISTEN 3437/rpc.mountd tcp6 0 0 :::44509 :::* LISTEN 3437/rpc.mountd tcp6 0 0 :::8920 :::* LISTEN 11384/docker-proxy tcp6 0 0 :::8989 :::* LISTEN 13934/docker-proxy tcp6 0 0 :::81 :::* LISTEN 5100/nginx: master tcp6 0 0 :::80 :::* LISTEN 5100/nginx: master tcp6 0 0 :::111 :::* LISTEN 3414/rpcbind tcp6 0 0 :::443 :::* LISTEN 5100/nginx: master tcp6 0 0 :::58946 :::* LISTEN 7523/docker-proxy tcp6 0 0 :::34005 :::* LISTEN 3418/rpc.statd tcp6 0 0 :::58846 :::* LISTEN 7568/docker-proxy tcp6 0 0 :::9696 :::* LISTEN 15094/docker-proxy udp 0 0 192.168.122.1:53 0.0.0.0:* 9225/dnsmasq udp 0 0 0.0.0.0:67 0.0.0.0:* 9225/dnsmasq udp 0 0 10.150.0.4:68 0.0.0.0:* 1164/dhcpcd: [netwo udp 0 0 10.150.0.4:111 0.0.0.0:* 3414/rpcbind udp 0 0 10.253.0.1:111 0.0.0.0:* 3414/rpcbind udp 0 0 127.0.0.1:111 0.0.0.0:* 3414/rpcbind udp 0 0 10.150.0.4:123 0.0.0.0:* 1276/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 1276/ntpd udp 0 0 10.253.0.1:33236 0.0.0.0:* 3735/unraid-api udp 0 0 127.0.0.1:659 0.0.0.0:* 3418/rpc.statd udp 0 0 0.0.0.0:58946 0.0.0.0:* 7540/docker-proxy udp 0 0 0.0.0.0:59083 0.0.0.0:* 3437/rpc.mountd udp 0 0 127.0.0.1:2049 0.0.0.0:* - udp 0 0 10.253.0.1:2049 0.0.0.0:* - udp 0 0 10.150.0.4:2049 0.0.0.0:* - udp 0 0 0.0.0.0:51566 0.0.0.0:* 4611/avahi-daemon: udp 0 0 10.150.0.4:43540 0.0.0.0:* 3735/unraid-api udp 0 0 0.0.0.0:51820 0.0.0.0:* - udp 0 0 0.0.0.0:60835 0.0.0.0:* 3418/rpc.statd udp 0 0 0.0.0.0:3702 0.0.0.0:* 4566/wsdd2 udp 0 0 0.0.0.0:3702 0.0.0.0:* 4566/wsdd2 udp 0 0 0.0.0.0:5353 0.0.0.0:* 4611/avahi-daemon: udp 0 0 0.0.0.0:5355 0.0.0.0:* 4566/wsdd2 udp 0 0 0.0.0.0:5355 0.0.0.0:* 4566/wsdd2 udp 0 0 0.0.0.0:38891 0.0.0.0:* - udp 0 0 0.0.0.0:55704 0.0.0.0:* 3437/rpc.mountd udp 0 0 0.0.0.0:55786 0.0.0.0:* 3414/rpcbind udp 0 0 0.0.0.0:39619 0.0.0.0:* 3437/rpc.mountd udp6 0 0 :::57411 :::* 3414/rpcbind udp6 0 0 :::57421 :::* - udp6 0 0 ::1:111 :::* 3414/rpcbind udp6 0 0 :::50009 :::* 3437/rpc.mountd udp6 0 0 :::58946 :::* 7547/docker-proxy udp6 0 0 :::51820 :::* - udp6 0 0 :::45189 :::* 3437/rpc.mountd udp6 0 0 :::38426 :::* 3418/rpc.statd udp6 0 0 :::39577 :::* 3437/rpc.mountd tower-diagnostics-20240519-1441.zip Quote Link to comment
Frank1940 Posted May 19 Share Posted May 19 Only the Share, 'h------s' is being Exported using the SMB protocol. The other two shares are not being exported via SMB! Today, Windows in its default state will not allow access to a server using 'Guest' credentials. (You must have a login. There are ways around this but there is no guarantee that MS might close those hacks as a part of its monthly security updates.) Quote Link to comment
Hannnes Posted May 19 Author Share Posted May 19 17 minutes ago, Frank1940 said: Only the Share, 'h------s' is being Exported using the SMB protocol. The other two shares are not being exported via SMB! Today, Windows in its default state will not allow access to a server using 'Guest' credentials. (You must have a login. There are ways around this but there is no guarantee that MS might close those hacks as a part of its monthly security updates.) I'm unable to access home-nas ('h------s' in the diagnostics), even if it is exported. Doubt this is a Windows issue, since the problem appeared on several different clients with different operating systems at the same time. Quote Link to comment
Frank1940 Posted May 19 Share Posted May 19 Found this in your syslog file: May 19 05:39:42 Tower smbd[4555]: smbd version 4.17.12 started. May 19 05:39:42 Tower smbd[4555]: Copyright Andrew Tridgell and the Samba Team 1992-2022 May 19 05:39:42 Tower smbd[4555]: [2024/05/19 05:39:42.381191, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) May 19 05:39:42 Tower smbd[4555]: tdb(/var/lib/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 16384 May 19 05:39:42 Tower smbd[4555]: [2024/05/19 05:39:42.381211, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) May 19 05:39:42 Tower smbd[4555]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record May 19 05:39:42 Tower smbd[4555]: [2024/05/19 05:39:42.381237, 0] ../../source3/passdb/secrets.c:67(secrets_init_path) May 19 05:39:42 Tower smbd[4555]: Failed to open /var/lib/samba/private/secrets.tdb May 19 05:39:42 Tower smbd[4556]: [2024/05/19 05:39:42.382694, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) May 19 05:39:42 Tower smbd[4556]: tdb(/var/lib/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 16384 May 19 05:39:42 Tower smbd[4556]: [2024/05/19 05:39:42.382753, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) May 19 05:39:42 Tower smbd[4556]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record May 19 05:39:42 Tower smbd[4556]: [2024/05/19 05:39:42.382786, 0] ../../source3/passdb/secrets.c:67(secrets_init_path) May 19 05:39:42 Tower smbd[4556]: Failed to open /var/lib/samba/private/secrets.tdb May 19 05:39:42 Tower smbd[4556]: [2024/05/19 05:39:42.382834, 0] ../../lib/util/become_daemon.c:119(exit_daemon) May 19 05:39:42 Tower smbd[4556]: exit_daemon: daemon failed to start: smbd can not open secrets.tdb, error code 13 May 19 05:39:42 Tower root: /usr/sbin/wsdd2 -d -4 May 19 05:39:42 Tower root: /usr/sbin/winbindd -D This has been found in the past and it seems that it is usually the result of corruption on the boot flash drive. See here: https://forums.unraid.net/topic/149487-how-do-i-fix-these-samba-errors/ and https://forums.unraid.net/topic/163438-smb-acces-not-work-windows-11/#comment-1411185 Make sure that both the smbpasswd and the secrets.tdb files exist in the /config folder/directory on the flash drive. (Neither of these threads are very definitive but once the OP started looking at the boot drive, the problem appears to have been resolved.) Quote Link to comment
Solution JorgeB Posted May 20 Solution Share Posted May 20 There was a user having a similar issue that fixed it by removing the following files from the flash drive config folder: "passwd", "secrets.tdb", "shadow", "smbpasswd", you can move them somewhere else instead of deleting them just in case, after that please reboot the server and retest, also note that you will need to recreate the users if you have some, but you should only need to set the name and password, the permissions on the shares should be retained in the shares config files. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.