Hi, had my readynas 104 for 10 months with three x 3TB drives fitted - all working well - but had occasional failed transfers to it but this seems to have cleared up till recently. I spotted it wasn't on the network the other day, pressing the power button briefly showed it was happy, 73% space remaining and the fixed ip address. Still couldn't connect to it.
Pressing the backup button for 5s to try the reconnect and is says cannot connect discovery server. It stays like this for some time - about 5 minutes, and then screen goes off and hitting the power button all seems fine on the display. Still not on the network.
It's never had a power-down, so am loathe to do this if not needed if there's a possibility it might cause other issues - is that the next thing though?
so I've bitten the bullet and held the power button in, released , saw message to shut down so pressed power again. Shut down, powered on, and still saying cannot connect discovery server, - lights are on the hub, and then it seems now to have got back to normal and I can now see it. Just needed a kisk up its backside I guess...
OK, still got issues - can't connect any other computers to the nas through wifi, the desktop works, which is wired into a gigabit switch in the same room as the nas, tried laptop wired into switch and it won't see it either! I'm sure I had fixed the ip before the reboot, it always had the same address on the nas box, now since reboot it's 192.168.1.100 and not changed. It's now giving me the "cannot connect discovery server" again after holding the backup button for 5 seconds and https://readycloud.netgear.com/client/index.html#page=discoverdevices won't see it.
Raidar sees it - on laptop wired and wifi, and so does the desktop, but clicking on setup takes me to https://192.168.1.100/admin/ where I then get the message "This webpage is not available"
I can still access files on the nas via the desktop.
"can't connect any other computers to the nas through wifi, the desktop works, which is wired into a gigabit switch in the same room as the nas, tried laptop wired into switch and it won't see it either!"
Can you give us some more details on how your network is configured? Perhaps a simple diagram, also giving model numbers for switches, routers, access points, powerline.
virgin cable i i virgin router and hub i i Netgear wifi (better range than the Virgin media issue one so have disabled wifi on theirs i i ethernet from Netgear hub to powerline - TP link 500 both ends i i tp 500 connected to netgear 8 port gs108 switch i i i this is then connected to my desktop and the nas and the laptop I tried. the NAS isn't showing on my network on the deskop, but I can access it via the drive letter Z I created when I installed it.
Ok. So you can access the NAS from the desktop, even though the NAS isn't appearing on the left pane of windows explorer.
You can't access it from the laptop at all? Even with \\nas-name or \\nas-ip-address entered directly into the windows explorer address bar (using the real name and IP address of course)???
The TP500 is almost certainly faster than your virgin internet. It's not as fast as the NAS though. Whether its faster than your wifi link depends on the WiFi mode and the circuit quality on the TP-500 connections. The change shouldn't do any harm (assuming the new router location is good for WiFi coverage), and it might be somewhat better.
I can't even get to it via the IP address on the desktop (from where I can access the NAS!) p.s. Is it normal to type an IP into windows explorer and have it open in Chrome?
Have the topology as it is as the virgin cable comes into the back of the house and the study with all my IT is in the front. Router at back covers the garden and kirchen extension, but wouldn't reach if I had the router in the study.
Moved nas to bedroom where internet comes in. Plugged into the Netgear router and afterwards also the Virgin router. display still reads cannot connect discovery server (from both routers), still can't access via IP (192.168.1.121) (from bouth routers) BUT is still accessible via the desktop when it was plugged into EITHER router.
yes, that's how all things were connected, to the netgear router.
typing in \\192.168.1.121 into windows explorer does nothing... eventually only bring up the popup "network error" and windows cannot access 192etc - diagnose etc.
pressing and holding the backup button brings up the message cannot connect discovery server and pressing and holding again brings up discovery on.
also, running readynas remote, I get this error
"ReadyNAS Remote is currently running and needs to be stopped before running ReadyNas Remote" - readynas isn't running - I've checked task manager too...
I've unistalled it and reinstalled it now. Readynas remote says nas is offline. raidar sees it, it's current OS, but can't enter setup.
I had the same issue. Moved to Eth1 or the other ethernet input and started working again. I was doing quite a bit of button mashing trying to understand a different issue, but the settings were still good. Beta FW fixed it for me.
