Cannot use Allen-Bradley BOOTP/DHCP Tool over an eCatcher connection
Hi,
Long time user with a great deal of experience in getting all aspects of an eWON working... but this one has me stumped.
When I use eCatcher to connect to an eWON, I normally get access to that remote LAN as if I have plugged into the system locally.
I can ping devices with no issue, as long as they have been set up in the Firewall settings as accessible devices.
I normally talk to Allen-Bradley PLCs and HMIs, and their programs have no issues in talking to the devices on that remote side.
However, I have run into a case where a certain utility cannot see the VPN as a way to access those remote devices.
This is the BOOTP/DCHP tool for Allen-Bradley devices.
You run the program, but instead of being able to see (example) the 10.10.45.xxx subnet of the LAN, it uses the subnet of the TAP Windows Adapter, such as (example) 10.23.130.182.
When I run that program, it asks me which network connection I want to use, but the LAN which is connected by my VPN is not offered as a choice.
QUESTION:
Is there something I can do (or that I am missing) to associate my LAN to that TAP address, perhaps like a gateway, so my laptop will know that 10.10.45.xxx can be reached using the TAP address of 10.23.130.182? (examples)
-
Hi Mitchell.hein!
Unfortunatly BootP is not working over the VPN connection of Cosy/Flexy.
BootP is for very low level communciation like setting an IP address when your device has none.
(MAC Layer communication) and that does not work...
If it were about Broadcasts you could do that:
But MAC Layer stuff that is needed for commissioning devices doesn't work. over the remote Connection unfortunately
You could try our Netbiter Product instead. It uses a different way to connect and allows more (also MAC Layer stuff) i belive.
br
i.A. Franziska Gültig
0
Please sign in to leave a comment.
Comments
1 comment