28.08.2018, 21:24 (This post was last modified: 29.08.2018, 06:39 by Erwin van der Zwart.)
Hi,
Just like i told you in previous post, when you can connect locally there is nothing wrong with the device settings and / or hardware.
The router handles your forwarding from the WAN to the LAN so there you must look for the solution. The fact that other ports are working has nothing to do with this.
You must search for the solution in the router..
It can be that the forwarding is not working because the controller has a static IP and is not known in your router’s DHCP list, i have seen that before, anyway your solution must be searched in the router and not in the controller.
Just like i told you in previous post, when you can connect locally there is nothing wrong with the device settings and / or hardware.
The router handles your forwarding from the WAN to the LAN so there you must look for the solution. The fact that other ports are working has nothing to do with this.
You must search for the solution in the router..
It can be that the forwarding is not working because the controller has a static IP and is not known in your router’s DHCP list, i have seen that before, anyway your solution must be searched in the router and not in the controller.
edit:
Seems to work at this moment:
BR,
Erwin
Hi Erwin
a last question for understanding. You tried to connect to my HomeLynk and you have managed?
VPN is good also to bypass restrictions of routers in-between of client-LM. Probably your ISP's router or your ISP's ISP () is blocking or not processing correctly necessary ports. And when Erwin is connecting - he is on another ISP network thus it might work fine.
but I had port 3671 to forward to HomeLynk visualization. And it worked fine. Now I use again external port 3671 to 80 for Visulation. do you mean that probably my Router blocks internal port?
you can traceroute from your remote location and see how many hops are in-between you and LogicMachine. So there are different servers/providers between you and LogicMachine. One of them might affect the communication.
but I had port 3671 to forward to HomeLynk visualization. And it worked fine. Now I use again external port 3671 to 80 for Visulation. do you mean that probably my Router blocks internal port?
BR
Why do you forward 3671 to 80?? This is wrong! 80 is for webbased visu (html) and 3671 is for KNX IP protocol. Please read some articles about this..
29.08.2018, 20:53 (This post was last modified: 30.08.2018, 05:00 by balatis.)
γεια
αν θέλετε να χρησιμοποιήσετε dyndns τότε πρέπει να χρησιμοποιήσετε το donaim http://example.dyndns.org
θα ανεβάζουν κάποιες φωτογραφίες από τις ρυθμίσεις μου
ets σύνδεση με ddns
εάν δεν λειτουργούν δοκιμάστε τη θύρα 80 από το ISP σας
but I had port 3671 to forward to HomeLynk visualization. And it worked fine. Now I use again external port 3671 to 80 for Visulation. do you mean that probably my Router blocks internal port?
BR
Why do you forward 3671 to 80?? This is wrong! 80 is for webbased visu (html) and 3671 is for KNX IP protocol. Please read some articles about this..
BR,
Erwin
Dear Edgar,
I think that is a mistake from my side. I forward 3668 to 80 for visualization and 3671 to 3671 for KNX protocol. My main question was that I have tried from 2 different ISP's from 2 friends houses and I had the same problem. All IPS's have a problem? I think it is too strange.
Also, I have tracerouted and I send the picture. Sorry, but I can't understand too much. Any of these 30 hops cause the problem? And how can find which?
Tracert was just to show in general that there are lots of farms inbeween and you cannot change them. If it's not working through NAT, I recommend to enable VPN server on your router.
(30.08.2018, 08:57)edgars Wrote: Tracert was just to show in general that that there are lots of farms inbeween and you cannot change them. If it's not working through NAT, I recommend to enable VPN server on your router.
Ok Edgar.
Thanks a lot for your help.
And something last. Sometimes HomeLynk looses the communication with KNX. I don't know why.
If I unplug the bus terminal and plug again to HomeLynk is ok, but this is a problem for the customer.