Issue with Static IP?
Posted: Wed Dec 03, 2014 1:20 am
Today the windstream router got a new ip address as it does several times a week. However this time the router stopped all traffic. I discovered this because my dotnet app monitoring the envisalink and blueiris failed to send a status alert to my phone (Motion on one of the cameras).
Disabling the alarm ( vista20P ) didn't yield a message from eyez-on either. I know their is a delay from the actual loss of communications until a message is sent. Logging into the eyez-on site showed offline and last communications was several hours earlier.
After rebooting the windstream router I got a supervision fault from eyez-on. Very late but correct.
On the Network page of the envisalink it showed 'OFFLINE" and the Envisalerts Server IP as 192.168.254.254(E)
Don't know what the (E) means but that's the IP of Gateway setting and of course the router.
Rebooting the windstream router, the envisalinkvia via the web page, the Vista20p panel power, disconnecting my app from the TPI session didn't help.
After reading about another user on the fourm un-checking the 'Make Network Settings Static?' check box fixing his issue I tried that.
The envisalink connected to the Envisalerts Server within a few seconds. Then I made it static again by checking the box and setting the last digit of the IP. All is well now.
Is their a know issue with setting the envisalink to a static IP? The whole system has been very stable to months.
Disabling the alarm ( vista20P ) didn't yield a message from eyez-on either. I know their is a delay from the actual loss of communications until a message is sent. Logging into the eyez-on site showed offline and last communications was several hours earlier.
After rebooting the windstream router I got a supervision fault from eyez-on. Very late but correct.
On the Network page of the envisalink it showed 'OFFLINE" and the Envisalerts Server IP as 192.168.254.254(E)
Don't know what the (E) means but that's the IP of Gateway setting and of course the router.
Rebooting the windstream router, the envisalinkvia via the web page, the Vista20p panel power, disconnecting my app from the TPI session didn't help.
After reading about another user on the fourm un-checking the 'Make Network Settings Static?' check box fixing his issue I tried that.
The envisalink connected to the Envisalerts Server within a few seconds. Then I made it static again by checking the box and setting the last digit of the IP. All is well now.
Is their a know issue with setting the envisalink to a static IP? The whole system has been very stable to months.