Changed switch and now My Cloud can't connect

I changed the switch and now i can’t access WD drive
The led is blue and it gets IP from the router, but the network doesn’t detect it
I tried to reset the drive and still nothing
No ping, no web access, the software detection of WD doesn’t find it
What the problem is?

You changed “the switch” from what to what? Is the My Cloud configured for a Static IP Address?

If the My Cloud is receiving an IP address from the network DHCP server (typically in the broadband router/gateway) then other network devices should be able to access the My Cloud via it’s IP address unless you have put the My Cloud behind a second firewall.

Couple of suggestions. power down all network devices including the My Cloud, switches, and broadband router/gateway. Then power on the broadband router/gateway first. Wait at least five minutes. Then power on the My Cloud and wait till it has a solid blue LED on the front. Next power on one computer and wait till it finishes booting to its operating system. Then check for My Cloud access using that one computer. If you can access the My Cloud then power on the rest of the network devices/computers and once finished recheck My Cloud access on each computer/device on the network.

I changed the switch to a gigabit one. no firewalls, no configurations.
The WD had a static IP. I wasn’t able to ping it or see it in network devices. Turned off all the devices but nothing.
So i reset it to factory settings. Plugged it on the net and router gave IP, i saw the dhcp list. But nothing!!!

Is the computer you are using to test connectivity to the My Cloud on the same IP subnet as the My Cloud?

For example if the My Cloud static IP address is 192.168.1.2, is the computer’s IP address in the same IP address subnet range of 192.168.1.x?

What operating system (Windows, Mac, other) are you using on the computer?

Is the computer connected to the same switch as the My Cloud? If not is the computer connecting to the local network via WiFi?

Yes same subnet and switch. The computer runs win7

What switch are you using? Full name please.
Is the switch managable? If yes, have you configured it?

Does the switch port, where the My Cloud is connected to, shows at least the connection LED? Is the activity LED of this port flickering?

Have you checked the cabling? Is it plugged in well on both sides?

What DHCP-Address was given to the My Cloud?

D-Link DGS 1024D
not manageble

I connected the WD on the switch and on the router. the IP that gets is 192.168.1.104
and yes the led on the port flickers

Thanks for reply.

flickering LED means traffic, so the My Cloud seems to send data pakets.

Can you access the My Cloud web interface on http://192.168.1.104 ?

no i tried that too
not even ping it

What IP settings are on your PC?

192.168.1.102

Is it possible to update the firmware somehow?

a bit more please

IP-Address: 192.168.1.102
Subnet Mask:
Standard Gateway:
Primary DNS Server:

Why firmware update? This seems not related to any firmware issue; it seems related to some misconfiguration in ip adresses or network.

Not all errors are related to firmware, sometimes it could be a simple Error 40.

If you cannot reach the My Cloud there is no way to manually update the firmware. You first must figure out why you cannot access the My Cloud from the computer.

In addition to the suggestions made above, have you tried disabling the Firewall on the computer (if it has one)?

If using Windows, ensure Use NETBIOS over TCP/IP is enabled, and ensure the network setting is configured for Private and not Public. If configured for Public you may not be able to access certain devices on the local network like the My Cloud.

Just to try to clarify your setup…

You have a modem/router of some sort.
You have a D-Link DGS 1024D gigabit switch connected to the router.
You have your PC connected to the switch (or is it connected to the router?).
You have your MyCloud connected to the switch.

Is that correct?

You can connect to the router from your PC (via the switch), and see that it has assigned an IP address to the MyCloud. Is that correct? Or do you connect your PC direct to the router?

What I’m trying to find out is whether you have any other devices successfully passing traffic through the switch, or whether you just have a defective switch…

I’m not sure I follow that. Did you mean that you have connected the MyCloud to both the router and to the switch, and you observe that it is assigned the same IP address in both cases?

If you connect everything to your router (PC and MyCloud), can you access the MyCloud from the PC?

subnet mask 255.255.255.0
gateway 192.168.1.1
DNS 62.169.194.47

not public, and yes netbios over tcp/ip in enabled
i disabled the firewall on the computer but still nothing, not even ping

router → switch → devices

i login to routers’ web interface and see the dhcp pool

(i can ping the router and other devices but not MyCloud)

Yes i connected WD to both the routrt and the switch and same results

The DNS setting is a serious problem. Your Primary DNS Server has to be the internal DNS aka your router, 192.168.1.1. Yet all DNS lookup requests are forwarded out of your internal network to a DNS server which does not know the devices in your internal network.

You have to set
Primary DNS = 192.168.1.1
Secondary DNS = 62.169.194.47

But Second DNS is not neccessary as the forowarding to the provider DNS would be done by your router by default in case of need.

After this, your My Cloud can be reached by its hostname.
Remember that Windows is still using NetBIOS over IP, which you stated to be activated.

If you point to the wrong DNS (which you do), then all DNS request into your own network cannot be answered.

But this I yet don’t understand:

You should be able to ping 192.168.1.104. What is the result of the ping? Dropped packed?
Have you changed any setting of your My Cloud network configuration or is it simply DHCP?
Maybe try another ethernet cable and re-test the ping. You said, the traffic LED on the switch port for My Cloud is flickering, so there is traffic given. But maybe we have a broken ethernet cable (happens more often than you may think).