- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Slow network after ReadyNAS firmware updates
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ReadyNAS 316 Firmware version: 6.6.0 (latest)
Netgear Nighthawk router (R7000), firmware version: 1.0.7.2_1.1.93 (latest)
Windows 10 (two different PCs)
MAC OS X 10.11.6
Access to mapped drives on the NAS is crushingly slow. Click on folders and I get the Windows blue 'waiting for' circle for many seconds, sometimes minutes, sometimes never connecting. When logging on, the drives map to NAS shares, but often disconnect for no apparent reason.
Any suggestions to get network drive access back to previous acceptable speeds would be greatly appreciated.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Pianissimo84 wrote:
... I rebooted again and it seems that it's running better now; don't know why.
Good to know. One other poster reported a similar slowdown, and a restart resolved his issue also.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Slow network after ReadyNAS firmware updates
What firmware were you running before the firmware update?
If you haven't tried restarting the NAS, then start there.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Slow network after ReadyNAS firmware updates
- I keep the NAS current on FW, so the most recent version was 6.5.? (don't know the specific sub-version number).
- After installing the latest update, the system rebooted. I rebooted again and it seems that it's running better now; don't know why.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Pianissimo84 wrote:
... I rebooted again and it seems that it's running better now; don't know why.
Good to know. One other poster reported a similar slowdown, and a restart resolved his issue also.