NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
4.1.7 Slow To Respond To SMB Network Discovery...
Hi,
Since upgrading my DUO to 4.1.7 I have noticed that the DUO is *very* slow to respond SMB/SAMBA network share enumeration requests. It may take up to about a minute for the DUO to provide its list of shares. The problem happens *every* time the DUO is asked to list its shares and not just for the first request. This was not an issue under 4.1.6. (I never ran any of the betas and upgraded from 4.1.6 production directly to 4.1.7 production. There were no obvious issues with the upgrade.)
On a client PC this results in about a minute of waiting before the DUO responds with a share list. This is long but not particularly problematic. On the other hand, to my media players this response is *so* long that the media player times out and is no longer able to find the DUO. This is *very* problematic.
This is only happening on my DUO with 4.1.7. The same DUO with 4.1.6 was fine and my NVX with 4.2.15 is also fine.
Is it possible to get a patch to repair this issue? Is there anything I can do to restore the previously snappy performance? Is it safe/possible to revert to 4.1.6?
Regards,
Ian.
Since upgrading my DUO to 4.1.7 I have noticed that the DUO is *very* slow to respond SMB/SAMBA network share enumeration requests. It may take up to about a minute for the DUO to provide its list of shares. The problem happens *every* time the DUO is asked to list its shares and not just for the first request. This was not an issue under 4.1.6. (I never ran any of the betas and upgraded from 4.1.6 production directly to 4.1.7 production. There were no obvious issues with the upgrade.)
On a client PC this results in about a minute of waiting before the DUO responds with a share list. This is long but not particularly problematic. On the other hand, to my media players this response is *so* long that the media player times out and is no longer able to find the DUO. This is *very* problematic.
This is only happening on my DUO with 4.1.7. The same DUO with 4.1.6 was fine and my NVX with 4.2.15 is also fine.
Is it possible to get a patch to repair this issue? Is there anything I can do to restore the previously snappy performance? Is it safe/possible to revert to 4.1.6?
Regards,
Ian.
179 Replies
Replies have been turned off for this discussion
- Add another person to the slow access issue.
I wasn't sure if it was 4.1.7 or the fact that i added a new Seagate drive to the Duo, but it seems with everyone else experiencing this issue it must be 4.1.7. WSJ wrote: chirpa wrote: I've asked an L3 agent to check out your case history, #14577085
Thanks chirpa for stepping in, finally.
But all that did happen is that my case got closed - without providing any solution.
I did not see any L3 taking over.
Oh, I've also been asked to participate in "The NETGEAR Customer Support Survey" - this I will do. :evil:
Looks like the case got closed out by the auto-closer. I'll see if I can replicate this tomorrow when I get in, I went ahead and assigned the case to my queue.- Hi Siigna,
Do you have any updates on this issue?
Regards,
Ian. - For some reason, same as Jedi Knight, I can't reproduce this issue with my setup. Duo w/ 4.1.7 and my Win7 client, only thing I've got in between here is a little GS105. Browsing to CIFS shares is pretty much instantaneous, I'm not seeing any wait time here. I'll load up one of the shares with data here, give it a reboot and see what happens.
- Hi Siigna,
Is there anything any of us who do have the problem can do to assist you track the issue down?
The problem is a solid failure here *every* time my DUO restarts. The workaround is to bounce the SMB service and then all is fine until the next restart.
Regards,
Ian. - Actually if anyone here that can replicate the issue has root access that'd be great. If you can increase the logging for samba and try connecting to the share, then send me the resulting logs that might be helpful here.
You can either increase the log level in /etc/samba/smb.conf (log level = 0 auth:2 should be the line), or send the smbd process a kill -SIGUSR1 to increase verbosity by one level (SIGUSR2 to decrease a level).
Log level 2 should give me enough information here, so either edit the config and reload samba/restart the NAS or send it the SIGUSR1 signal twice, make the connection and grab the log (/var/log/samba/log.smbd). Make sure to revert the changes afterwards else you run the risk of filling up the OS partition with logging.
Another thing that might be helpful here is a packet capture while trying the connection as well (with Wireshark or something of the sort). - Hi Siigna,
I don't have the access you suggest but is the extra logging something you can trigger remotely? I am in Australia but would be prepared to find a time we can work together to try and track this issue down.
Regards,
Ian. IanSav wrote: Hi Siigna,
I don't have the access you suggest but is the extra logging something you can trigger remotely? I am in Australia but would be prepared to find a time we can work together to try and track this issue down.
Regards,
Ian.
That would work. PM me your contact info and I'll get in touch with you.- I've got the same problem. Here's what I did:
Bought a new ReadyNas Duo with 2Tb Drive installed
It came with 4.1.6 pre-installed so I upgraded to 4.1.7 before adding any data
Added a 2nd, identical 2Tb drive a couple weeks later before adding any data
After the new drive was formatted I set up some custom shares with bespoke users groups, users and permissions
Started adding files to the drive with a Win XP machine (no probs here)
Access times suffer when using XBMC Live via SMB - circa 1min to load a folder with 10 files in it over a cabled 100Mb Lan from a high-spec machine but all is well when I use Win 7 on the same machine.
Cheers
Dan
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
