This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
So when your old Windows 10 computer dies, you replace it with a new one which will now come, by default, with Windows 11, right?
This is what happened to me. The new PC came with Windows 11 Pro already installed (which may or may not be a good thing). Fortunately I was able to salvage the SSD, HHD and memory (it was just a dead power supply on the old one), meaning migrating and getting everything up and running was a (fairly) quick operation on the new one, which generally is what you want.
But what about the ReadyNAS backups? They fail of course – unable to reach host. Not unreasonable. A quick change of host and login criteria should fix that, right? No. Changing the username and password to match what you log into Windows with won’t work and here’s why:
Under Windows 11 Microsoft require you to create two user profiles, a local machine-based one, and a network one with them. By default, you use the network profile so you can use all their lovely OneDrive, Office 365, etc services – for which, of course, you pay (I found a genuine Office Pro Plus 2021 licence for £28 on a very large online retailer site, so no I won’t, thanks). When you start up the new PC for the very first time and go through the Windows 11 setup, Microsoft lead you to believe you’ve set up both the network and your local accounts. In reality, it seems, the local one is incomplete. This means the ReadyNAS backup of the new Windows 11 machine will fail – it will try and use the local account, not the network one, but because that’s incomplete, it can’t ever log in.
The solution is simple, although not obvious. On your Windows machine you’ll need to complete the local account setup. Go into Control Panel (not Settings!) > User Accounts > Make changes to my account in PC settings. This will then redirect to Accounts > Your info in the Settings program (I suspect there’s another way to get to this, but it’s not obvious). Scroll down the window and you’ll see an Account settings section. You’ll need to change this to Local account, where it will then prompt you to set up a password. Once you’ve done that, test it by logging out of the network account and into the local one – I think Windows forces you to do this anyway. Interestingly, trying to switch back to the network profile fails with an error, but frankly, at the moment, I don’t care.
Over on ReadyNAS enter the now complete local account name and password in the Backup Source tab and test the connection. It should work. Happy days!
One caveat: I’m having to use the IP address as the remote host, as ReadyNAS is currently not recognising the new computer name, so that’s the next problem to resolve. Otherwise my backups are (for now) working again – until I reboot the PC perhaps!
Then reserving its WIFI IP address in the router will help.
Then either edit the backup job(s) for the PC to use the IP address instead of the hostname, or edit the hosts file on the NAS so you can continue to use the hostname.
I haven't really thought seriously yet about the configuration of the new network equipment to be honest, but have taken the opportunity to cable in whilst access is available
I did that some years back. Even though I have at least one ethernet line running to each room, I still like the mesh.
My desktop PCs and ReadyNAS use ethernet, and I do use ethernet as the backhaul for the mesh. But laptops, phones, tablets, etc all are just on wifi.
If I had to choose whether I'd give up the mesh or give up the ethernet, I'd give up the ethernet first.
One caveat: I’m having to use the IP address as the remote host, as ReadyNAS is currently not recognising the new computer name, so that’s the next problem to resolve.
No longer actively operating any RedyNAS, I remember there is no mDNS-based resolver on the ReadyNAS (and in fact on any other industry standard NAS), and on most networks, the Windows clients can't register a DNS name dynamically.
Method of choice is to enable the SMB 1.0/CIFS (both client and server) protocol, as this brings the NetBIOS-based name resolution. Now you can even ping your NAS using it's configured name.
If you "fix" the IP address by reservation in your router (better than setting static address), you can make an entry into the HOSTS file ( C:\Windows\System32\drivers\etc\hosts, if on Windows) to add the entry to map the IP to the name. It's a simple text file with no extension. You can then use the NAS's name instead of the IP. Just be aware that if the IP changes (reset router, update router, change ISP etc.), you'll need to redo the reservation.
Didn't know ReadyNAS was so obsolete! It's been sitting there doing it's thing for a few years now, very happy with it, don't need anything else right now. Just the occasional firmware upgrade when they come out...
I should really move it to a different floor though, I have building work going on right now. What's the worst that could happen? 😬🔥 I have taken the opportunity to lay Ethernet cables of varying Cat whilst they do their stuff (when they turn up 😆), so undoubtedly will be going back to Netgear for upgraded kit very soon!
Thanks, but yeah the ReadyNAS is perfectly visible to the PC, no problem, drives mapped, etc. It's the other way that's the issue.
If the PC uses both wifi and ethernet (not at the same time), then I don't think there is a simple fix. If it is only connected to one interface, then reserving the PC's IP address in the router and then using the IP address in the NAS backup job will work.
Personally I prefer to run PC backups on the PC (with the NAS as the destination). FreeFileSync is one of several tools you can use for this. That would work around your problem, since your PC can always find the NAS.
so undoubtedly will be going back to Netgear for upgraded kit very soon!
Netgear has clearly exited the NAS business - the last ReadyNAS platforms were introduced back in 2017, and all ReadyNAS are identifed as end-of-life on the Netgear support pages.
So if you are looking for another ReadyNAS, then you would have to purchase a used model. If you want a supported NAS running a current linux distribution you will need to look at other vendors.
PC is wireless only, but ReadyNAS is wired to a Netgear switch. The new Ethernet is for the coming (haven't bought them yet) WAPs, junior's Xbox and the intended TIDAL streaming service. The WiFi struggles to get to many rooms, so some kind of wired network is necessary, and now is the time to be putting it in so it's not visible. Example of the problem is the Smart meter: the gas meter is outside the house, and has to get through 4 Victorian walls to the electricity meter inside. It has never succeeded, and I'm certainly not paying to have either of them moved or for some kind of special meter installed!
PC is wireless only, but ReadyNAS is wired to a Netgear switch.
Which is fine. If the PC is sometimes wireless, and sometimes wired then it will end up with two IP addresses (depending on how it is connected). In that scenario, reserving IP addresses in the router for the PC won't help.
But as I said earlier, I think it is better to run the backup jobs on the PCs with the NAS as a destination. There are several PC options, and they can be scheduled (including waking the PC up if it is powered down). FreeFileSync is one of the free ones, and could easily replace the NAS backup jobs you are using now.
Personally I like image backups, so I can restore the PC completely if the disk fails. I am currently using Acronis TrueImage.
The WiFi struggles to get to many rooms, so some kind of wired network is necessary,
I suggest looking at a wifi mesh first. It is easier to deploy, and in almost all cases can give you full-house coverage. You can then add ethernet selectively later on if you want to (for instance to get multigig to some devices).
I use an Orbi 860 at the moment, with two satellites. There are several other choices (both from Netgear and from other vendors).
PC is never wired, and not expecting it to be in the future when it gets to its permanent home in the new office (never say never of course).
I haven't really thought seriously yet about the configuration of the new network equipment to be honest, but have taken the opportunity to cable in whilst access is available. Electricians tend to avoid anything that's signal related and like to get a specialist in, but I can do that work myself, so...
If the wired setup ends up not getting used it doesn't matter, for the price of a cable, a few clips & some trunking. I do know I'll want a switch with PoE, as I intend to to put some kind of access point at the bottom of the garden where's there's no power - the armoured cable is already there.
Interesting we got here from ReadyNAS! Still think it's a great little unit! 😁
ReadyNAS do have a hosts file in which you can assign a name to an IP address, located at /etc/hosts. You can assign any name, even more than one, to an IP address by modifying the hosts file via SSH.
ReadyNAS do have a hosts file in which you can assign a name to an IP address, located at /etc/hosts. You can assign any name, even more than one, to an IP address by modifying the hosts file via SSH.
Yes, but if PC were connected via both wifi and ethernet, then you'd need two IP addresses with the same hostname. Which of course wouldn't work.
Then reserving its WIFI IP address in the router will help.
Then either edit the backup job(s) for the PC to use the IP address instead of the hostname, or edit the hosts file on the NAS so you can continue to use the hostname.
I haven't really thought seriously yet about the configuration of the new network equipment to be honest, but have taken the opportunity to cable in whilst access is available
I did that some years back. Even though I have at least one ethernet line running to each room, I still like the mesh.
My desktop PCs and ReadyNAS use ethernet, and I do use ethernet as the backhaul for the mesh. But laptops, phones, tablets, etc all are just on wifi.
If I had to choose whether I'd give up the mesh or give up the ethernet, I'd give up the ethernet first.
Yes, but if PC were connected via both wifi and ethernet, then you'd need two IP addresses with the same hostname. Which of course wouldn't work.
True, but you can define two host names and define two backup jobs. The one for the interface to which the computer is connected will complete, the other will fail. That allows you to use easier remembered names instead of IP addresses.
Still, I also find that having the backup originate from the PC is best. It can take advantage of Windows Shadow Copy to back up open files (especially things like email databases) and doesn't require that the PC be on all the time (so long as the software used on the PC has a function that starts a missed backup after power-on).
