NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
IanSav
Nov 30, 2010Apprentice
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
- biggerbyte1AspirantYes, I took it upon myself to uncheck that last night. I thought that was probably the issue. Strange that I've never bothered with that setting either way in the past.
Thank you very much for trying to help me out. You confirmed my theory, so now the issue should be gone. Once 4.1.8 comes out, and these 4.1.7 issues are resolved, I shall turn this feature back on. It could be rather handy with the right conditions.. No? :)
Take Care..
BB - WSJTutor
biggerbyte wrote: Once 4.1.8 comes out ...
Well, that seems to be fairly unlikely ... - at least with regards to new features. :shock:
But definetly, Netgear will have to provide fixes for the bugs which seem to be introduced with 4.1.7. So, yes, there should be a 4.1.8 - and hopefully in the near future. :roll: - KrusherAspirantI thought that maybe it was always this way after the recent upgrade because I was getting used to it. After reading more about it here though, yep I have the same thing as everyone else regarding the initial network file share. (On both XP and Win 7 computers.)
The good news is that I toggled CIFS off/on and so far, it's working instantaneously again when I open up a share. Hopefully it stays that way; I don't reboot my NV+ unless I have to for some reason.
Thanks for the tips. - arsenicrunAspirantThis Netgear forum is initially deceptive so don't get your hopes up. Despite the efforts of the community to document, test and resolve the issue, the last message from anyone associated with Netgear about this was December 12 that basically said "I can't reproduce the problem; seems like your config files might be corrupt." Honestly, this forum just being here is crushing my expectations as a consumer.
I have been living off of the 4.1.6 firmware to cope. - hnoAspirantHas it been confirmed this issue is not seen when the ReadyNAS is configured with a static IP?
If the issue is only seen when the ReadyNAS gets it's IP via DHCP then it's probably a timing issue at startup, either related to IP assignment as such or DNS Server information (/etc/resolv.conf). I am guessing the latter. - IanSavApprenticeHi WSJ,
Has there been any contact, progress or resolution from your Netgear support ticket?
Regards,
Ian. - WSJTutor
IanSav wrote: Has there been any contact, progress or resolution from your Netgear support ticket?
Not in the last 4 weeks - I've updated my inquiry asking for a status update. - chirpaLuminaryI've asked an L3 agent to check out your case history, #14577085
- IanSavApprenticeHi Chirpa,
Thank you for following up on this issue. The many of us who are affected by this problem very much appreciate the update.
Regards,
Ian. - WSJTutor
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:
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!