Update on 14 of Aug. The issue has been gone for 2 days....

[XHP]

Update on 14 of Aug.  The issue has been gone for 2 days.  Seems like a IP conflict / confusion - I saw 15 IP conflict warnings in NAS's log. Probably on first day NAS "struggled" with one another device for the fixed IP 192.168.0.10 which was set up in NAS, sometimes NAS won while sometimes the other device won - that probably is the reason why the issue came and went.  After more hours, the other device might give up and got a new IP by Blue Curve's DHCP.

I will update otherwise.  Thanks again @mdk 

[mdk]

@XHP -- I thought that a "non-bridged" BlueCurve cable-modem would supply IP-addresses in the "10.0.0.xxx" range in response to DHCP-requests, not IP-addresses in the "192.168.0.yyy" range. So, if the NAS sends a DHCP-request, it should receive a "10.0.0.xxx" IP-address, namely in the same range as other wired/wireless devices connected to the BlueCurve.

Logon to the BlueCurve, and list the "connected" devices -- both their names and their IP-addresses.