- Joined
- 11 Mar 2019
- Messages
- 2
- Reaction score
- 0
- Country
Hi, here my problem, I have had a ComIP working OK for years now. After various Network provider upgrades (BT) It has left me with a weird problem. The panel throws up the odd Com2 fault. After a short period I am able to connect with Wintex ONLY through a third party ISP (I have BT and Virgin connected to my house) The Texecom Premier is attached to my BT service router on 192.168.1.210 port 10001. It is configured via DNYDNS. 90% of the time I can connect with the BT service locally through DNYDNS and I can also ping the ComIP just fine. When the Com2 fault happens I loose the connectivity to the unit via BT and have to switch to the Virgin ISP of 4G. The BT routers has the firewall configured properly (i think) and does work for long periods. It used to get Com2 faults when I had a Com2400 connected to Com2 and the ComIP was on Com1. I then dumped the Com2400, switched the ComIP onto Com2 and installed a third party Arduino based GSM dialer that is completely seperate from any Comms. (I use this in 1Pmobile and works great). Any ideas.
PS. If I change the Host address of the Panel to 192.168.1.210 (from DNYDNS host address which in e.g. something.dnsnet.org I can access the panel with my BT service. Its like randomly the system objects to DNYDNS address.
PS. If I change the Host address of the Panel to 192.168.1.210 (from DNYDNS host address which in e.g. something.dnsnet.org I can access the panel with my BT service. Its like randomly the system objects to DNYDNS address.