Texecom Comip - Connection With Control Panel 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]

 

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),

 

 

The above is basically 'no ICMP response' from any device at that address - so the device isn't working as expected.  If the device responded, it would give number of bytes and a response time.

 

C:\k2>ping 10.226.111.2

Pinging 10.226.111.2 with 32 bytes of data:

Reply from 10.226.111.2: bytes=32 time<1ms TTL=128

Reply from 10.226.111.2: bytes=32 time<1ms TTL=128

Reply from 10.226.111.2: bytes=32 time<1ms TTL=128

Reply from 10.226.111.2: bytes=32 time<1ms TTL=128

Ping statistics for 10.226.111.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

[zurrieq]

Maybe the panel / the comip has another IP address? I got the 192.168.1.66 from the modem /router which was assigned via DHCP and then I forced it to not change.

 

Is there a way I can check the IP address from the  keypad?

Edited December 6, 2015 by zurrieq

[sixwheeledbeast]

Maybe the panel / the comip has another IP address? I got the 192.168.1.66 from the modem /router which was assigned via DHCP and then I forced it to not change.

 

Is there a way I can check the IP address from the  keypad?

 

You should use a static IP.

It must be set in the control panel. UDL/Digi Options.

[zurrieq]

You should use a static IP.

It must be set in the control panel. UDL/Digi Options.

 

Thanks - that did the trick - was in fact on .50