My Cloud Home keeps getting new IP address every 16 minutes

All transfers get disrupted of course. DHCP lease time is 3 days… Also all the network activity is slow. This product is real garbage. WD should release “poweruser” firmware for it or something with proper SMB and stuff. Thinking about ripping the drive out and placing it in Syngery box. I have files under normal and public folders. Will ALL the data be accessible if i place the drive in another NORMAL NAS box?

What router, make, model and firmware are you using?

https://support.wdc.com/knowledgebase/answer.aspx?ID=19504&lang=en

I’m using a Linux gateway PC (2.6 Kernel). DHCP Reservation is properly configured:
host storage {
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed-address 192.168.xx.xx;
ddns-hostname “storage”;
option host-name “storage”;
option domain-name “xxxxxxxx.xxx”;
}
My Cloud Home still requests a new address. I think it’s an issue with the drive, not the DHCPD

Log:
May 3 09:51:46 gw dhcpd: Added new forward map from storage.xxxxxx.xxx to 192.168.xx.xx
May 3 10:23:06 gw dhcpd: Added new forward map from storage.xxxxxx.xxx to 192.168.xx.xx
May 3 10:38:45 gw dhcpd: Added new forward map from storage.xxxxxx.xxx to 192.168.xx.xx
May 3 10:54:25 gw dhcpd: Added new forward map from storage.xxxxxx.xxx to 192.168.xx.xx

still 16 minutes…

May 3 10:23:06 gw dhcpd: DHCPREQUEST for 192.168.xx.xx from xx:xx:xx:xx:xx:xx via eth1
May 3 10:38:45 gw dhcpd: DHCPREQUEST for 192.168.xx.xx from xx:xx:xx:xx:xx:xx via eth1
May 3 10:54:25 gw dhcpd: DHCPREQUEST for 192.168.xx.xx from xx:xx:xx:xx:xx:xx via eth1
May 3 11:10:05 gw dhcpd: DHCPREQUEST for 192.168.xx.xx from xx:xx:xx:xx:xx:xx via eth1
May 3 11:25:45 gw dhcpd: DHCPREQUEST for 192.168.xx.xx from xx:xx:xx:xx:xx:xx via eth1

and so on…

@ApA I’ve sent you a PM for more information

Ok, thank you, will check.

@ApA engineering had a look at your issue. It appears that the LAN side interface of the linux server router is set to not respond to pings, so the MCH is dropping connectivity. The configuration needs to be modified so the LAN side will respond to pings.