Ecatcher not pinging LAN through virtual Machine
I am using ecatcher 7.0.3 and am having quite a bit of difficulty getting my virtual machine to actually talk to any LAN devices through ecatcher.
I am using Oracle VirtualBox version 7.1.4 , running a Windows 10 image. My host machine is running Windows 11. If i start ecatcher on my host machine, i can ping everything no problem, can connect a VNC viewer to look at the remote HMI. Normally with other VPN clients [ETIC modem, CISCO anyconnect], I can select the TAP V9 adapter that they generate and do a bridged adapter to my VM. this lets me ping through my VM no problem. this was not working so i installed ecatcher directly on to my VM. I've got my WiFi adapter bridged over so the VM has full access to the internet. ecatcher says it is connected and that all devices on the LAN are accessible, however when i try to ping any of the LAN addresses, I get a request timeout. I cant ping the local TAP adapter no problem, whether I'm running ecatcher on my host PC or the VM. but i can't ping the Ewon IP address from my VM under any circumstances. All windows firewalls are turned off [both host and VM] and no other firewalls are active currently.
some things i have tried already:
- host-only adapter with ecatcher running on host machine. - cant ping LAN
- ecatcher running on VM, with only IPv4 enabled. - cant ping LAN
- manually clearing routes and adding back in routes specifically for the ecatcher VPN address range. - cant ping LAN
- force-quitting all other VPN clients on the host PC and the VM. - cant ping LAN
I've scrubbed through every other relevant topic i could find on this forum and a few others, but nothing seems to work.
If anyone could help out, I'd appreciate it.
-
Hi Spencer,
Make sure to check the recommendations in the troubleshooting guide: Unable to Ping or Connect to LAN Device
On the VM, after connecting to the Ewon with Ecatcher, can you ping the VPN IP address of the Ewon?
(this is found to the left of the LAN IP address)
If you type 'route print -4' in the cmd prompt, do you see a route to the LAN network, like this?
What is the result when you run 'tracert 10.10.200.50' (please substitute the actual LAN address of the Ewon)?
Kyle
0
Please sign in to leave a comment.
Comments
1 comment