NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SMB not working for some users after upgrade 6.4.0. upgrade
Hi Netgear, I upgraded the firmware of my Readynas 314 to version 6.4.0. Everything worked after the upgrade, except SMB for some of our users (for example Wim) that where in the specified group,...
Quick Revision,
Seems that I did not explore the issue on my Win 7 laptop closely enough. The issue is also effecting this machine, not just my Win 10 desktop.
Hello TobyE,
Can you try disabling then re-enabling the SMB please?
You might also want to try loading 6.4.2-T59 (Beta 1).
Regards,
JennC
I tried disabling and re-enabling SMB in the settings menu and the browsing results are the same. I downloaded and installed 6.4.2 T59 and rebooted. The server started normally but is still displaying the same symptoms. Examined the smbd.log and the last error thrown by SMB was last night at about 10p as shown below:
[2015/12/30 21:54:12.024665, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 15878 (4.2.4)
Please read the Trouble-Shooting section of the Samba HOWTO
[2015/12/30 21:54:12.024716, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2015/12/30 21:54:12.024761, 0] ../source3/lib/util.c:788(smb_panic_s3)
PANIC (pid 15878): internal error
[2015/12/30 21:54:12.026584, 0] ../source3/lib/util.c:899(log_stack_trace)I really don't know what this means, but I tend to think it's not good. Do you have any other suggestions?
Thanks!
Can you send in your logs (see the Sending Logs link in my sig)?
mdgm,
Thank you for offering to look at my logs. I have sent them in per your instructions.
In the mean time, I was discussing this issue on another thread:
Another user said that they had some degree of success solving his problem by trying to disable antivirus.
I turned off the antivirus program and guess what. Everything is working perfectly! I will monitor over the next day or two, but I think this issue may be solved.
I'll tell you one thing for certain, after all of the time I have wasted over the last year or two getting antivirus to work, I will NEVER use it again.
I will update this thread over the next day or two to make sure that this solution continues to work.
I appreciate your assistance, and would still be curious to know if the logs bear out the fact that antivirus was the problem.
Thanks again
Toby
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
