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 ...
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.
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
