Something has changed in my setup here over the last few weeks. I can control my Innuos via a browser using the IP address. However, the Innous (and a new NUC) do no show up in the Network window of File Explorer. Also the shortcut to the HDD of the Innuos which I set up a while back does not work. The troubleshooter tells me:
Your computer appears to be correctly configured but the device or resource (IP address of Innuos) is not responding.
There were two separate changes:
(i) The Innuos disappeared from the Network according to Windows following an update. This was when I set up the shortcut.
(ii) The shortcut stopped working following a change of Modem/Router on Monday.
Were inuus and nuc using dynamic or static IP before you changed the router?
If dynamic then they have almost certainly been given a different IP address by the new router, if static u need to check that new router is using same ip range as old one, otherwise they may be on a different network
Does your shortcut point to the ip address or a dns name?
If name, they you may need to add it tot he routing table in new router so it knows what ip the name refers to, unless you have another DNA server elsewhere
The shortcut points to an IP address. I can use a browser to connect to the device via this address. I cannot map the feckin’ thing as a network drive though. It is a NAS so this is a bit of an issue.
I have to say, my cross mounts to my NAS are exceptionally reliable. But since moved all my music from my NAS to the Aries Mini, the AM keeps dropping off the network shares.
So, I got everything up and running again (sort of) but then noticed that I had an email from @maverick today. Effectively, Paul said:
it is an issue with SMBv1 if you are using Windows 10?
Basically Windows 10 Home and Windows 10 Professional still contain the SMBv1 client by default
So for Windows 10 - if the SMBv1 client or server is not used for 15 days in total (excluding any time during which the computer is off), they each automatically uninstall themselves. thanks M$
Automatic removal of SMBv1 after 15 days is a one-time operation. If an administrator re-installs SMBv1, no further attempts will be made to uninstall it (this is good news)
so check this: Control Panel>programs and features>Turn Windows features on or off find SMB 1.0/CIFS File Sharing Support and check all the boxes - note it has three sub-items.
reboot
Soooo, following Paul’s advice I reinstalled SMBv1 and everything works again. What a fucking stupid and useless update!!
Many thanks to Paul, and perhaps those of us using Windows 10 might like to reinstall SMBv1 to get stuff going again.