D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-345 => Topic started by: dnsguy on September 15, 2012, 02:28:41 PM
-
Hi,
I bought a new router and switched my DNS-345 over. The mycloud relay service is no longer active. Has anyone had this problem. What do I need to do to activate the relay service?
-
First question, did you set up your new router exactly the same as your old one?
If something was working and now isn't and you have changed a component in the chain then the first place to look to start solving the problem is the changed component.
-
First question, did you set up your new router exactly the same as your old one?
If something was working and now isn't and you have changed a component in the chain then the first place to look to start solving the problem is the changed component.
The only thing I changed was the IP from 192.168.100.10 to 192.168.0.10
-
Have you changed everything on your network from the 192.168.100.xxx subnet to the 192.168.0.xxx subnet?
Those getting an IP address via DHCP will do so automatically but anything you hard wired the old address into will require that you manually change it.
-
Have you changed everything on your network from the 192.168.100.xxx subnet to the 192.168.0.xxx subnet?
Those getting an IP address via DHCP will do so automatically but anything you hard wired the old address into will require that you manually change it.
Only the NAS has a static ip. Everything else is DHCP.
-
Then the thing to look for is how you accessed the NAS before, in other words did you access it by name or IP?
If it was by IP then have you changed that old IP to the new one?
-
Then the thing to look for is how you accessed the NAS before, in other words did you access it by name or IP?
If it was by IP then have you changed that old IP to the new one?
I can get to it from internally with the IP and port number. The problem is with the cloud relay. It keeps going inactive. I can't use my cloud url name. i.e. membername.mydlinkcloud.com It won't find it because my nas is not reporting to the cloud server what my external facing IP is.