EC310 Lan not connecting to PLC and HMI

Ewon Support Ewon Netbiter

Cpeyerk March 15, 2023, 1:00pm #1

Hello,
I have been using EC310’s for years so I am pretty knowledgeable about them and troubleshooting. I have a customer with one and it was working fine until I logged on today. I can connect to the EC310 but cant see the plc or hmi on the lan side (those are the only things plugged into the EC310, thru a switch). I updated the firmware and config, had then try a new cable to the switch to the lan port, as well as directly to the plc but still nothing. I know it could possibly be a bad lan port, but it was working fine a month or so ago.
Current info:

|Product name |EC310|

|Version|2.04.05|

|Build|01|

|Kernel version|4.1.37-yocto-standard|

|MAC address|00:30:11:FA:66:7C|

|WAN IP|192.168.113.39|

|LAN IP|192.168.0.215|

|Information updated|2023-03-14 19:37:56|

|Time settings|Time check OK (-1 sec)|

Cpeyerk March 15, 2023, 1:56pm #2

Also, there is no overlap.
PLC → 192.168.0.1
HMI → 192.168.0.2
Ewon → 192.168.0.215
Computer on Lan thru Ewon → 192.168.0.105
Wan → 192.168.113.39

kyle_HMS March 15, 2023, 2:01pm #3

Did you make sure that the TAP adapter is named “QuickConnect Network Bridge”?

Is there another VPN connection on the PC? This could be interfering with the routing.

Cpeyerk March 15, 2023, 2:58pm #4

The adaptor is named correctly, it would not connect to the ewon if it wasnt. I have two other vpn’s but they are not connected.
I have attached picture of the adaptors as well as the lan devices

kyle_HMS March 15, 2023, 7:57pm #5

1- Please run the following commands in the Windows Command prompt and share screenshots of the result:

‘ipconfig’
‘route print -4’

2- Please send the QuickConnect logs located in C:\ProgramData\HMS\QuickConnect.

For additional logging you can launch Quickconnect from C:\Program Files (x86)\HMS\QuickConnect/Quickconnect (extra logging)

3- Please share the System ID of the device.

kyle_HMS March 15, 2023, 8:02pm #6

Also, can you ping 192.168.0.215? If not, please share the error message and the response to ‘tracert 192.168.0.215’ in command prompt.

Cpeyerk March 15, 2023, 8:32pm #7

System ID 003011FA667C

lts.log (28.7 KB)

C:\WINDOWS\system32>ipconfig

Windows IP Configuration

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter Ethernet 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter Ethernet 4:

Connection-specific DNS Suffix . : Industrial
Link-local IPv6 Address . . . . . : fe80::9387:e815:79ed:617a%20
IPv4 Address. . . . . . . . . . . : 192.168.22.143
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.22.1

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter QuickConnect Network Bridge:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::6a72:ce3d:8eba:fc64%10
Autoconfiguration IPv4 Address. . : 169.254.172.182
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\WINDOWS\system32>route print -4

Interface List
19…54 b2 03 0f 5b 0e …Intel(R) Ethernet Connection I219-LM
2…02 50 41 00 00 01 …PANGP Virtual Ethernet Adapter #2
20…54 b2 03 0f 5b 0f …Dell Giga Ethernet
12…38 ba f8 f1 6d 56 …Microsoft Wi-Fi Direct Virtual Adapter
21…3a ba f8 f1 6d 55 …Microsoft Wi-Fi Direct Virtual Adapter #2
10…00 ff 39 e0 b0 f0 …TAP-Windows Adapter V9
23…38 ba f8 f1 6d 59 …Bluetooth Device (Personal Area Network)
22…38 ba f8 f1 6d 55 …Intel(R) Dual Band Wireless-AC 8260
1…Software Loopback Interface 1

IPv4 Route Table

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.22.1 192.168.22.143 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
169.254.0.0 255.255.0.0 On-link 169.254.172.182 311
169.254.172.182 255.255.255.255 On-link 169.254.172.182 311
169.254.255.255 255.255.255.255 On-link 169.254.172.182 311
192.168.22.0 255.255.255.0 On-link 192.168.22.143 281
192.168.22.143 255.255.255.255 On-link 192.168.22.143 281
192.168.22.255 255.255.255.255 On-link 192.168.22.143 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 169.254.172.182 311
224.0.0.0 240.0.0.0 On-link 192.168.22.143 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 169.254.172.182 311
255.255.255.255 255.255.255.255 On-link 192.168.22.143 281

Persistent Routes:
None

C:\WINDOWS\system32>

C:\WINDOWS\system32>ping 192.168.0.215

Pinging 192.168.0.215 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.215:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS\system32>

C:\WINDOWS\system32>tracert 192.168.0.215

Tracing route to 192.168.0.215 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.22.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

kyle_HMS March 15, 2023, 9:30pm #8

Your TAP adapter doesn’t have a valid IP address:

Have you tried uninstalling and reinstalling QuickConnect?

Cpeyerk March 16, 2023, 12:57pm #9

i removed the tap adaptor, I uninstall and reinstalled. still had issue and non valid IP. I updated the driver for the adaptor and still had issue and non valid IP. What do you think would cause this? It has been working fine til recently.
As a note, i also use this adaptor for ecatcher, i just rename it and make sure to put the ipv4 back to auto when switching back to quickconnect.

Cpeyerk March 17, 2023, 1:35pm #10

I tried using a hotspot for internet instead of my network and still the same issue. I just tried connecting to a different customer/netbiter and it connected fine and gave a valid IP for it, but when I tried the problem netbiter again still the same issue with the non valid IP. (other customer ref below)

kyle_HMS March 17, 2023, 5:04pm #11

It sounds like there is a problem with the IP address you are trying to use, so it’s rejecting it - possibly an IP conflict? Have you tried a different one?

Cpeyerk March 17, 2023, 5:40pm #12

How would I try a different one, do you mean the IP address for the LAN? It was 215 and i changed it to 205.Same issue.
for the Wan i believe they set a statis IP with the following info:
IP: 192.168.11.200
SM: 255.255.255.0
GW: 192.168.113.1

kyle_HMS March 17, 2023, 6:42pm #13

Yes.

It seems strange that the IP is set for another Netbiter, but not for this one. Have you tried resyncing the settings on the Netbiter and creating a new connection in QuickConnect?