WD Sync does not work on my 2nd computer

I have a WD My Cloud Mirror at home and installed WD Sync software on my 1st computer which a laptop PC in office. I selected “sign in” with my account when installed the WD Sync, it works fine on my office laptop.

Now I tried to install WD Sync on my 2nd computer which is a desktop PC at home, in the same LAN with MCM. Since the two devices are in the same LAN, I didn’t select “sign in” but just selected the device shown on the screen. The WD Sync was installed successful on my desktop PC.

Here is my problem:

  1. I placed some files in the My Cloud folder of my 1st computer
  2. The files were synchronized in the folder on My Cloud Mirror
  3. Opened the My Cloud folder of my 2nd computer, the files were not synchronized
  4. Tried to placed some files in the My Cloud folder of my 2nd computer, the files were not synchronized in the folder of MCM either
  5. Checked the WD Sync status on my 2nd computer, it shows “No internet connection”
  6. Opened the MCM dashboard, confirmed the cloud access was active on my 2nd computer

Hello,

Please check name resolution to the following WD servers from the 2nd PC

nslookup api.wd2go.com
nslookup files.mycloud.com

It shows “DNS request timed out”

Hello,

This means that from your location, you are unable to resolve the domain names required by WD Sync.
Here are the resources

nslookup api.wd2go.com

Non-authoritative answer:
Name: CORE-CSLoadBalance-179GSFINONZMG-751562920.us-west-2.elb.amazonaws.com
Addresses: 54.148.87.136
35.164.76.238
54.187.208.209
35.161.237.65
54.68.29.140
35.164.110.143
52.34.203.255
52.36.12.88
Aliases: api.wd2go.com

nslookup files.mycloud.com

Non-authoritative answer:
Name: webfiles-wfloadbal-k5vvr6pgpk5d-19794949.us-west-2.elb.amazonaws.com
Addresses: 52.26.245.61
52.38.143.183
Aliases: files.mycloud.com
webfiles21.mycloud.com

Hello,

Today I tried to check the name resolution again, looks like it returned the expected information, but I still couldn’t sync my 2nd computer - “no internet connection detected”.

Here it is

Non-authoritative answer:
Name: CORE-CSLoadBalance-179GSFINONZMG-751562920.us-west-2.elb.amazonaws.com
Addresses: 54.68.29.140
35.164.110.143
54.187.208.209
35.161.237.65
52.34.203.255
52.36.12.88
54.148.87.136
35.163.28.10
Aliases: api.wd2go.com

Non-authoritative answer:
Name: webfiles-wfloadbal-k5vvr6pgpk5d-19794949.us-west-2.elb.amazonaws.com
Addresses: 52.38.143.183
52.26.245.61
Aliases: files.mycloud.com
webfiles21.mycloud.com

SSL

  1. Ensure that SSL is checked under WD Sync Settings -> General Options

Your My Cloud Device (Unique ID)

  1. Open your mycloud device in a web browser

  2. Add https:// in front of the IP to expose the cert and unique domain name

  3. The screen should show two device names.
    These are the unique domain names of your MyCloud. (DO NOT POST IN PUBLIC FORUM)

    LAN device4111111-aaaaaaaa-local.wd2go.com
    WAN device4111111-aaaaaaaa.wd2go.com

You should be able to lookup and tracert the WAN name from your PC #2 and from
an external web resource like http://mxtoolbox.com/DNSLookup.aspx

If the WAN name doesn’t not resolve, then this could trigger the “no internet connection” issue.

I tried your method and got my WAN name.

Does it mean that WAN name is not resolved?

http wd2go.com The remote name could not be resolved: ‘wd2go.com’ (http://wd2go.com)
dmarc wd2go.com Record Missing
dns wd2go.com Primary Name Server Not Listed At Parent

How to resolve it? Thanks!

Now, the interesting thing is -

I connected my 1st PC in the same LAN, uninstalled WD Sync on my 1st PC and then reinstalled it. Because I normally use my 1st PC remotely, when I installed, I selected “sign in” with my account information.

The error message “cannot connect to the remote server”.

I checked and confirmed the domain names can be resolved on my 1st PC (same as the 2nd one).

Could it be the problem related to the router? I closed the anti-virus software and Windows firewall, the problem still exists.

If the Unique ID does not resolve, then YES you could have an internal or external DNS problem or an issue of VPN interference. Cannot connect to remote server could also mean a name resolution issue.