I don’t know what happened this weekend but suddenly I lost access to my WD My Cloud. I’ve done a hard-reset of the drive and I still can’t connect to it. I’ve received the NAS alert mail that the drive had been reset so I know the network is ok. I see the drive with the IP 192.168.1.7 and I can even ping it:
Pints-2:~ eduardonpinto$ ping 192.168.1.255
PING 192.168.1.255 (192.168.1.255): 56 data bytes
64 bytes from 192.168.1.200: icmp_seq=0 ttl=64 time=0.062 ms
64 bytes from 192.168.1.50: icmp_seq=0 ttl=255 time=1.538 ms
64 bytes from 192.168.1.7: icmp_seq=0 ttl=255 time=1.787 ms
Pints-2:~ eduardonpinto$ ping 192.168.1.7
PING 192.168.1.7 (192.168.1.7): 56 data bytes
64 bytes from 192.168.1.7: icmp_seq=0 ttl=255 time=3.841 ms
64 bytes from 192.168.1.7: icmp_seq=1 ttl=255 time=2.328 ms
I’ve also tried to SSH to it but I get a “connection refused”:
I thought I knew to what the other IPs beside the .7 belonged to but it seems I was wrong. The IP address of the drive was actually the .9 and for an unknown reason my TimeCapsule wasn’t bridging to the drive. It is all working fine now after a restart of the TimeCapsule.
I am having a simialr issue. The WD my cloud was visable as a separate network device in windows now it is not showing. The main probelm is that I cannot map SMB shares to the device via the windows 7 laptop, yet oddly I can access the SMB share via a “Raspberry PI 2” and via an Android tablet. The laptop knows that the device is there as it is seeing it as storrage the issue is that its only showing the public shares and not the shares I have created. I have download some WD software and it is now mapping the indivdual shares as network drives but this does not really solve my issue as I am trying to map these in Kodi but it keeps dropping out. Any help appriacated.
yet oddly I can access the SMB share via a “Raspberry PI 2” and via an Android tablet.
What IP address are you using to map the SMB drive on those devices? Or are you relying on a name resolution (i.e. using smb://wdmycloud/sharename)? If the latter, it may be that the name resolution hasn’t caught up with a change in IP address.
Check your router to find out what IP address has been assigned to the MyCloud, and then use the router to fix that address, so it won’t change again; use an infinite DHCP timeout (‘always use this address’ on my router), or you could set it static.