Cannot connect to Envisalink server

[jwshome]

Hi,

I have an EVL-4 board that is working properly on my local network - it connects properly to my alarm system and to my home automation system. The EVL shows that it is not connected to the Envisaslink server, although it knows the IP address of the server (198.61.170.85). I have a few questions:

1. I changed my home network IP addresses to 192.168.0.xxx (from 192.168.86.xxx) - could that have caused the disconnect?

2. Every 12 hours my EVL gives a series of errors in the Homeseer log, saying the remote connection has been broken. The internet connection on the computer, though, is not broken (I monitor it every five seconds and the internet remains up during the time the EVL board cannot communicate)

3. My firmware is version 130 - I'm wondering if I need new firmware? Other than the disconnect every 12 hours, the network is stable and the EVL remains connected.

Any thoughts on fixing the error, and/or providing me with updated firmware?

Thanks in advance for your help.

[Crikey]

Hi,

I have an EVL-4 board that is working properly on my local network - it connects properly to my alarm system and to my home automation system. The EVL shows that it is not connected to the Envisaslink server, although it knows the IP address of the server (198.61.170.85). I have a few questions:

Have you tried ping'ing 198.61.170.85 from a computer to see if it's even reachable from your LAN?

1. I changed my home network IP addresses to 192.168.0.xxx (from 192.168.86.xxx) - could that have caused the disconnect?

The only problem I had when I re-addressed my LAN, recently, was in the remote syslog server configuration. The basic communications functionality of our EVL4 was otherwise unaffected.

2. Every 12 hours my EVL gives a series of errors in the Homeseer log, saying the remote connection has been broken. The internet connection on the computer, though, is not broken (I monitor it every five seconds and the internet remains up during the time the EVL board cannot communicate)

You've already established that the EVL4 isn't talking to EyezOn's server, so this is no surprise.

3. My firmware is version 130 - I'm wondering if I need new firmware? Other than the disconnect every 12 hours, the network is stable and the EVL remains connected.

Ours is 01.02.130A. I have never experienced problems with the EVL4 communicating with the mothership.

Any thoughts on fixing the error...?

Since, presumably, it worked before you re-addressed your network, I suspect you did something wrong in that re-addressing. Got one of the network parameters wrong. E.g.: Wrong netmask on the router. Or neglected up update a firewall rule that used to take into account the old addressing.

[jwshome]

Crikey,

Thanks for helping problem-solve this. 198.61.170.85 is pingable from my network. I don't think I did the reconfiguration of the network wrong, since I have 82 devices on the LAN, and the other 81 are having no communications issues, and haven't for the past nine months. I did forget to open up the EVL ports (4120 to 4125, or something like that) originally, but I opened those up and rebooted the EVL and the device still cannot communicate with the Eyez-On server. And the EVL stayed connected to the Eyez-on Server for about 8 months after I switched network addressses - it started failing only about a month ago.

I think the "every 12 hours" is a clue to fixing the problem. What is triggering this, does anyone know? It's not the Homeseer plugin - the plugin author told me the plugin does not interact with the remote server.

[GrandWizard]

Your Module is firewalled somehow. Submit a tech support request from your Eyezon portal and we can help you further.

[jwshome]

I've determined from the log file (see below) that the problem is not related to the Eyez-On remote server. The communications break is occurring when the Homeseer plugin is unable to reach the EVL-4 device on the LAN. It tries seven times and is then able to reconnect. This exact pattern repeats itself every 12 hours.

I am running firmware version 01.02.130A, which I understand is the most recent version and fixed the "intermittent connection" errors that existed a few years ago, so that doesn't seem to be the source of the problem.

GrandWizard, I will submit a ticket from my Eyez-On portal as you suggested, and I will also reach out to the Homeseer plugin author (Spud) to see if he has any thoughts.

Here's the log file:

• Nov-25 04:32:06 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
  Nov-25 04:32:06 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  at EnvisaLinkAdemco.Communications.Reciever.Run()
  Nov-25 04:32:06 INFO Connection Lost, will try to reconnect in 10 seconds
  Nov-25 04:32:17 INFO Trying to reconnect to: 192.168.0.xxx:4025
  Nov-25 04:32:38 ERROR A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.0.xxx:4025
  Nov-25 04:32:40 INFO Trying to reconnect to: 192.168.0.xxx:4025
  Nov-25 04:32:45 INFO Reconnection OK
  Nov-25 04:32:45 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
  Nov-25 04:32:45 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  at EnvisaLinkAdemco.Communications.Reciever.Run()
  Nov-25 04:32:45 INFO Connection Lost, will try to reconnect in 10 seconds
  Nov-25 04:32:56 INFO Trying to reconnect to: 192.168.0.xxx:4025
  Nov-25 04:32:56 INFO Reconnection OK
  Nov-25 04:32:56 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
  Nov-25 04:32:56 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  at EnvisaLinkAdemco.Communications.Reciever.Run()
  Nov-25 04:32:56 INFO Connection Lost, will try to reconnect in 10 seconds
  Nov-25 04:33:07 INFO Trying to reconnect to: 192.168.0.xxx:4025
  Nov-25 04:33:07 INFO Reconnection OK
  Nov-25 04:33:07 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
  Nov-25 04:33:07 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  at EnvisaLinkAdemco.Communications.Reciever.Run()
  Nov-25 04:33:07 INFO Connection Lost, will try to reconnect in 10 seconds
  Nov-25 04:33:18 INFO Trying to reconnect to: 192.168.0.xxx:4025
  Nov-25 04:33:18 INFO Reconnection OK
  Nov-25 04:33:18 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
  Nov-25 04:33:18 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  at EnvisaLinkAdemco.Communications.Reciever.Run()
  Nov-25 04:33:18 INFO Connection Lost, will try to reconnect in 10 seconds
  Nov-25 04:33:29 INFO Trying to reconnect to: 192.168.0.xxx:4025
  Nov-25 04:33:29 INFO Reconnection OK
  Nov-25 04:33:29 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
  Nov-25 04:33:29 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  at EnvisaLinkAdemco.Communications.Reciever.Run()
  Nov-25 04:33:29 INFO Connection Lost, will try to reconnect in 10 seconds
  Nov-25 04:33:40 INFO Trying to reconnect to: 192.168.0.xxx:4025
  Nov-25 04:33:40 INFO Reconnection OK
  Nov-25 04:33:40 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
  Nov-25 04:33:40 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  at EnvisaLinkAdemco.Communications.Reciever.Run()
  Nov-25 04:33:40 INFO Connection Lost, will try to reconnect in 10 seconds
  Nov-25 04:33:51 INFO Trying to reconnect to: 192.168.0.xxx:4025
  Nov-25 04:33:51 INFO Reconnection OK
  Nov-25 04:33:51 DEBUG Received: Login:
  
  Nov-25 04:33:51 DEBUG Request: SendKeystrokeString xxxxxxxxxx
  Nov-25 04:33:51 DEBUG LoginInteraction
  Nov-25 04:33:51 DEBUG Received: OK
  
  Nov-25 04:33:51 INFO Password OK
  Nov-25 04:33:51 DEBUG LoginOK