mzn50 Posted July 5, 2013 Share Posted July 5, 2013 Hello all.. I recently changed ISP providers and got a static IP addy for access to my ISY remotely I used to see a local IP address for the ISY of 192.168.1.102 The ISY ALWAYS booted up with that address.. with the new ISY... I now see 192.168.3.100 since the move to the new ISP. I have rebooted the ISY and confirmed it came up again with the 100 address .. Question : What dictates the local IP address and will the ISY ALWAYS come up with the same local IP moving forward ? thank you !!! Matt Link to comment
fuentesa Posted July 5, 2013 Share Posted July 5, 2013 It seems that you also change your router. Your ISY is probably configured to use DHCP address instead of a static one. As long as you don't disconnect your iSY for too long; it will came with the same address. However if you want to assure that it always have the same IP; you need to configure a static IP in your ISY. Just go to network settings and select static IP. It is important that the IP that you assign be in the same subnet as your router. It seems that your old router was using 192.168.1.x and the new one is using 192.168.3.x. Link to comment
mzn50 Posted July 5, 2013 Author Share Posted July 5, 2013 fuentesa.. you are 100% correct .. Router is also doing the DHCP .. before the modem from previous ISP did it.. I did see that option.. was hesitant to change it.. will do so now.. this location is in the Gatineau Mountains of Quebec... and power outages are common.. even though I have a UPS plugged in to support the ISY and modem..router.. sometimes power goes out for a day or more... setting the static IP on the ISY will hopefully avoid it rebooting up differently.. thanks ! Link to comment
mzn50 Posted July 5, 2013 Author Share Posted July 5, 2013 configed and set.. thanks only anomaly I see now is that the SET TIME NTP Server get a DNS error ? which means I can no longer auto time set .. I tried resetting to another server but no luck.. thanks ! Matt Link to comment
mzn50 Posted July 5, 2013 Author Share Posted July 5, 2013 figured it out... wrong DNS addy.. needs the LAN.. not internet Link to comment
arw01 Posted July 5, 2013 Share Posted July 5, 2013 I recently had issues with using the LAN dns vs going out to google 8.8.8.8. There were massive DNS failures in the logs with mobilinc and the lan DNS. After the change there have been no more dns failures. Might be something to check into a few times on the error log in the next few days. Alan Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.