NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Connect error code: -300 ?
Hi,
This has happened several times between two ready NAS's. The only fix seems to be to create a new backup session and run the initial backup over the local LAN before separating them and backing up over WWW.
Anyone else seen this error?
FYI Nothing has changed in the ADSL routers at either end other than the IP address delivered by the ISP may have changed because it's not fixed, would that cause this problem?
Error log shows:-
Info] p2p connect to nas-(MAC address) in (7 digit number) network
[2014-10-26 21:04:14] [Error] Unable to connect to nas-MAC address
[2014-10-26 21:04:14] [Error] Connect error code: -300
This has happened several times between two ready NAS's. The only fix seems to be to create a new backup session and run the initial backup over the local LAN before separating them and backing up over WWW.
Anyone else seen this error?
FYI Nothing has changed in the ADSL routers at either end other than the IP address delivered by the ISP may have changed because it's not fixed, would that cause this problem?
Error log shows:-
Info] p2p connect to nas-(MAC address) in (7 digit number) network
[2014-10-26 21:04:14] [Error] Unable to connect to nas-MAC address
[2014-10-26 21:04:14] [Error] Connect error code: -300
6 Replies
Replies have been turned off for this discussion
- What version of ReadyNAS OS is on each NAS?
- Both on 6.1.9 and Replicate 1.2.0 Build 6
- So you get the error code -300 often?
- Happened back in April but we thought it may have been caused by a power outage at the backup end.
Units were installed new in March this year. - Same error -300.
Also tried to fix it with upgrading to 6.2. --> back up kept failing
New base without same LAN also fails. The website can browse from the replicate site and can see the number of files. No files are transmitted though.
BTW: after upgrade to 6.2 Readynas Remote (without using ReadyCloud) fails as well.
I will try to but them together in the same LAN and try it again. - Try to port-forward TCP 6819 to the destination unit from the WAN address. It would eliminate leafp2p as a possible issue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
