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
- arsenicrunAspirantI see. I'm afraid that installing an addon, an ssh client, and diving into ssh access without being familiar with that stuff seems to be outside of my comfort zone. If there's more of a point and click way of finding out your info, I'd probably be more able to help.
As an update, I've downgraded my other 4.1.7 ReadyNAS Duo back to 4.1.6 and I am once again a happy user. My 3 Duo's are all socializing pleasantly and efficiently with all of their network friends. - wiltonwAspirantHi
I got the same problem with other users on this post. I wonder if Netgear will fix this problem sooner or later, or they basically forget the Sparc users with 4.1.7 and just let us use 4.1.6 from now on.
I am a Duo user, I use my Duo for my small business, I bought it on April of 2010, it is still under warranty. Same as most of the Sparc Readynas users, I looked forward to the official 4.1.7 update for a long time. However, after a lot of bugs fixed work. The latest official firmware still has seriously performance problem. Is it acceptable?
I am planning to get another NAS for my partner's office. We are considering to get a 4 bays high performance NAS this time, it will becoming our main central server, but I am hesitating to use Readynas series NAS now. If the Netgear personnel actually read this forum, please could you found out what happen and provide a solution as soon as possible.
Thanks a lot - adam_pAspirantI had the same problem after going from 4.1.6 to 4.1.7.
I have the problem resolved as follows: I switched the Duo from DHCP to a fixed IP and the problem went away. I do not know why. - WSJTutorO.k. let me summarize the issue for the NetGear technical support guys (hopefully they read the forum postings):
ReadyNAS (Duo) is inacceptably slow to respond SMB/SAMBA network share enumeration requests (it takes about 30s and more).
This refers to (single) file share access requests as well as to (status) requests to network printers (exposed by ReadyNAS).
- it effects everyone who is using RAIDiator 4.1.7 (those who purchased a brand-new model with 4.1.7 suffer the same)
- it can be temporarily fixed by toggling the CIFS service off and on (but that fix only lasts until the next reboot)
- downgrading to RAIDiator 4.1.6 resolves the problem (but is not acceptable for most customers)
- performing an OS reinstall does not help
- it effects also customers who have not installed the "Enable Root SSH Access" add-on
- using a fixed IP address seems to resolve the problem (so far only stated by one single customer)
After all those investigations performed by us customers, it's now NetGears turn to perform a proper root cause analysis (using their own equipment). I'm starting to get a bit disappointend of NetGear - actually I did hope that they are a bit more professional. - wiltonwAspirant
adam.p wrote: I had the same problem after going from 4.1.6 to 4.1.7.
I have the problem resolved as follows: I switched the Duo from DHCP to a fixed IP and the problem went away. I do not know why.
Thanks for your tip, but I am afraid that it is not working for my situation. Actually, I am using fixed IP for my Duo since the day one that I got it. I was happy with it until I upgraded to 4.1.7. :( - IanSavApprenticeHi WSJ,
Good summary. :)
Shame that Netgear is dragging its collective feet on this one. They are pushing ahead with betas for the 4.2.x series but even then they seem to move two steps forward then one step back. The 4.1.x series appears to be neglected in comparison. It is a shame that the sense of pride in quality of the firmware did not make the transition from Infrant to Netgear. (In the old days these sorts of reports were usually investigated and resolved within days. Even though the Jedi handles appear the same the response to customer requests and feedback is not. :()
Regards,
Ian. - BikeHelmetAspirantHello there,
Until recently I had a home-built Ubuntu NAS that exhibited the same symptoms. That was actually one of the reasons I was looking at NAS units. It also had the symptom of extremely slow folder creation - then after creating a "New Folder", I had to press F2 and rename it to something else.
I ultimately resolved it by changing the name resolve order in /etc/samba/smb.conf to include bcast.
It's unlikely that we have the same cause for the same symptoms, but it's something to look into. - BerkhoutAspirant
WSJ wrote: O.k. let me summarize the issue for the NetGear technical support guys (hopefully they read the forum postings):
ReadyNAS (Duo) is inacceptably slow to respond SMB/SAMBA network share enumeration requests (it takes about 30s and more).
This refers to (single) file share access requests as well as to (status) requests to network printers (exposed by ReadyNAS).
- it effects everyone who is using RAIDiator 4.1.7 (those who purchased a brand-new model with 4.1.7 suffer the same)
- it can be temporarily fixed by toggling the CIFS service off and on (but that fix only lasts until the next reboot)
- downgrading to RAIDiator 4.1.6 resolves the problem (but is not acceptable for most customers)
- performing an OS reinstall does not help
- it effects also customers who have not installed the "Enable Root SSH Access" add-on
- using a fixed IP address seems to resolve the problem (so far only stated by one single customer)
After all those investigations performed by us customers, it's now NetGears turn to perform a proper root cause analysis (using their own equipment). I'm starting to get a bit disappointend of NetGear - actually I did hope that they are a bit more professional.
I totally agree with WSJ.
greetings Berkhout - WSJTutor
BikeHelmet wrote:
I ultimately resolved it by changing the name resolve order in /etc/samba/smb.conf to include bcast.
It's unlikely that we have the same cause for the same symptoms, but it's something to look into.
Well - my ReadyNAS Duo (with 4.1.7 firmware) hasname resolve order = "lmhosts host wins bcast"
So, that seems not the cause.
PS: "smbd --version" returns "3.0.37" (with RAIDiator 4.1.7) - WSJTutorhttp://samba.org/samba/history/samba-3.2.2.html:
"Fix freezing Windows Explorer on WinXP while browsing Samba shares.
This one led to timeouts during printing as well." (BUG #5617)
Well, that could be related (although it's not exactly the same issue).
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!