Comfort Automation/ Security System Forums
Problem with remote connection with comfort client - Printable Version

+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Software Applications (https://www.comfortforums.com/forum-4.html)
+--- Forum: ComfortClient (https://www.comfortforums.com/forum-65.html)
+--- Thread: Problem with remote connection with comfort client (/thread-2725.html)

Pages: 1 2

- koutsogiannis - 02-09-2012

I try to connect remotely to the comfort with client. The error message I get is that the photo upload. The version I have is the past. In earlier versions remotely connect without any problems. The Wizards Comfort connect normally.

- Ingo - 02-09-2012

Does it work on the local LAN?

Perhaps when you try to connect remotely you forgot to open UDP port 65535 on your router. That is the port that the Tibbo Module uses for connection information.


Newer Client versions check the Tibbo Module before it makes a connection.

Regards,

Ingo



- koutsogiannis - 02-09-2012

I opened the door, and 65535, but not connect. Version 1.20.2.35 is linked properly. What could be the problem?

- ninotorres - 02-09-2012

I have the same problem.

- juwi_uk - 02-09-2012

So as Ingo says you need whatever TCP port you are connecting on (1001 typically) and UDP port 65535.

The timeout for the UDP response is hardcoded at 3 seconds so it looks like you didnt get a reponse within that time. Does it repeatedly fail or just sometimes?

I\'ll make the Tibbo checking an option in the next build so you can turn off.

Julian

- juwi_uk - 02-09-2012

Hi,

Replace the current ComfortClient.exe with this patched version where I\'ve disabled the Tibbo checking and let me know if it works.

http://www.futurehomesoftware.co.uk/releases/ComfortClient-3.1.2.21-NoTibboCheck.zip

Regards

Julian

- koutsogiannis - 02-09-2012

It works ok. Τhank you very much Julian.

- juwi_uk - 02-09-2012

So it\'s either UDP port 65535 being blocked then or the link being slow and you not getting a response back from the Tibbo within 3 seconds. I\'ll make more configurable next release for these scenarios.

J

- ninotorres - 02-12-2012

The patched version worked perfectly.
And yes I don\'t have the mentioned UDP port opened, so that\'s why it fails.

My question now is, what does that checking for Tibo module adds? I was fine with only one well defined port opened in my firewall.

Thanks,
Nino

- juwi_uk - 02-12-2012

Hi

I added this functionality because the tibbo module can only accept one connection at a time. So via this tibbo management port i can check if the ucm is already connected to something (eg comfigurator, iphone app, Wizcomfort etc) and warn the user appropriately either to gracefully concede to the existing connection or force it to close so you can grab it! I found this useful for eth02 modules though less important with later Eth02 ones as they now auto disconnect on logoff.

J