Flexy 205 doesn't recognize a valid Internet Connection
The internet connection is the same as all the previous eWONs I've set up using V11 and earlier. Any idea why the Internet isn't recognized on the Flexy 205? I've tried two different ports as the WAN, and all I get is this in the event log.
-
@mitchell.hein
In the internet setup wizard, is it passing one step and not the other? So does it pass establishing WAN connection and fail on test internet connection?
0 -
Yes. It passes the WAN Connection, and fails the Internet connection. The weird part is that the 4005CD units never had this issue, and the Flexy 205 (with the V12.2s1 software) does.
0 -
@mitchell.hein
That is strange, does the unit still pass the Talk2M wizard? What if you set Google DNS, does that help with the 2nd internet test?
0 -
OK: here's what I have so far.
I used to set up eWON 4005CD and Flexy 201 units at my desk. The wizards had no problem accessing the internet via DHCP with the WAN cable I provided.
Yesterday, I tried to set up my first Flexy 205 using the exact same method. It showed the WAN connection was valid (green check), but the Internet connection failed (red X). The firmware was the newer style V12.2s1, so I had some trouble finding out if all my settings were correct, because everything is shuffled around and looks different.
No matter what I tried, I could NOT get the eWON to pass the test where it tried to see the talk2m server.
Our I.T. specialist had me move my entire setup into our server room, and he assigned me a static port on the other side of the company firewall. After I reconfigured the ETHERNET connection settings with his static address, I was able to pass the communication test. After that, the VPN setup using the activation code worked just fine, and it completed all tests.
Here's the strange part:
I took all my equipment back to my desk, and set it all back up. I connected (via the LAN) from my computer directly to the eWON and set it back up to DHCP. I then plugged it into the same old WAN cable I've always used, and it went online with eCatcher within a minute. I was able to successfully connect and access the eWON.
SO: why would the link be good enough for Online access through eCatcher using DHCP, but the wizard doesn't accept DHCP as good enough?
Possibility: Is the web address different in the wizard than it used to be in earlier firmware versions, where I need to add something new to our firewall white list?
0 -
Hi @mitchell.hein
Yes, the test endpoint did update in newer firmware revisions. Previously the unit reached out to as.pro.talk2m.com. As of firmware 12.2 the unit now tests: device.api.talk2m.com. That would explain the issues if your IT guy needs to whitelist addresses to test.
0 -
If device.api.talk2m.com wasn't whitelisted and our firewall blocked that particular access, would that cause the Internet Connection test to fail?
0 -
@mitchell.hein
Yes, that would as that is the domain used to test that as well.
0 -
I just attempted to configure a second device, and I still find that I cannot establish an Internet Connection in the eWON Connection Wizard, even though we have whitelisted *.talk2m.com in our firewall.
Are there any other addresses required, or special ports which we would need to insure are open for this function to work? We know it is a firewall issue, as we can configure the device by plugging it in on the other side of the firewall, but it is very time consuming to do it that way.
The 4005CD never had an issue going through configuration, but these Flexys simply won't behave.
0 -
Actually, this problem wasn't solved by this information.
We whitelisted *.talk2m.com in our firewall, and the Internet Access Wizard still failed the Internet Connection test.
The reason is that the Flexy 205 apparently asks talk2m what TCP/IP address it should use using the domain name, but then it accesses the configuration server DIRECTLY using a hard-coded TCP/IP address.
So, once we added 92.52.111.213 to our whitelist, the configuration was successful. However, if you guys change that hard address, then we will start failing again. You might want to take a look at why the older system allowed us to pass the firewall, and the new system doesn't. I'm surprised more people don't encounter this issue.
0 -
Hi
Could you please add this Information to the Talk2M Server Addresses & Hostnames Dokument. I had the same issue, because Client Firewall blocks everything.
0 -
I had the same issue. Now i try to whitelist the same IP in the firewall.
0 -
Hello,
This page shows all of the servers and ports that will need to be opened to get the device access through a firewall.
https://www.ewon.biz/technical-support/pages/talk2m/talk2m-status/talk2m-vpn-servers
0 -
Thanks Tim. It is possible that the IP from the Server can change? Example: device.vpn25.talk2m.com is at the moment 158.177.77.149.
0 -
Yes it is possible that the IP could change. We don't ask customers to whitelist IP addresses, but rather whitelist the domain *talk2m.com. Or if that isn't possible, whitelist your URL: device.vpn25.talk2m.com
0
Please sign in to leave a comment.
Comments
14 comments