NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
eyalrt
Aug 27, 2023Aspirant
Cannot detect WD cloud home device
I have Orbi RBR350 Mesh Router. I also have a WD home cloud personal storage, and I can access it from the internet or my cellular using Android APP any time I want, but for some strange reason, t...
CrimpOn
Aug 30, 2023Guru - Experienced User
eyalrt wrote:
I cannot see the drive. It freaks me out.
It looks like a bug in the Router software.🙂
There is probably no method to have the WD drive display its network parameters:
- IP address
- subnet
- Gateway
- DNS servers
Nothing in Attached Devices with that MAC address?
When the WD drive is plugged in, the number of attached devices does not increase?
eyalrt
Aug 30, 2023Aspirant
Hi CrimpOn,
no. nothing. no change, as if the drive doesn't exist. The number of connected devices stays the same.
eyalrt
no. nothing. no change, as if the drive doesn't exist. The number of connected devices stays the same.
eyalrt
- CrimpOnAug 30, 2023Guru - Experienced User
- eyalrtAug 30, 2023AspirantHi CrimpOn,
Thank you for investing time helping me.
I have tried this already. from the WD site, I can now log in as a remote user, or as a local user, which is the same, because it is from WD site.
Since the Orbi router doesn't detect or report the device, windows/linux (tried both) cannot detect it either. This is why it is a bug. If it cannot detect the device and it has no ip, it cannot access it.
The drive must have an IP, or WD couldn't access it as well. It does.
The router doesn't report it for some reason....
thanks, again,
eyalrt- schumakuAug 30, 2023Guru - Experienced User
Hard to imagine it does not have an IP address - considering it's able to reach the WD Cloud Home through your network.
The WD "design" (almost non-existing, no utilities for discovery, no common ) to figure out the LAN IP appears to be issuing an arp -a from the command line, and then locate the IP address based on the MAC address printed on the device label.
Have already enabled the Windows feature to enable the SMB 1.0/CIFS Client and SMB 1.0/CIFS Server (the automatic removal is not required - certain risk that if not making use of SMB 1.0/CIFS for a certain time it does disappear magically), and rebooted the system?
Once done so, I would expect the WD Cloud Home system to become visible. Some WD resources state only SMB2 and SMB3 is enabled by default. From what I understand, the current WD OS5 should be smb2 and smb3 only. But no idea on how these devices should appear on the average user desktop usually.
Start with the "discovery" using arp -a. Do a ping to the subnet, like 192.168.1.255 for example before.