fireplex Posted May 25, 2017 Share Posted May 25, 2017 So I upgraded from 6.3.3 to 6.3.4 a couple of days ago. I now notice I cannot access my shares from any of my Windows 10 PCs. Tower does not appear under "Network" on Windows like it used to and trying to browse "\\tower" fails with "Windows cannot access \\tower" If I use the IP address of my unRAID server 192.168.1.25 it works OK... unRAID is the master browser according to the Dynamix Local Master plugin. Tried rebooting PCs and unRAID but no change. Any ideas ? Link to comment
Frank1940 Posted May 25, 2017 Share Posted May 25, 2017 You may have two Local Master Browsers on your network. A couple of thoughts. Make sure that all of your computers have the workgroup name spelled in ALL capital letters. (That is the way that Windows treats the name anyway. But Linux would treat Home and home as two different items! I am not sure how Samba running on a Linux OS resolves this issue. I know for a fact that it does NOT handle Share names with this issue in a graceful manner.) Second, figure out which computer your WIn10 computers thinks it is the Local Master. Here is an article which will tell you how to do that and a link to a program that he developed to automate this process. https://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/ (I have used this program and I can tell you that it works with Win7 computers but I always hesitate to tell someone to blindly download something from the Internet.) I assume that you have rebooted all of the Win10 computers as this will sometimes resolve this kind of issue. I have recommended in the past that you powerdown all computers and other devices that access your server on the network expect your server. Go make a cup of coffee. Then go around and turn back on everything you powered down at about thirty second intervals. Sit down. Relax and drink that cup of coffee. Now see what the you find. (The Local Master is determined by an election process and, because, Samba/SMB was developed back in the days of the 386 processor, it runs on a very relaxed time schedule--- think minutes for polling intervals.) Link to comment
fireplex Posted May 25, 2017 Author Share Posted May 25, 2017 Actually, using the IP address presents a login box for username & password, I enter the correct one and it just comes back and asks again... Link to comment
fireplex Posted May 25, 2017 Author Share Posted May 25, 2017 Hi, yes I googled and https://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/ was the first thing I have tried. net view just reports my own PC and nothing else and C:\WINDOWS\system32>nbtstat -a FIREPLEX VirtualBox Host-Only Network #2: Node IpAddress: [192.168.56.1] Scope Id: [] Host not found. Ethernet 2: Node IpAddress: [0.0.0.0] Scope Id: [] Host not found. Ethernet: Node IpAddress: [192.168.1.31] Scope Id: [] Host not found. 192.168.1.31 is my PC The thing is, everything was fine for years before I upgraded unRAID to this latest release Link to comment
fireplex Posted May 25, 2017 Author Share Posted May 25, 2017 C:\WINDOWS\system32>nbtstat -c VirtualBox Host-Only Network #2: Node IpAddress: [192.168.56.1] Scope Id: [] No names in cache Ethernet 2: Node IpAddress: [0.0.0.0] Scope Id: [] No names in cache Ethernet: Node IpAddress: [192.168.1.31] Scope Id: [] NetBIOS Remote Cache Name Table Name Type Host Address Life [sec] ------------------------------------------------------------ TOWER <00> UNIQUE 192.168.1.25 365 Strange, it seems to know about it.... Link to comment
fireplex Posted May 25, 2017 Author Share Posted May 25, 2017 Definitely an unRAID issue, I have a backup script on a Raspberry Pi that now fails: pi@raspberrypi:~/scripts $ sudo mount -t cifs -o username=raspberry,password=password //192.168.1.25/PiBackup /mnt/backups mount error(11): Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) How can I debug samba/cifs on unRAID, any logs anywhere ? Link to comment
fireplex Posted May 25, 2017 Author Share Posted May 25, 2017 So, I turned on samba debugging and find: [2017/05/25 19:53:53.106382, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: authentication for user [raspberry] -> [raspberry] -> [raspberry] succeeded [2017/05/25 19:53:53.119154, 0] ../lib/util/fault.c:78(fault_report) =============================================================== [2017/05/25 19:53:53.119177, 0] ../lib/util/fault.c:79(fault_report) INTERNAL ERROR: Signal 11 in pid 25811 (4.5.7) Please read the Trouble-Shooting section of the Samba HOWTO [2017/05/25 19:53:53.119188, 0] ../lib/util/fault.c:81(fault_report) =============================================================== [2017/05/25 19:53:53.119195, 0] ../source3/lib/util.c:791(smb_panic_s3) PANIC (pid 25811): internal error [2017/05/25 19:53:53.120239, 0] ../source3/lib/util.c:902(log_stack_trace) BACKTRACE: 31 stack frames: #0 /usr/lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x2b9beedfdbaa] #1 /usr/lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x2b9beedfdc80] #2 /usr/lib64/libsamba-util.so.0(smb_panic+0x2f) [0x2b9bec4c2baf] #3 /usr/lib64/libsamba-util.so.0(+0x1bdb6) [0x2b9bec4c2db6] #4 /lib64/libpthread.so.0(+0x115b0) [0x2b9bec29a5b0] #5 /usr/lib64/libsamba-util.so.0(all_zero+0x24) [0x2b9bec4c1e14] #6 /usr/lib64/libsamba-util.so.0(smb_xmemdup+0x14) [0x2b9bec4c1d44] #7 /usr/lib64/libsmbd-base-samba4.so(+0xfff58) [0x2b9bec81bf58] #8 /usr/lib64/libsmbd-base-samba4.so(+0xebfee) [0x2b9bec807fee] #9 /usr/lib64/libsmbd-base-samba4.so(+0x11805f) [0x2b9bec83405f] #10 /usr/lib64/libsmbd-base-samba4.so(+0x118bf1) [0x2b9bec834bf1] #11 /usr/lib64/libsmbd-base-samba4.so(make_connection+0x220) [0x2b9bec8350f0] #12 /usr/lib64/libsmbd-base-samba4.so(reply_tcon_and_X+0x684) [0x2b9bec7e2594] #13 /usr/lib64/libsmbd-base-samba4.so(+0x11233a) [0x2b9bec82e33a] #14 /usr/lib64/libsmbd-base-samba4.so(+0x114183) [0x2b9bec830183] #15 /usr/lib64/libsmbd-base-samba4.so(+0x1157cc) [0x2b9bec8317cc] #16 /usr/lib64/libtevent.so.0(+0x98b3) [0x2b9bed4818b3] #17 /usr/lib64/libtevent.so.0(+0x7df7) [0x2b9bed47fdf7] #18 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) [0x2b9bed47c01d] #19 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x2b9bed47c1bb] #20 /usr/lib64/libtevent.so.0(+0x7d97) [0x2b9bed47fd97] #21 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x6c9) [0x2b9bec832ae9] #22 /usr/sbin/smbd(+0xcf84) [0x5649d7f89f84] #23 /usr/lib64/libtevent.so.0(+0x98b3) [0x2b9bed4818b3] #24 /usr/lib64/libtevent.so.0(+0x7df7) [0x2b9bed47fdf7] #25 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) [0x2b9bed47c01d] #26 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x2b9bed47c1bb] #27 /usr/lib64/libtevent.so.0(+0x7d97) [0x2b9bed47fd97] #28 /usr/sbin/smbd(main+0x1755) [0x5649d7f84cf5] #29 /lib64/libc.so.6(__libc_start_main+0xf0) [0x2b9bf01e3350] #30 /usr/sbin/smbd(_start+0x2a) [0x5649d7f84eaa] [2017/05/25 19:53:53.120340, 0] ../source3/lib/dumpcore.c:303(dump_core) dumping core in /var/log/samba/cores/smbd [2017/05/25 19:53:53.121556, 1] ../source3/smbd/server.c:868(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2017/05/25 19:54:01.197073, 1] ../source3/smbd/server.c:1438(smbd_parent_sig_hup_handler) parent: Reloading services after SIGHUP [2017/05/25 19:54:01.197462, 1] ../lib/param/loadparm.c:1729(lpcfg_do_global_parameter) WARNING: The "null passwords" option is deprecated Link to comment
fireplex Posted May 26, 2017 Author Share Posted May 26, 2017 Downgrading to 6.3.3 resolves the issue Link to comment
fireplex Posted May 28, 2017 Author Share Posted May 28, 2017 6.3.5 resolves the issue Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.