List of Contributions

Ah, I apologize. You were correct, this has fixed the issue. I am experiencing a code 8004f207 trying to put one of the modules in from what was on the EN2T but that's a separate issue I'll work through. Thanks for all the help and patience! -------------------------------------------

If I move all of the devices under the controller vs the EN2T, I will still be unable to go online via FT Logix Echo unless I use the 127.0.0.1. -------------------------------------------

The way I had approached it was similar to having a real switch + PLC + EN2T setup on my second ethernet card. Set the PC/card as its own IP, and everything else is different as to not create IP conflicts. I changed my adapter settings for my loopback network to be the same as the PLC IP in FT Echo ...

Mark, So I added the Hyper V adapter and can ping it at 192.168.1.3, and my PC is properly routing 192.168.1 addresses through that adapter, but putting a Logix Echo PLC on that network won't connect. Going off of the "Logix Echo with Loopback Adapter" link you shared, I installed the Windows Loopback ...

I had to let go of my switch for another project going on and am currently trying to make do with Logix Echo. I'm able to connect to the Logix Echo Chassis via loopback address, 127.0.0.1, but I know that you cannot make a Class 1 connection via loopback. I'm attempting to connect the PLC to Logix Echo ...