Connection checker stranger error

Ewon Support Ewon Flexy
#1

thumbnail_image005
thumbnail_image005520×520 9.33 KB

2023-09-06 11:53:35.5263|INFO|ConnectionChecker.TestRunner|---------------------------------------------------------

2023-09-06 11:53:35.7603|INFO|ConnectionChecker.TestRunner|Talk2MConnection Checker 2.0.0 build 16641

2023-09-06 11:53:35.7759|INFO|ConnectionChecker.TestRunner|Starting connection test on 9/6/2023 11:53:35 AM

2023-09-06 11:53:35.7759|TRACE|ConnectionChecker.TestRunner|Identifying your active network interface…

2023-09-06 11:53:35.8071|INFO|ConnectionChecker.TestRunner|Active network interface: Ethernet (Local Area Connection)

2023-09-06 11:53:35.8227|TRACE|ConnectionChecker.TestRunner|Testing DNS. Resolving Talk2M hostname…

2023-09-06 11:53:35.8383|TRACE|ConnectionChecker.TestRunner|Host name : as.pro.talk2m.com

2023-09-06 11:53:35.8539|TRACE|ConnectionChecker.TestRunner|IP address List : 92.52.111.210

2023-09-06 11:53:35.8539|INFO|ConnectionChecker.TestRunner|DNS OK. Talk2M hostname resolved: 92.52.111.210

2023-09-06 11:53:35.8695|TRACE|ConnectionChecker.TestRunner|Testing Internet connectivity. Pinging Talk2M…

2023-09-06 11:53:35.9943|TRACE|ConnectionChecker.Pinger|Pinged 92.52.111.210 (92.52.111.210) in 106 ms

2023-09-06 11:53:36.1191|TRACE|ConnectionChecker.Pinger|Pinged 92.52.111.210 (92.52.111.210) in 106 ms

2023-09-06 11:53:36.2283|TRACE|ConnectionChecker.Pinger|Pinged 92.52.111.210 (92.52.111.210) in 106 ms

2023-09-06 11:53:36.3375|TRACE|ConnectionChecker.Pinger|Pinged 92.52.111.210 (92.52.111.210) in 106 ms

2023-09-06 11:53:36.4467|TRACE|ConnectionChecker.Pinger|Pinged 92.52.111.210 (92.52.111.210) in 106 ms

2023-09-06 11:53:36.4623|INFO|ConnectionChecker.TestRunner|Ping result: Packet loss = 0% RTT = 106/106/106 msec.

2023-09-06 11:53:36.4623|INFO|ConnectionChecker.TestRunner|Internet connection OK. Can ping the Talk2M server.

2023-09-06 11:53:36.4779|TRACE|ConnectionChecker.TestRunner|Testing UDP connection to Talk2M…

2023-09-06 11:53:36.5871|INFO|ConnectionChecker.TestRunner|UDP Connection to Talk2M OK.

2023-09-06 11:53:36.6027|TRACE|ConnectionChecker.TestRunner|Testing TCP connection to Talk2M…

2023-09-06 11:53:37.1019|INFO|ConnectionChecker.TestRunner|TCP connection to Talk2M OK.

2023-09-06 11:53:37.1175|TRACE|ConnectionChecker.TestRunner|Identifying your public IP address…

2023-09-06 11:53:37.5699|INFO|ConnectionChecker.TestRunner|Your public IP: 12.69.154.162

2023-09-06 11:53:37.6011|TRACE|ConnectionChecker.TestRunner|Identifying your Talk2M region…

2023-09-06 11:53:37.6479|DEBUG|Talk2MXmlRpc.Processor|getMyLocation()…

2023-09-06 11:53:38.3031|ERROR|ConnectionChecker.TestRunner|CookComputing.XmlRpc.XmlRpcInvalidXmlRpcException: Invalid value element: <#cdata-section>

at CookComputing.XmlRpc.XmlRpcSerializer.ParseFault(XmlNode faultNode, ParseStack parseStack, MappingAction mappingAction)

at CookComputing.XmlRpc.XmlRpcSerializer.DeserializeResponse(XmlDocument xdoc, Type returnType)

at CookComputing.XmlRpc.XmlRpcSerializer.DeserializeResponse(Stream stm, Type svcType)

at CookComputing.XmlRpc.XmlRpcClientProtocol.ReadResponse(XmlRpcRequest req, WebResponse webResp, Stream respStm, Type returnType)

at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, MethodInfo mi, Object[] parameters)

at XmlRpcProxy636c1127-a1e5-4003-b8c4-1d79070a6331.getMyLocation()

at Talk2MXmlRpc.Processor.GetMyLocation()

at ConnectionChecker.TestRunner.VpnServersTest()

at ConnectionChecker.TestRunner.DoTest(BackgroundWorker worker, WizardContext context)

2023-09-06 11:53:38.3031|ERROR|ConnectionChecker.TestRunner|Invalid value element: <#cdata-section>

#2

Hi evveryone, i have been using eWon for many years, this is first time i come accross with this error? can anyone shed any light?

Thanks
Jiayuan

#3

Hi Jiayuan,

Can you try running a more recent version of the utility? You can download one here: Talk2m Connection Checker

This version is quite out of date, so I’d like to rule that out as the cause before we troubleshoot further.

#5

Hi Hugh,
Sorry for the delay coming back to you. We tried almost all options for thsi eWon. Finally, we changed this eWon to a new Flexy 205, and it worked. However, with the old eWon, I could not see any damage fron hardware point view, and all the software function on that old eWon seems OK.

#6

Can you attach a backup with support files from this device so we can see its logs? You can download a support backup using eBuddy. Select the Ewon, click Backup/Restore, then make sure to check “include support files” before clicking through the rest of the dialogues. You can download eBuddy here: Ewon Software Download | Ewon Technical Support

#7

MOVED TO STAFF NOTE (835 KB)
Thanks Hugh.

#9

It seems like there might be an issue with the FLX3101 extension card that’s being used to provide a WAN Ethernet port for this device. There are errors in the logs showing an issue with communicating with the interface. Can you try powering it down, removing the extension card, then plugging it back into a different slot?