After more than 2 years, can't access MyCloud by it's name, only by IP

ovisopa · December 31, 2017, 1:20pm

Hello guys, and girls

I used this cloud device for more than 2 year, a few months back I started to have issues with the iPhone app not being able to locate the device (and sync the photos). Most of the time this was fixed after rebooting the drive, sometimes. I want to talk about this issue too , but most important issue is the one that appeared today, I installed a new HTPC in my living room, it worked fine for a week, but today I could not access any mapped drives from MyCloud. I came down to my office to check and the drive was accessible from my workstation.
Moved back in the living room and I found out that the only way to access it was by IP, so I mapped again all drives using the IP address (\192.168.1.136\Movies) instead of the name (\xwdcloud\Movies)

Now I’m back in my office and it’s not working here also, the same issue, can’t access any mapped drive, can’t access by writing the address in Windows Explorer (\xwdcloud) only by IP (\192.168.1.136)

The IP address was set from the beggining as static, the name was also set from the day 1 .

Also trying to access it in browser is not an option, I get connection reffused

xwdcloud.local refused to connect.
Search Google for ncedcloud local
ERR_CONNECTION_REFUSED

Bellow is a screenshot with the drive top running processes.

Any recommendations from you guys, what I should check on the drive (using SSH) ?

ovisopa · January 4, 2018, 8:04am

Nobody with an suggestion ? Also My LG TV is not seeing the NAS shares anymore, and there I couldn’t find an option to browse by IP.

It must be something with the WD drive, but I’m not sure what, and what should I try.

Thank you.

cpt_paranoia · January 4, 2018, 8:37am

I’d suggest that it is your router, since it is your router that provides the DNS translation.

ovisopa · January 4, 2018, 12:19pm

I will check, but any other device in my network (pc or other nas) can be accessed by the name, only this device has those issues. Do you still think it could be the router ?

cpt_paranoia · January 4, 2018, 7:08pm

It could be.

Since you can get to the device via SSH, it appears that the ethernet connection is intact.

Can you access the Dashboard, either by name or IP address?

The fact that things started to go wrong when you added the HTPC could be coincidental, or causal… Have you tried removing the HTPC, and seeing what happens? Have you checked the network settings on the HTPC to make sure they’re consistent with your other computers?

One common reason for devices gradually disappearing from networks is IP address conflicts; have you checked your router’s IP table for clashes?

Have you tried resetting your router, or your MyCloud?

ovisopa · January 6, 2018, 9:25am

#1 I also think the ethernet connection to the WD MyCloud is ok, as I can still work in my office with all the files on the shares, using the HTPC in the living room or the media player in the bedroom I can watch movies without any issue, after I mounted the new drives using \192.168.1.136\Movies instead of \mycloud\Movies

#2. Accessing MyCloud Dashboard using a browser is not working either by IP or by hostname (ERR_CONNECTION_REFUSED)

#3. The HTPC was in my network since 15 december, but I had it in my office (same LAN) while configuring and testing Kodi, games … etc, everything was fine. The IP if HTPC is set manually to .4

#4 Most of my devices are using static IP, HTPC and all other PC, also the media players have static IP address, bellow .100, I set up DHCP in the router to assign automatic IP addresses only from .100 to .254, I reserved the bellow .100 to devices I will manually set IP. The IP of MyCloud was always set .136 … but I will change it now to something bellow .100.

After I rebooted the WD MyCloud using SSH I could also connect again by it’s name, also the web interface is working again and also the iPhone App has synced my photos (but this has happen in the past, after a reboot is working, but a few more time it will not work again - the sync process)

Now, being sure there is something wrong with the software of MyCloud, do you have any ideas what I could check, if any of the bellow issue happens again ?

The iPhone app says the device is offline after a while, since rebooting the WD MyCloud
We interface is not available “ERR_CONNECTION_REFUSED” appears in the browser.
This happen only once, now about a week ago, the device shares ware not accessible by device name, only by it’s IP.

PS. My router is Asus RT-AC1200G+

Thank you.

cpt_paranoia · January 6, 2018, 1:17pm

Locally, or remotely?

If your remote access fails after some time, check to see if your router has rebooted (and been given a new global IP address by your ISP). If this happens, cloud access is disrupted, and you need to toggle the Cloud Access control in the Dashboard to re-establish it.

I note that you don’t appear to have done a MyCloud reset yet; reboot is not a reset. Reset requires you to push the reset button. See the user manual for the two types of reset, and their consequences.

ovisopa · January 9, 2018, 7:34am

I’m only talking about local connection only (iPhone is connected to the same Wifi), all PCs and TVsare in the same network.

I haven’t reset the WD yet as it is used daily, and didn’t had free time to make the entire process.

In my prev post I told you that after reboot I was able to connect to the administration webpage in the browser, but not it doesn’t work again. I can access the mapped drives by their name, also by IP but I can’t connect to the administration page (locally).
UPDATE. And after a few more hours accessing the drive by name is not possible anymore, again I can access it only by IP

I don’t know if it helps, but bellow are the last few lines of some log files

XWDCloud:/var/log# tail -10 user.log
2018-01-06T11:27:08.423129+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout
2018-01-06T11:27:35.804541+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout
2018-01-06T11:27:57.504839+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout
2018-01-06T11:28:18.521323+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout
2018-01-06T11:28:58.490663+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout
2018-01-06T11:29:23.004853+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout
2018-01-06T11:33:14.469248+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout
2018-01-06T11:33:43.817392+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout
2018-01-06T11:34:07.561456+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout
2018-01-06T11:34:55.378042+02:00 di=qfImQyNXvc notice restsdk[6243]: paths.go:49: Reading from crawler socket, error: read unix @->/tmp/WDMCRequest.socket: i/o timeout

XWDCloud:/var/log# tail -10 wdphotos.log
ReadOnly: 0
2018-01-06T02:45:19.510886+02:00 di=qfImQyNXvc info wdphotodbmerger: Iterating over mount point /shares
2018-01-06T02:45:19.510986+02:00 di=qfImQyNXvc info wdphotodbmerger: Iterating over mount point /shares/
2018-01-06T02:45:19.697764+02:00 di=qfImQyNXvc info wdphotodbmerger: The volume is plugged and capacity is 3359940608.000000 and capacity_used is -234012672.000000 for mountPoint /shares/
2018-01-06T02:45:19.698048+02:00 di=qfImQyNXvc info wdphotodbmerger: MasterVolumeScannedState:: VolumePlugged, ignoring!
2018-01-06T06:07:30.395912+02:00 di=qfImQyNXvc info wdphotodbmerger: :: Transcodedbatch
2018-01-06T06:07:30.462310+02:00 di=qfImQyNXvc info wdphotodbmerger: Profile ==> cb62bbdd389b48898f2e5244977cb2c5 ==>
2018-01-06T06:07:30.488051+02:00 di=qfImQyNXvc info wdphotodbmerger: MasterVolumeScannedState:: handlePictureTranscoded, doing merge for mountPoint /shares/ using master volume at /shares
2018-01-06T06:14:53.464717+02:00 di=qfImQyNXvc info wdphotodbmerger: Retrieved changed folders list for /shares/ in 434.035 W   7.400 U   2.720 S   2.3%
2018-01-06T08:19:52.480517+02:00 di=qfImQyNXvc info wdphotodbmerger: Retrieved 500047 changed files list for /shares/ in 7497.904 W   54.310 U   51.200 S   1.4%

XWDCloud:/var/log# tail -10 wdnas.log
2017-12-25T20:02:58.707329+02:00 di=qfImQyNXvc notice wdAutoMounter[7216]: AutoMounter started
2017-12-26T21:29:38.493835+02:00 di=qfImQyNXvc info logger: updateShareBindMntDir.sh:--delete TimeMachineBackup
2017-12-26T21:29:39.163146+02:00 di=qfImQyNXvc info logger: updateShareBindMntDir.sh:umount succeded
2017-12-26T22:51:04.791291+02:00 di=qfImQyNXvc notice wdAutoMounter[7216]: AutoMounter stopped
2017-12-26T22:55:51.294514+02:00 di=qfImQyNXvc info logger: updateShareBindMntDir.sh:--init
2017-12-26T22:56:27.324752+02:00 di=qfImQyNXvc info logger: /usr/local/sbin/monitorTemperature.sh: Starting Temperature Monitor
2017-12-26T22:57:37.145430+02:00 di=qfImQyNXvc notice wdAutoMounter[7085]: AutoMounter started
2018-01-06T00:08:47.707611+02:00 di=qfImQyNXvc info logger: updateShareBindMntDir.sh:--init
2018-01-06T00:09:22.875277+02:00 di=qfImQyNXvc info logger: /usr/local/sbin/monitorTemperature.sh: Starting Temperature Monitor
2018-01-06T00:10:33.222772+02:00 di=qfImQyNXvc notice wdAutoMounter[7086]: AutoMounter started

XWDCloud:/var/log# tail -100 wdalerts.log
Nov 29 06:13:45 XWDCloud nas: warning:  { "msgid":"alert", "code":"2035", "level":"info" }
Nov 29 06:18:41 XWDCloud nas: warning:  { "msgid":"alert", "code":"2004", "level":"info" }
Nov 29 10:42:33 XWDCloud nas: warning:  { "msgid":"alert", "code":"1001", "level":"warning" }
Dec  2 12:37:36 XWDCloud nas: warning:  { "msgid":"alert", "code":"2001", "level":"info" }
Dec  2 20:36:50 XWDCloud nas: warning:  { "msgid":"alert", "code":"1001", "level":"warning" }
Dec 25 20:03:13 XWDCloud nas: warning:  { "msgid":"alert", "code":"2001", "level":"info" }
Dec 26 00:24:53 XWDCloud nas: warning:  { "msgid":"alert", "code":"1001", "level":"warning" }
Dec 26 22:57:34 XWDCloud nas: warning:  { "msgid":"alert", "code":"2001", "level":"info" }
Jan  6 00:10:40 XWDCloud nas: warning:  { "msgid":"alert", "code":"2001", "level":"info" }
XWDCloud:/var/log# tail -20 wdmcserver.log
Traceback:
thrown from /data/workspace/workspace/wdmcserver_3.0.1/src/util/Socket.cpp, line 403
2018-01-06T11:28:36.376956+02:00 di=qfImQyNXvc info wdmcserver: [6851:0x437bf460] Error  Broken pipe
Traceback:
thrown from /data/workspace/workspace/wdmcserver_3.0.1/src/util/Socket.cpp, line 403
2018-01-06T11:29:30.150390+02:00 di=qfImQyNXvc info wdmcserver: [6851:0x437bf460] Error  Broken pipe
Traceback:
thrown from /data/workspace/workspace/wdmcserver_3.0.1/src/util/Socket.cpp, line 403
2018-01-06T11:29:30.150535+02:00 di=qfImQyNXvc info wdmcserver: [6851:0x437bf460] Error  Broken pipe
Traceback:
thrown from /data/workspace/workspace/wdmcserver_3.0.1/src/util/Socket.cpp, line 403
2018-01-06T11:33:51.696219+02:00 di=qfImQyNXvc info wdmcserver: [6851:0x437bf460] Error  Broken pipe
Traceback:
thrown from /data/workspace/workspace/wdmcserver_3.0.1/src/util/Socket.cpp, line 403
2018-01-06T11:33:51.696371+02:00 di=qfImQyNXvc info wdmcserver: [6851:0x437bf460] Error  Broken pipe
Traceback:
thrown from /data/workspace/workspace/wdmcserver_3.0.1/src/util/Socket.cpp, line 403
2018-01-06T11:36:02.597735+02:00 di=qfImQyNXvc info wdmcserver: [6851:0x437bf460] Error  Broken pipe
Traceback:
thrown from /data/workspace/workspace/wdmcserver_3.0.1/src/util/Socket.cpp, line 403

XWDCloud:/var/log/apache2# tail -20 error.log
[Sat Jan 06 11:31:12.878992 2018] [mpm_prefork:error] [pid 4223] AH00161: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting

XWDCloud:/var/log# tail -30 daemon.log
2018-01-06T00:09:00.824516+02:00 di=qfImQyNXvc info ifplugd(eth0)[5131]: Program executed successfully.
2018-01-06T00:09:18.372026+02:00 di=qfImQyNXvc info init: no more processes left in this runlevel
2018-01-06T00:09:18.912870+02:00 di=qfImQyNXvc info init: Switching to runlevel: 2
2018-01-06T00:09:19.910759+02:00 di=qfImQyNXvc info atopacctd[5897]: Version: 2.2-3 - 2015/06/25 11:07:21  <gerlof.langeveld@atoptool.nl>
2018-01-06T00:09:24.559486+02:00 di=qfImQyNXvc notice rpc.mountd[6222]: Version 1.2.6 starting
2018-01-06T00:09:27.719575+02:00 di=qfImQyNXvc err winbindd[6316]: [2018/01/06 00:09:27.719177,  0] param/loadparm.c:7885(lp_set_enum_parm)
2018-01-06T00:09:27.719997+02:00 di=qfImQyNXvc err winbindd[6316]:   WARNING: Ignoring invalid value 'SMB3' for parameter 'max protocol'
2018-01-06T00:09:27.720379+02:00 di=qfImQyNXvc err winbindd[6316]: [2018/01/06 00:09:27.720194,  0] param/loadparm.c:7969(lp_do_parameter)
2018-01-06T00:09:27.720643+02:00 di=qfImQyNXvc err winbindd[6316]:   Ignoring unknown parameter "smb2 leases"
2018-01-06T00:09:27.728743+02:00 di=qfImQyNXvc err winbindd[6316]: [2018/01/06 00:09:27.728519,  0] param/loadparm.c:7969(lp_do_parameter)
2018-01-06T00:09:27.729126+02:00 di=qfImQyNXvc err winbindd[6316]:   Ignoring unknown parameter "durable handles"
2018-01-06T00:09:27.729482+02:00 di=qfImQyNXvc err winbindd[6316]: [2018/01/06 00:09:27.729301,  0] param/loadparm.c:8004(lp_do_parameter)
2018-01-06T00:09:27.729762+02:00 di=qfImQyNXvc err winbindd[6316]:   Global parameter kernel oplocks found in service section!
2018-01-06T00:09:27.730209+02:00 di=qfImQyNXvc err winbindd[6316]: [2018/01/06 00:09:27.730044,  0] param/loadparm.c:7969(lp_do_parameter)
2018-01-06T00:09:27.730472+02:00 di=qfImQyNXvc err winbindd[6316]:   Ignoring unknown parameter "kernel share modes"
2018-01-06T00:09:27.731051+02:00 di=qfImQyNXvc err winbindd[6316]: [2018/01/06 00:09:27.730886,  0] param/loadparm.c:7969(lp_do_parameter)
2018-01-06T00:09:27.731308+02:00 di=qfImQyNXvc err winbindd[6316]:   Ignoring unknown parameter "max share size"
2018-01-06T00:09:27.731748+02:00 di=qfImQyNXvc err winbindd[6316]: [2018/01/06 00:09:27.731588,  0] param/loadparm.c:7969(lp_do_parameter)
2018-01-06T00:09:27.731999+02:00 di=qfImQyNXvc err winbindd[6316]:   Ignoring unknown parameter "drive cache flush"
2018-01-06T00:09:27.732260+02:00 di=qfImQyNXvc err winbindd[6316]: [2018/01/06 00:09:27.732113,  0] param/loadparm.c:7209(service_ok)
2018-01-06T00:09:27.732512+02:00 di=qfImQyNXvc err winbindd[6316]:   WARNING: No path in service TimeMachineBackup - making it unavailable!
2018-01-06T00:09:27.751074+02:00 di=qfImQyNXvc err winbindd[6317]: [2018/01/06 00:09:27.750698,  0] winbindd/winbindd_cache.c:3147(initialize_winbindd_cache)
2018-01-06T00:09:27.752650+02:00 di=qfImQyNXvc err winbindd[6317]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
2018-01-06T00:09:28.583671+02:00 di=qfImQyNXvc notice netatalk[6352]: Netatalk AFP server starting
2018-01-06T00:09:29.202087+02:00 di=qfImQyNXvc notice cnid_metad[6354]: CNID Server listening on localhost:4700
2018-01-06T00:09:29.267472+02:00 di=qfImQyNXvc notice afpd[6353]: Netatalk AFP/TCP listening on 192.168.1.136:548
2018-01-06T00:09:29.420609+02:00 di=qfImQyNXvc notice ntpdate[5921]: adjust time server 80.96.120.252 offset -0.005563 sec
2018-01-06T01:09:26.185722+02:00 di=qfImQyNXvc warning atopacctd[5897]: reactivate process accounting
2018-01-06T03:00:46.775717+02:00 di=qfImQyNXvc notice ntpdate[10041]: step time server 31.28.161.68 offset -1.701740 sec
2018-01-06T09:01:21.162676+02:00 di=qfImQyNXvc warning atopacctd[5897]: reactivate process accounting

XWDCloud:/var/log# tail -10 mycloud.log
2018-01-06T03:01:25.556005+02:00 di=qfImQyNXvc notice deviceInfoCollect: { "msgid":"configuration", "ftp_enabled":0, "volume_encryption_enabled":0, "dlna_enabled":0, "cloud_access_config":"auto", "drive_standby_enabled":1, "language":"en_US", "RAID_mode":"na", "time_machine_enabled":1, "network_config":"static", "auto_update_enabled":1, "iTunes_enabled":0, "ssh_enabled":1 }
2018-01-06T04:11:51.575114+02:00 di=qfImQyNXvc notice CommMgr: { "msgid":"cloudConnectivity", "state":"connecting", "type":"portforwarded" }
2018-01-06T04:11:53.835080+02:00 di=qfImQyNXvc notice CommMgr: { "msgid":"cloudConnectivity", "state":"failed", "type":"portforwarded" }
2018-01-06T08:13:10.735871+02:00 di=qfImQyNXvc notice CommMgr: { "msgid":"cloudConnectivity", "state":"connecting", "type":"portforwarded" }
2018-01-06T08:13:14.214955+02:00 di=qfImQyNXvc notice CommMgr: { "msgid":"cloudConnectivity", "state":"failed", "type":"portforwarded" }

Here is the result of top comand

top - 16:19:07 up 16:11,  1 user,  load average: 4.57, 4.80, 5.14
Tasks:  82 total,   1 running,  81 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.3 us,  2.8 sy, 21.8 ni, 37.0 id, 35.9 wa,  0.0 hi,  2.1 si,  0.0 st
KiB Mem:    232320 total,   184064 used,    48256 free,     2304 buffers
KiB Swap:   500672 total,   108416 used,   392256 free,    22016 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
 6851 root      20   0 45376  12m 2304 S   8.7  5.6  81:02.23 wdmcserver
11514 root      20   0     0    0    0 S   1.6  0.0   0:07.81 kworker/1:1
10277 root      20   0     0    0    0 S   0.6  0.0   0:19.14 kworker/0:0
14901 root      20   0  4544 2496 1408 R   0.6  1.1   0:00.25 top
  293 root      20   0     0    0    0 D   0.3  0.0   3:55.52 kswapd0
 2473 root      20   0     0    0    0 D   0.3  0.0   2:49.80 pfe_ctrl_timer
 5889 root      20   0     0    0    0 S   0.3  0.0   0:07.51 knetatop
 6769 root      20   0 95808 2368 1280 S   0.3  1.0   3:40.10 upnp_nas_device
 6995 root      20   0 30144 3136 1472 S   0.3  1.3   9:13.77 wdnotifier
 8116 root      20   0     0    0    0 S   0.3  0.0   0:01.46 flush-8:0
10341 root      20   0 13824 1728 1088 S   0.3  0.7   0:01.21 sshd
    1 root      20   0  3264  896  640 S   0.0  0.4   0:33.28 init
    2 root      20   0     0    0    0 S   0.0  0.0   0:00.02 kthreadd
    3 root      20   0     0    0    0 D   0.0  0.0   0:00.00 cpu1_hotplug_th
    4 root      20   0     0    0    0 S   0.0  0.0   0:15.77 ksoftirqd/0
    7 root      rt   0     0    0    0 S   0.0  0.0   0:00.00 migration/0
    8 root      rt   0     0    0    0 S   0.0  0.0   0:00.00 migration/1
    9 root      20   0     0    0    0 S   0.0  0.0   3:53.20 kworker/1:0
   10 root      20   0     0    0    0 S   0.0  0.0   0:06.31 ksoftirqd/1
   11 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 khelper
   12 root      20   0     0    0    0 S   0.0  0.0   0:00.00 kworker/u:1
  230 root      20   0     0    0    0 S   0.0  0.0   0:00.32 sync_supers
  232 root      20   0     0    0    0 S   0.0  0.0   0:00.01 bdi-default
  234 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 kblockd
  240 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 ata_sff
  251 root      20   0     0    0    0 S   0.0  0.0   0:00.02 khubd
  257 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 md
  280 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 rpciod
  294 root      20   0     0    0    0 S   0.0  0.0   0:00.00 fsnotify_mark
  295 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 nfsiod
  296 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 crypto
  334 root      20   0     0    0    0 S   0.0  0.0   0:00.00 scsi_eh_0
  337 root      20   0     0    0    0 S   0.0  0.0   0:00.00 scsi_eh_1
  340 root      20   0     0    0    0 S   0.0  0.0   0:00.07 kworker/u:2
  351 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 comcerto_spi.1
  353 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 comcerto_spi.0
  402 root      -2   0     0    0    0 D   0.0  0.0   0:36.87 btn_t
  412 root      -2   0     0    0    0 S   0.0  0.0   0:00.00 a3gblink_t
  433 root      20   0     0    0    0 S   0.0  0.0   0:00.76 md1_raid1
  435 root      20   0     0    0    0 S   0.0  0.0   0:00.32 kjournald
 2065 root      20   0  4480  704  704 S   0.0  0.3   0:00.39 udevd
 2528 root      20   0  4416  704  704 S   0.0  0.3   0:00.07 udevd
 2529 root      20   0  4416  704  704 S   0.0  0.3   0:00.00 udevd
 4396 root      20   0     0    0    0 S   0.0  0.0   0:01.78 jbd2/sda4-8
 4397 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 ext4-dio-unwrit
 5959 root      20   0  8576  768  768 S   0.0  0.3   0:00.01 sshd
 6051 root      39  19  3584  960  960 S   0.0  0.4   0:16.55 monitorio.sh
 6210 root      20   0     0    0    0 S   0.0  0.0   0:00.00 lockd
 6211 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 6212 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 6213 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 6214 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 6215 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 6216 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 6217 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 6218 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd

Altitude · November 13, 2024, 5:13pm

November 16th 2024, I just had this very same issue happen overnight. My cloud is only accessible by ip address and no longer accessible by name. I did see the response about resetting the router and I will try that in a minute.

Bennor · November 14, 2024, 12:13am

@Altitude, if you experienced the issue when using Windows 11 24H2 see some of the suggestions in the following recent subforum post:

Recent Microsoft updates to Windows once again appear to have cause issues with NAS access.

Topic		Replies	Views
MyCloud Dashboard not accessible My Cloud	1	403	June 7, 2020
MyCloud issues My Cloud	6	3852	April 11, 2014
Cloud access - no access My Cloud EX2	3	1408	July 25, 2016
WD MyCloud 2TB - access problems after name change My Cloud	2	601	March 23, 2017
Can't access MyCloud device My Cloud	2	904	March 13, 2017

After more than 2 years, can't access MyCloud by it's name, only by IP

Related topics