- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: ReadyNAS 104 constantly polling peer server
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My ReadyNAS 104 is constantly, and I mean every 1-2 seconds according to firewall logs, making a connect attempt to "peerserver4-ncal.netgear.com/peer/request"
I cannot seem to locate where this could be coming from on the NAS interface so figured I wouuld ask the experts.
Any help would be appreciated as this seems excessive.
Thanks
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which services and apps are you running?
6.2.4 is old firmware released back in April last year.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 104 constantly polling peer server
Are you using ReadyCLOUD?
Which firmware are you running?
Welcome to the Community!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 104 constantly polling peer server
Hi,
I was using ready cloud, however I have turned it off.
Firmware is 6.2.4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which services and apps are you running?
6.2.4 is old firmware released back in April last year.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 104 constantly polling peer server
Services are: SMB, AFP, NFS, FTP, ReadyDLNA, HTTP, HTTPS, SSH
No apps are running.
I will update the firmware to 6.4.2 (which it is saying is the latest) now and update after
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS 104 constantly polling peer server
The update to the firmware appears to have resolved the issue - thanks!