NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WIN 10 Slow Directory enumeration SMB
After upgrading to Win 10, access to my ReadyNas 312 has become problematic. When I browse to a share in explorer, it takes a long time to display the share contents (10-60 seconds). This becomes f...
Update: I turned off the ReadyNAS anti-virus and removed network and file access permissions on the one share I had them on. All started working well. So I then turned back on the network-access permissions (left file-access alone since if you can't access the share over the network then who cares about the file-access... I think). Still everything is going well. So now I guess my next move will be to turn on anti-virus again.
Stephen,
Thanks for the response. I did try this with no joy. I found a solution for this error that had me copy the Winsock and Winsock2 registry entries from a working system and replacing them in the registry. This cleard the error from the troubleshooter, but did not solve my issue.
Some additional information: I explored the chance that it was an authentication issue, and have kinda ruled that out. My windows login is the same as the User and Share name on the NAS (Toby). I also entered the server IP along with Admin user name and password (for the NAS) in the Windows Credentials. I went to the User config on the NAS and changed the password for Toby and it took about 2 minutes, but it fineally resulted in only being able to access the shares on the server via the IP address and it also showed the "Data" share as expected. I then changed the Toby password back to match the windows login and access was restored to the \\Server share.
I then examined the smbd.log from the server and saw the login transactions as expected.
[2015/12/19 14:03:57.990804, 2] ../source3/auth/auth.c:315(auth_check_ntlm_password)
check_ntlm_password: Authentication for user [Toby] -> [Toby] FAILED with error NT_STATUS_WRONG_PASSWORD
[2015/12/19 14:04:30.911822, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Admin] -> [Admin] -> [admin] succeeded
Long story short, I don't think it is an authentication issue. This is driving me nuts. This is not just an annoyance, it almost makes the server unusable. For example, I fire up Windows Media Player and it takes forever to populate my music library, while the access light on the server stays on almost constantly. Opening the Pictures share takes forever to populate the thumbnail images, etc. I can't use the preview pane in Windows explorer (say for images or PDFs) because even after closing the explorer window, the file lockouts prevent me from editing or saving the file I was viewing for about 1-2 minutes.
I really need some help, I think the next step may be some network traces, but I am not sure about the best method to accomplish this. Once again, any help would be appreciated!
Toby
Seems as though I didn't look closely enough at the SMBD.log file. Since October 2, 2015 SAMBA has been crashing regularly. The logs I have cover 10/2/15 through today and 10/17/14 - 7/30/15. There are no errors in the latter but in the 10/2 log they appear every day. They are all like this:
===============================================================
[2015/10/21 03:04:48.780437, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 16306 (4.2.4)
Please read the Trouble-Shooting section of the Samba HOWTO
[2015/10/21 03:04:48.780510, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2015/10/21 03:04:48.780556, 0] ../source3/lib/util.c:788(smb_panic_s3)
PANIC (pid 16306): internal error
[2015/10/21 03:04:48.902839, 0] ../source3/lib/util.c:899(log_stack_trace)
BACKTRACE: 30 stack frames:
#0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) [0x7f8a81c6841a]
#1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x1a) [0x7f8a81c684fa]
#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f8a83a93e5f]
#3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1b081) [0x7f8a83a94081]
#4 /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7f8a83cbb8d0]
#5 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(file_close_user+0x9) [0x7f8a83639b19]
#6 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(smbXsrv_session_logoff+0xdc) [0x7f8a836c4b2c]
#7 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x13dece) [0x7f8a836c4ece]
#8 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x13deee) [0x7f8a836c4eee]
#9 /usr/lib/x86_64-linux-gnu/libtalloc.so.2(+0x9368) [0x7f8a808bb368]
#10 /usr/lib/x86_64-linux-gnu/libtalloc.so.2(+0x8f9b) [0x7f8a808baf9b]
#11 /usr/lib/x86_64-linux-gnu/libtalloc.so.2(_talloc_free+0xeb) [0x7f8a808b470b]
#12 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x1422cd) [0x7f8a836c92cd]
#13 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x14272e) [0x7f8a836c972e]
#14 /usr/lib/x86_64-linux-gnu/samba/libsmbd-shim-samba4.so(exit_server_cleanly+0x12) [0x7f8a81627d82]
#15 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x125d5c) [0x7f8a836acd5c]
#16 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(+0x128a09) [0x7f8a836afa09]
#17 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) [0x7f8a81c7cbe1]
#18 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x37e57) [0x7f8a81c7ce57]
#19 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f8a806a843d]
#20 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f8a806a85db]
#21 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so(smbd_process+0x728) [0x7f8a8369fe08]
#22 /usr/sbin/smbd(+0xb550) [0x56025a45a550]
#23 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) [0x7f8a81c7cbe1]
#24 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x37e57) [0x7f8a81c7ce57]
#25 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f8a806a843d]
#26 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f8a806a85db]
#27 /usr/sbin/smbd(main+0x185f) [0x56025a456f7f]
#28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f8a8031cb45]
#29 /usr/sbin/smbd(+0x8085) [0x56025a457085]
[2015/10/21 03:04:48.903452, 0] ../source3/lib/dumpcore.c:318(dump_core)
dumping core in /var/cores
[2015/10/21 06:26:51.027037, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 14:35:08.179233, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:10:11.768961, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:10:55.608523, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:12:21.948669, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:22:44.084879, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [Toby] -> [Toby] -> [Toby] succeeded
[2015/10/21 16:23:32.149115, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2015/10/21 16:23:32.149201, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 30385 (4.2.4)
Please read the Trouble-Shooting section of the Samba HOWTO
[2015/10/21 16:23:32.149252, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2015/10/21 16:23:32.149297, 0] ../source3/lib/util.c:788(smb_panic_s3)
PANIC (pid 30385): internal error
[2015/10/21 16:23:32.151019, 0] ../source3/lib/util.c:899(log_stack_trace)
BACKTRACE: 30 stack frames:
===============================================================
Seems like different PIDs are involved every time.
Don't know what is making it crash and don't know if it is on the Win10 pc side or the server side. As stated before, a Win7 pc on the same network seems to work just fine.
Hope this helps narrow down where the problem lies.
Thanks
I've been having the same slow problems from Windows 10 and also from a Mac (El Capitan). Sometimes it simply doesn't come back. I've had this problem for months.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
