Everything worked fine on my old Win10 PC, then I switched to a new Win10 PC. Readyshare is setup for no password read and write. I can access my readyshare drive to read, but not write. When I try to access it (as a network location), Win10 only offers a menu to Browse Folders (and access to Music, Pictures, and Video). I cannot create a folder or write at all to the readyshare drive. If I try on Win10 to map the drive, it cannot find it. The Browse Folders option allows me to read the readyshare drive just fine. I assume this must be a Win10 problem, not a Netgear problem.
Your router is pretty old, and I suspect it only supports SMB 1. Microsoft is deprecating that, so it is not enabled on new PCs. I am thinking that you have DLNA enabled in the router settings, and that Windows is using it to access the media on the drive.
Try going into "Turn Windows Features on or off", and see if the SMB 1.0/CIFS client is enabled. If it isn't, enable it (ignoring the security warning) and then see if you can access the files from file explorer. Enter \\router-ip-address in the address bar (using the real router IP address of course, and using the correct slash direction). The default router IP address is 192.168.1.1
Thanks. SMB 1 is enabled. My router is at 192.168.1.64. I try and access 192.168.1.64\readyshare\USB_Storage using Map Drive, and it tells me the device rejects the connection. Interesting, because Windows lets me read the device - just not write to it.
I don't know what AP is. I see no option on the router setup regarding that. I have set readyshare for no passwords. When I go to CMD and try net view \\192.168.1.64 or 192.168.1.1 or even the local 10.0.0.1, I get an error that no connection exists.
Maybe I am wrong about the IP. 192.168.1.64 is the internet IP. But why did net view not find 192.168.1.1? Yes, my system is set up for 10.0.0.x. Would AP do anything for me? The system works fine, except for this new USB writing issue.
Maybe I am wrong about the IP. 192.168.1.64 is the internet IP. But why did net view not find 192.168.1.1? Yes, my system is set up for 10.0.0.x.
If your local network is 10.0.0.x, then the internal IP address of the Netgear router would normally be 10.0.0.1.
192.168.1.64 is a private IP address. So if that is the Netgear's WAN address, then you are double-routing (your modem is actually a gateway - that is a modem+router, and you are connecting it to the Netgear).
You can confirm by running CMD on the PC (just enter CMD into windows search), and entering tracert 1.1.1.1
You should see something that looks like this:
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 <1 ms <1 ms <1 ms 192.168.1.1
3 7 ms 3 ms 2 ms one.one.one.one [1.1.1.1]
Trace complete.
There could be other stuff between the hop 2 and the final hop to 1.1.1.1
Network is private. Running Norton. Old PC has been trashed. tracert performed as expected. We do not seem to be getting any closer to finding the issue.
