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 ...
Good news, everyone! (at least I hope)
I first attempted to do an OS reinstall by (a) powering off the device and (b) pressing the reset button with a paper clip for at least 5 seconds. I saw no LED lights at around 10 seconds, so I became worried and released the reset button. So that didn't work. I am definitely not willing to do a factory default reset at this time. I still have moderate faith in tech teams in general to resolve these bugs in future patches.
As I said before, I've got three ReadyNAS Duo's configured extremely similarly (apart from unique identifiers like device names), and I've upgraded two of them to 4.1.7, at which time both of the devices with the upgraded firmware always, always required at least 15 seconds, but usually 30+ seconds for SMB network discovery and enumeration completion.
What (seems to have) worked for me, just now:
In the HTTPS web configuration -
- Services, Discovery Services > I unchecked upnp, hit apply
- Services, Standard File Protocols > I unchecked HTTP and unchecked CIFS, hit apply
- (same) I checked CIFS, hit apply.
I booted several other computers on the network, some Windows XP SP3 and some Windows 7, and browsed to the device that I was tampering with. I pulled up an instant network share over CIFS from one machine and pulled up an instant mapped network drive on another computer (which is, in theory, the same mechanic at work). I tested browsing to the other ReadyNAS device that also was upgraded, but untampered, and it required the normal 30 seconds to find. As this was a good sign, I then toggled the CIFS service on the second device and tested it with a Windows 7 laptop that had not been connected for a few days, and alas, both shares came up instantly. Looks promising.
EDIT:
The bad news - I went ahead and tested the durability of this fix surviving a reboot, and my tests have said that no, it certainly does not. :(
The good news -Toggling CIFS after the reboot resolved it again temporarily, though.
tl;dr - toggle the CIFS service on the ReadyNAS and they suddenly become instantly discovered.
I first attempted to do an OS reinstall by (a) powering off the device and (b) pressing the reset button with a paper clip for at least 5 seconds. I saw no LED lights at around 10 seconds, so I became worried and released the reset button. So that didn't work. I am definitely not willing to do a factory default reset at this time. I still have moderate faith in tech teams in general to resolve these bugs in future patches.
As I said before, I've got three ReadyNAS Duo's configured extremely similarly (apart from unique identifiers like device names), and I've upgraded two of them to 4.1.7, at which time both of the devices with the upgraded firmware always, always required at least 15 seconds, but usually 30+ seconds for SMB network discovery and enumeration completion.
What (seems to have) worked for me, just now:
In the HTTPS web configuration -
- Services, Discovery Services > I unchecked upnp, hit apply
- Services, Standard File Protocols > I unchecked HTTP and unchecked CIFS, hit apply
- (same) I checked CIFS, hit apply.
I booted several other computers on the network, some Windows XP SP3 and some Windows 7, and browsed to the device that I was tampering with. I pulled up an instant network share over CIFS from one machine and pulled up an instant mapped network drive on another computer (which is, in theory, the same mechanic at work). I tested browsing to the other ReadyNAS device that also was upgraded, but untampered, and it required the normal 30 seconds to find. As this was a good sign, I then toggled the CIFS service on the second device and tested it with a Windows 7 laptop that had not been connected for a few days, and alas, both shares came up instantly. Looks promising.
EDIT:
The bad news - I went ahead and tested the durability of this fix surviving a reboot, and my tests have said that no, it certainly does not. :(
The good news -Toggling CIFS after the reboot resolved it again temporarily, though.
tl;dr - toggle the CIFS service on the ReadyNAS and they suddenly become instantly discovered.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
