4.1.7 Slow To Respond To SMB Network Discovery...

If my Duo's CIFS shares have been recently (within 15-30ish minutes, I'd guess) viewed in Windows, the share will pop up instantaneously, but other than that it requires the 30 to 45 seconds of patience each time to show me the contents. So perhaps unplugging and replugging the client computer into the network might help to reproduce the issue?

Regardless, is it possible or safe to downgrade to 4.1.6? I don't want to risk corrupting the firmware.

jeremydo wrote:
Which system logs ? for the client or the server ? I am not able to ssh into my server. I have had a small amount of success enabling afp and using that instead of smb, but it is still glacially slow - 90 seconds to do a directory listing. It almost seems like something else might be running in the background that is taking up a lot of cpu. But I can't tell what.

Go to FrontView->Status Page-> you will see the download all system logs link. Download the zip file and email it to me. Attention Jedi Knight with this post thread.

arsenicrun wrote:

If my Duo's CIFS shares have been recently (within 15-30ish minutes, I'd guess) viewed in Windows, the share will pop up instantaneously, but other than that it requires the 30 to 45 seconds of patience each time to show me the contents. So perhaps unplugging and replugging the client computer into the network might help to reproduce the issue? Regardless, is it possible or safe to downgrade to 4.1.6? I don't want to risk corrupting the firmware.

Could you send in your system logs?

Jeremy:

Thanks for the system log. I am seeing this in your system log as well as Ian' system log.
--
tcp_retransmit: 76098
tcp_retransmit_unrecovered: 1121
--

Is there anyway would any of you guy willing to do the OS reinstall via system reset switch? and also test with direct connect to PC?

I will have one of my guy contact one by one slowly so that we can walk this issue out.

would the os re-install wipe out the main volumes ? I have 2.5T of personal stuff on there.

OS Reinstall will not wipe off the volume. Make sure not to pressing the reset button more than 5 Seconds OR too long. 30seconds will factory default the system.

Hello all,

I've the same problem too.
Data transfer rate is about 500kbytes/s via powerline LAN 85Mbit/s.
WinXP SP3 and Vista SP1

How is the transfer rate from other users systems?

Hi Rusty Srcew,

Rusty srcew wrote:
I've the same problem too. Data transfer rate is about 500kbytes/s via powerline LAN 85Mbit/s. WinXP SP3 and Vista SP1 How is the transfer rate from other users systems?

Once the share list is enumerated I have not noticed and transfer/speed rate issues.

Regards,
Ian.

Guys,

I still am not able to reproduce the issue in house. I tried with Disk Spindown Mode. I tired with Jumbo Frame. If you could try with Frimware reinstall again and test with Direct connect (the ReadyNAS to PC) to rule out any possible switch/router issue. I also would advise rebooting the Clients before doing any test. If you are still having an issue, please open the tech support ticket (post the ticket info here) so that we can contact each of you and try to debug your system.

If anyone have same issue, please open a new post.

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.