NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Connection Lost
4 Topics
ReadyNAS Pro 4 [X-RAID2] repeatedly inaccessible or looses connection to LAN on big data transfer
Trotz Factory-Reset verliert die ReadyNas Pro4 nach Update auf RAIDiator 4.2.31 beim Transfer größerer Datenmengen (so etwa ab 1 GB) ständig die Netzwerkverbindung bzw. verschwindet dann vom Netzwerk (IP-Adresse nicht mehr ansprechbar) und ist erst nach manuellem Neustart (Power off) wieder "ansprechbar". Wer weiß Abhilfe?4.4KViews0likes12CommentsReadyNAS Pro 4 [X-RAID2] looses connection to LAN repeatedly maby cause update to RAIDiator 4.2.31
My ReadyNAS Pro 4 ist connected to my LAN via a Netgear WNR 3500L just used as a switch, the router and DNS-server is a Maipu-Modem. This configuration worked quite well for 2 years. About two or three month ago my NAS startet to loose connection to the LAN in an increasing frequency. The only way to reconnect the NAS is to manually shut it down and restart it. Update to firmware RAIDiator 4.2.31 did not help, but made the situation even worse. The ReadyNAS now only stays connected for a few minutes before it hides itself again. Data transfer especially writing data seems to accelerate the disconnection. Can anyone help me? I'm just a basic user with no great experience in setting up networks or things like that. So please explain on a very basic level for me.Solved1.5KViews0likes5Comments
SONOS & ORBI : FW V1.5.0.12 - not working anymore
since FW 1.5.0.12 - my sonos system is constantly loosing its connection - tried different seups, the only setup which works at the moment is nr 4. as soon as the SONOS players and the ORBI system are in the same network, something went wrong like disappearing SONOS player / sonos players are loosing their ip adress ( tested also with static adress, but with no success) - SONOS customer care team has checked the players and found out that a heavy multicast traffic is causing the bridge disconnects and suggested to separate both. but before that FW update, the system was set up like nr 1 and was working! setup: 1.modem (AVM fritzbox, WLan disabled) --> Orbi (Router mode)--> SONOS Bridge via ethernet 2.modem (AVM fritzbox, WLan disabled) --> Orbi ( AP mode) --> SONOS Bridge via ethernet 3.Modem (AVM fritzbox, WLan disabled) --> SONOS Bridge via ethernet port 1 & Orbi ( AC mode) via ethnernet port 2 of the modem 4.Modem (AVM fritzbox, WLan disabled) --> SONOS Bridge via ethernet port 1 & Orbi ( Router mode) via ethnernet port 2 of the modem main issue with setup 4 - the SONOS brigde gets an IP from the modem´s DHCP while all other computers/tablets connecting wirelessly to the ORBIs other DHCP range --> resulting : the android controller is not seeing the SONOS players ( any suggestion like static routing ?)Solved