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.

Hello,I got exactly the same problem with my Duo after ugrade to 4.1.7greetings Berkhout

I've noticed similar behavior on a couple of NV+ units as well on both Win XP & Win 7 clients. Opening up My Computer for the first time with drives mapped to the NAS can take anywhere from 20-30+ seconds.-Randy

I also have noticed slower response. Please note that I had 60 minute spin down timers set before the upgrade to 4.1.7 and continue to have those timers in place.I have drive letters mapped on my vista box. On 4.1.6 when clicking on a network drive letter it was almost immediate, regardless of the spin down timers. Now on 4.1.7 I can wait up to 20 seconds before the contents of the drive are displayed and available to use. Definately something in the 4.1.7 upgrade that is doing this...

Hi,Can one of the Jedis please let us know if this problem is being investigated and how far the investigation has advanced? It would also be helpful if we can have an indication of how long it will take for this to be fixed.With my DUO holding lots of material for my media players I will need to revert firmware if this isn't fixed quickly. (I would welcome advice of any issues reverting from 4.1.7 production back to 4.1.6 production.)By the way, where can we get the 4.1.6 production version of the firmware? It doesn't appear to be available on the ReadyNAS website.Regards,Ian.

I have the same issue. Performance was fine before the 4.1.7 upgrade and now the enumeration is so slow, I cannot mount any filesystems via cifsfs from a Linux box because it times out. Windows is able to perform the mounts, but the initial enumeration is appallingly slow. I'd rather not have to downgrade to 4.1.6, but this problem may force me to do so :(For the record, with is an NV with 1GB of memory and 4 1.5GB Seagate drives.

4.1.7 Slow To Respond To SMB Network Discovery...

179 Replies

Replies have been turned off for this discussion

WSJ
Tutor
Jun 09, 2011
IanSav wrote:
Not that the ReadyNAS is a particularly "cheap" unit. For the money charged they could make some effort to address this issue.

I totally agree. The amount of effort spent so far (over the period of 6 months) is definetly not appropriate - because it's not just this forum posting but the two of us have also reported an official support case and provided all information requested from us. Now it's the vendors turn to take action. If they'll ask for more information or assistance: fine - we'll do our very best. But currently there's only silence - for quite some while. I've not even obtained any status updates, although I've asked for it, several times (in the official case). And that's not o.k. - even if they would really work hard on the issue, they should find some minutes to provide a status update.
IanSav
Apprentice
Jun 16, 2011
Hi,

Another week passes and we are yet to get the courtesy of *any* feedback or reports on progress investigating or fixing this issue.

If Netgear don't want to address the firmware issues in models that use 4.1.x firmware then how about they swap out our units for their equivalent model running the 4.2.x firmware so that we too can share in all the attention Netgear allocates to the 4.2.x firmware branch. (The lack of support is astounding given that units using the 4.1.x firmware are currently being sold in stores as new with multi year warranties!)

Regards,
Ian.
IanSav
Apprentice
Jun 30, 2011
Hi,

Another couple of weeks and we are now into a new month and still we have *NO* contact from Netgear.

Can one of the Jedi's please show us some respect by giving us an update if not a fix to this frustrating problem.

Regards,
Ian.
WSJ
Tutor
Jul 06, 2011
Well, I start loosing confidence that this issue will ever be resolved. :evil:
I doubt that I'll get a nice birthday present on next Tuesday ... (got the hint?! :wink:)
chirpa
Luminary
Jul 06, 2011
I haven't read through the whole thread, but have you contacted support to get a case number for official help on the issue?
IanSav
Apprentice
Jul 06, 2011
Hi Chirpa,
chirpa wrote:
I haven't read through the whole thread, but have you contacted support to get a case number for official help on the issue?

This has been an outstanding issue from the time that 4.1.7 was released. It has never been addressed.

WSJ has / had an open case number (Case 15187681). Siigna took up the issue and collected logs and information from us on about 6-May-2011 but never came back. There was no follow-up results or information. We have all been in limbo ever since.

Regards,
Ian.
WSJ
Tutor
Jul 08, 2011
chirpa wrote:
I haven't read through the whole thread, but have you contacted support to get a case number for official help on the issue?

Please have a kind look on what you have posted on April 1st(bad omen?):
"I've asked an L3 agent to check out your case history, #14577085"

Unfortunately case #14577085 was closed, so I've opened a new one (#15187681), two days later (April 3rd).

Another 3 days later, "siigna" stepped in - most appreciated by all of us. He asked for logs - we gladly gave him whatever he asked us for. That was in April.

On May 5th "siigna" asked for more logs - we've send it to him.

2 weeks later (May 19th) we started to ask for some feedback - without success.

I hope that you understand our frustration - we have offered and provided our help. But up to now there was no return on our efforts. How would you feel as a customer?!
pudsp1
Aspirant
Jul 09, 2011
I have a readynas duo and have come to the conclusion that it is a piece of crap, spend months to get it working and then before you know it, it's running (or should I say not running) like crap again. I think it's time to try something different.
IanSav
Apprentice
Jul 09, 2011
Hi Pudsp1,

You need to bounce the CIFS service after *every* restart to keep the workaround going.

Regards,
Ian.
pudsp1
Aspirant
Jul 15, 2011
yeah thanks but I think that I'll just use an external hard drive instead, it's a lot less maintenance.

Forum Discussion

4.1.7 Slow To Respond To SMB Network Discovery...

179 Replies

Related Content

Bonjour device discovery issue

GS308E Not Discovered by Switch Discovery Tool

Windows 10 Network discovery broken after 6.5.2 update

network

WC9500 Discovery doesn't work

NETGEAR Academy

ProSupport for Business