NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
USB Storage not found on C3000-100NAS
Firmware version: V2.02.21
Model: C3000-100NAS
Mfg Label: Netgear
Operating System: Windows 10 Pro w/ latest patches
1. Admin home page shows ReadySHARE is READY with no drive attached (so I assume this means the gateway is ready to support USB attached storage).
2. Storage device is a Western Digital My Home 1TB USB drive with external power, formatted with FAT, and has 3 folders already on it with content (which can be seen when attached to a PC or another NAS on my local area network).
3. Attached the external NAS and rebooted the gateway (just to be sure).
4. I can see the existing folders when I view them through the ReadyShare Admin panel on the gateway.
5. Firewall has been both enabled and disabled on local area network.
Cannot map either a network place or a new drive to either PC on the network. I am using the gateway login information during the mapping, but still get an error message is "Can't..."
I've looked at the forum and don't see anything that seems to address this issue directly.
Found the issue: the Network Neighborhood option was not enabled so the readyshare server was not responding to mapping requests.
5 Replies
Do you have any other USB drives you could try?
ReadySHARE can be picky.
The list of known devices for this modem/router is no encouraging:
ReadySHARE USB Drives Compatibility List | Answer | NETGEAR Support
But it is usually on the pessimistic side and out of date.
What do you see here?
ADVANCED > USB Storage > Advanced Settings
I have removed the WD My Cloud Mirror and replaced it with a Toshiba portable 500GB drive. I had the same results when I tried to map a network drive to either of the 2 PCs on the local area network. I have attached the screen shot as requested. The error message seems to indicate that \\readyshare is not a broadcast servername, so I tried \\192.168.0.1 and received the same results. I have the gateway set NOT to broadcast the Network ID, but seriously doubt that is the issue.
Found the issue: the Network Neighborhood option was not enabled so the readyshare server was not responding to mapping requests.
