# Connecting PLCs with the same IP address **URL:** \ **Category:** General Discussion\ **Created:** [May 27, 2020, 2:42pm UTC](https://forum.inductiveautomation.com/t/connecting-plcs-with-the-same-ip-address/35082 "2020-05-27T14:42:20Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![vasilevdim](https://avatars.discourse-cdn.com/v4/letter/v/7ba0ec/32.png) [@vasilevdim](https://forum.inductiveautomation.com/u/vasilevdim)\ **Post date:** [May 27, 2020, 2:42pm UTC](https://forum.inductiveautomation.com/t/connecting-plcs-with-the-same-ip-address/35082/1 "2020-05-27T14:42:20Z")
Hi all, Ignition 8.04, Windows 10 KEPWARE Server 6.8 Task: to connect 6 PLC ELAU C400 that have the same IP address (and it cannot be changed). Connecting one PLC to the PC has no issues. What needs to be done in case when multiple devices with the same IP address must be connected? Someone to share experience? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 27, 2020, 3:06pm UTC](https://forum.inductiveautomation.com/t/connecting-plcs-with-the-same-ip-address/35082/2 "2020-05-27T15:06:01Z")
Each machine will need some network gear in front of it doing NAT or something like that. You can’t have multiple instances of the same IP on a network. ---
**Author:** ![vasilevdim](https://avatars.discourse-cdn.com/v4/letter/v/7ba0ec/32.png) [@vasilevdim](https://forum.inductiveautomation.com/u/vasilevdim)\ **Post date:** [May 27, 2020, 3:11pm UTC](https://forum.inductiveautomation.com/t/connecting-plcs-with-the-same-ip-address/35082/3 "2020-05-27T15:11:51Z")
Yes, this is what I know too, I was wondering if someone has done something similar already, so at least some recommendations from hardware point of view could be shared. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 27, 2020, 3:14pm UTC](https://forum.inductiveautomation.com/t/connecting-plcs-with-the-same-ip-address/35082/4 "2020-05-27T15:14:44Z")
Ah, okay. I will defer to those who’ve actually put things into production for a hardware recommendation. ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [May 27, 2020, 3:16pm UTC](https://forum.inductiveautomation.com/t/connecting-plcs-with-the-same-ip-address/35082/5 "2020-05-27T15:16:25Z")
Like @Kevin.Herron indicated, the use of a NAT device will be required. Rockwell has quite a few options for NAT stuff with their Stratix line of hardware. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 27, 2020, 5:01pm UTC](https://forum.inductiveautomation.com/t/connecting-plcs-with-the-same-ip-address/35082/6 "2020-05-27T17:01:06Z")
Does the facility already have network connections to these devices? If so, there must already be some form of NAT in place (independent VLANs). I would look for that information and piggy-back on that. If not, I would strongly recommend having this done in a managed switch with layer3 support, if not in an actual firewall. ---
**Author:** ![wking](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/wking/32/21823_2.png) [@wking](https://forum.inductiveautomation.com/u/wking)\ **Post date:** [May 27, 2020, 5:09pm UTC](https://forum.inductiveautomation.com/t/connecting-plcs-with-the-same-ip-address/35082/7 "2020-05-27T17:09:41Z")
Couldn't recommend this bad-boy enough (500$): > **[MikroTik](https://mikrotik.com/product/crs354_48g_4splus2qplusrm)** > > MikroTik makes networking hardware and software, which is used in nearly all countries of the world. Our mission is to make existing Internet technologies faster, more powerful and affordable to wider range of users. Might be helpful: > [@Can anyone recommend a 48 port rack-mountable NAT Switch/Router?](http://forum.inductiveautomation.com/t/can-anyone-recommend-a-48-port-rack-mountable-nat-switch-router/32683): > > I have 36 machines. They are all copies of each other as far as the network goes. PLC is always kept at 192.168.0.100. The idea is to run a line to every machine. And do 1:1 Port Aware NAT translation. Plugging into the spare port on PLC comm coprocessor. They’re L18s or whatever so no extra network card. Right? The server lives at: 120.120.80.212 For example: Port 1 --\> 192.168.0.100:44818 --\> 120.120.80.1 \<–\> Server Port 2 --\> 192.168.0.100:44818 --\> 120.120.80.2 \<–\> Server I have a coupl… I plan on updating this post. With a guide of sorts. With what I, as a very novice network/IT eng, did when I was in your situation. But, basically you need to set up a network device to isolate ports from each other. And NAT 1:1 translate packets between devices and server. Or you could use a device for every machine. Like with what was mentioned above. With Stratix switches or something. If $$$ isn't an issue. I'd go that way. ---
**Author:** ![craigb](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@craigb](https://forum.inductiveautomation.com/u/craigb)\ **Post date:** [May 28, 2020, 10:04am UTC](https://forum.inductiveautomation.com/t/connecting-plcs-with-the-same-ip-address/35082/8 "2020-05-28T10:04:12Z")
What about using the MikroTik map. I use these for wireless PLC access points. Approx 30$ each. Not sure if it would work but you could assign each one a unique ip on your network, plug it into your plc and do some port forwarding. This way you use the map ip rather then the plc ip. > **[MikroTik](https://mikrotik.com/product/RBmAP2nD)** > > MikroTik is a Latvian company which was founded in 1996 to develop routers and wireless ISP systems. MikroTik now provides hardware and software for Internet connectivity in most of the countries around the world.