Issue With Reaching My Network Drive Following Windows 11 Installation
Issue With Reaching My Network Drive Following Windows 11 Installation
Yes, you might want to give it a shot.
However, the My Net N600 is quite outdated, its newest firmware doesn’t even handle SMB 2.0, and
the addition of 24H2 requires SMB signing (RequireSecuritySignature=1).
Despite this, many users report issues with newer WDC My Cloud devices that support SMB 3.0 still not doing the same, even though Microsoft has encouraged adoption since Windows NT4.
You could upgrade the N600 by switching to modern third-party firmware that supports both SMB signing and SMB 3.0, which would also enable USB drive sharing features.
This would involve installing additional packages like Samba4 or ksmbd, along with adding a username and password for the share, to work with the standard Windows 24H2 setup.
Alternatively, you might think about upgrading from your Wireless-N device, which only has 10/100 ports, since you’ve clearly received good value over the past 13 years.
I understand it's quite outdated. It was already considered old when I acquired it. But I took it up mainly to serve as an access point in our basement where the Wi-Fi signal was weak. Its compact design made it ideal for the limited space we had. I mostly rely on the network drive to link to our TVs for streaming movies. It functions just fine like a simple, temporary media server. The only problem now is that I can't transfer new videos from my computer anymore. At this stage, I might have to use my laptop to move files instead.
At 560MHz, USB 2.0 operations should be constrained by the CPU to roughly 10 and 5MB/s, which aligns well with 10/100 ethernet speeds. The issue arises when enabling encryption features like SMB signing and SMB 3.0 with updated firmware, as these processes are software-based and can further reduce drive performance. What speed is considered acceptable depends on the setup—if it's a single computer and security isn't a major concern, you can restore the older networking configuration in Windows, eliminating the need for a password.
Yeah, I don't really focus much on security because it's just my computer on our private network. But I've already made these changes and it didn't fix my issue. I'm considering moving my network drive to the newer main router. I only realized this today—it's pretty new and should support the newer SMB. I kept trying to use the old method, but I didn't think about whether there might be a better way.
I encountered a network path issue after upgrading from Windows 7 to 10 and then to 11 Pro. All other machines could still reach the server. I attempted standard solutions but none resolved the problem. It turned out my HOSTS file contained an outdated IP address for the server. Correcting that resolved everything.