# Connecting to a NET ENI

**URL:** <https://forum.inductiveautomation.com/t/connecting-to-a-net-eni/7211>\
**Category:** Ignition\
**Created:** [September 6, 2013, 5:55pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-net-eni/7211 "2013-09-06T17:55:15Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikehill100](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@mikehill100](https://forum.inductiveautomation.com/u/mikehill100)\
**Post date:** [September 6, 2013, 5:55pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-net-eni/7211/1 "2013-09-06T17:55:15Z")

</div>

Trying to connect to a PLC over a NET ENI. Will not connect. Can ping device.

Have tried disabling browse. Have tried restarting device to free up connections.

Know that nobody likes NET ENIs. I don’t either but it’s what I have to deal with.

Looking for advice.

Using version 7.6.2.

---

<div class="post-metadata">

**Author:** ![Micky.Franks](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Micky.Franks](https://forum.inductiveautomation.com/u/Micky.Franks)\
**Post date:** [September 6, 2013, 9:10pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-net-eni/7211/2 "2013-09-06T21:10:56Z")

</div>

Can you connect to the PLC with RsLinx through the ENI?

---

<div class="post-metadata">

**Author:** ![greg.simpson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/greg.simpson/32/3135_2.png) [@greg.simpson](https://forum.inductiveautomation.com/u/greg.simpson)\
**Post date:** [September 6, 2013, 9:45pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-net-eni/7211/3 "2013-09-06T21:45:26Z")

</div>

What PLC are you connecting to? Have you tried restarting the NET-ENI?

---

<div class="post-metadata">

**Author:** ![Justin](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@Justin](https://forum.inductiveautomation.com/u/Justin)\
**Post date:** [September 13, 2013, 8:08pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-net-eni/7211/4 "2013-09-13T20:08:44Z")

</div>

I’ve had a lot of trouble with these too as we have several in our plants. Rebooting usually restored communications, but only for awhile. Currently we only use Digi One IAP if we have intend to go online for programming/troubleshooting purposes. You may have tried this, but try connecting locally via ethernet if possible so you are connecting directly from your pc to the device. Rule out any other networking issues or OPC servers trying to connect such as Kepware. Shutdown RSLinx completely and restart. Also, if that doesn’t work, try restarting the PC you are using to connect with. I feel your pain…

---

<div class="post-metadata">

**Author:** ![Toby](https://avatars.discourse-cdn.com/v4/letter/t/7993a0/32.png) [@Toby](https://forum.inductiveautomation.com/u/Toby)\
**Post date:** [September 15, 2013, 12:32pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-net-eni/7211/5 "2013-09-15T12:32:00Z")

</div>

ENIWs are a pain. I found the easiest way to connect to a plc using ENIWs is to setup a read and write message to a PLC with an onboard Ethernet port like a micrologix 1100, 1400 or better yet a compact or control logix. Use the PLC that you are messaging too push / pull the data from your ignition project to the PLC with the ENIW. For some reason message instructions seem to be the only thing ENIWs do well.

Also every driver in linxs that points to the ENIW consumes a connection. ENIW’s are limited to two bidirectional connections, two outgoing connections and two incoming connections.

The ENI and ENIW support a maximum of 6 connections, allowing  
simultaneous communication with up to 6 other devices or  
applications. The connections are dedicated as follows:  
Number of Connections Dedicated to:  
2 outgoing messages  
2 incoming messages  
2 either incoming or outgoing messages

---

<div class="post-metadata">

**Author:** ![shawn\_75](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@shawn\_75](https://forum.inductiveautomation.com/u/shawn_75)\
**Post date:** [September 16, 2013, 6:29pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-net-eni/7211/6 "2013-09-16T18:29:56Z")

</div>

You haven’t yet provided much information beyond your ability to ping, so I’ll give some general ENI advice.

Upgrade to the latest firmware, especially with a series D. Upgrading the D’s I have to 3.22 made a world of difference to me. Also, even if you aren’t using external power for the ENI via the terminal strip, ensure that the ground lug is grounded.

These two things have reduced my ENI troubles drastically.

Shawn

---

<div class="post-metadata">

**Author:** ![mikehill100](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@mikehill100](https://forum.inductiveautomation.com/u/mikehill100)\
**Post date:** [October 4, 2013, 3:29pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-net-eni/7211/7 "2013-10-04T15:29:54Z")

</div>

Finally figured it out.

The PLC was in master slave mode.
