Texecom ComIP - Connection Problem

[zurrieq]

I have a Premier 48 (not Elite) with the ComIP that has been running for a few years. I tried to connect to Wintex but got a connection problem so I started some troubleshooting.

1) In the router modem, I found that the ComIP was not being assigned an IP. Eventually restarting the panel solved the problem and now it has an ip address 192.168.1.66

2) If I ping 192.168.1.66 it seems fine
Pinging 192.168.1.66 with 32 bytes of data:
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.

Ping statistics for 192.168.1.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

3) Checked panel fuses (did not replace them) & they look fine

4) Everything was setup on Com Port 1 so I switched of Panel and moved this to Port 2, tried with baud rate 19200 and 38400

5) typing 192.168.1.66 in browser gives 'ERR_CONNECTION_TIMED_OUT'

5) Checked the modem / router and I think I successfully allowed TCP/UDP on port 10001 (the modem changed a few months ago and I don't remember if I ever accessed the panel with the new modem)
Port Range 10001 - 10001
Translate To 10001 - 10001
Trigger Port 10001


Any help is appreciated. In the meantime I'm not sure if it's relevant but the Tx1 led on the panel is showing as red. I'm also attaching a photo of the panel (maybe it helps)... I have since moved back to port 1 as I was getting an error on the keypad after moving to port 2. Anything I'm missing?

 

[GalaxyGuy]

As per my reply on the other forum, the module is not responding to your ping. Check that it hasn't picked up a different address via DHCP from your router. The Texecom lantronix modules sometimes do this if they don't pick up the information from the panel to reconfigure the address Ie. they fall back to DHCP.

It's strange that this has happened if the COM-IP hasn't been rebooted in years. Nothing to say that a big power spike hasn't caused a watchdog reset and internal COM-IP reboot though...

 

[lynchnigel]

Networks hey
check your router is on the same subnet ie starts with 192.168.1.XX
If thats the case, I'm not sure they do DHCP assignments anyway regardless - it can pick up another IP address at any stage (depending on the router lease time which this might have done) so you need to assign it a static IP address on the Alarm panel
You could assign it that one it had 192.168.1.66
You will need the gateway (which should be the router IP address)
and maybe the subnet which might be 255.255.255.0

 

[Lectrician]

Networks hey
check your router is on the same subnet ie starts with 192.168.1.XX
If thats the case, I'm not sure they do DHCP assignments anyway regardless - it can pick up another IP address at any stage (depending on the router lease time which this might have done) so you need to assign it a static IP address on the Alarm panel
You could assign it that one it had 192.168.1.66
You will need the gateway (which should be the router IP address)
and maybe the subnet which might be 255.255.255.0

I wouldn't assign a static IP of .66, it's obviously in the DHCP pool, so could be dished out to something else. If you want to use it, you need to reserve it in the router to prevent it being used. Best to use an IP outside the DHCP range. BT routers typically start the DHCP range at .66 these days.

 

[lynchnigel]

Or assign it a more suitable range