1783-natr

epavin

Member
Join Date
Oct 2019
Location
Michigan
Posts
8
Hello,

I've got a 1783-NATR installed and configured and I am currently able to connect remotely to a CompactLogix PLC added to the NAT rules. I am trying to NAT a PC running Windows 7 connected to the same ENET switch as the PLC in the electrical panel but I can't ping/see that PC from the Public Network. This is what I have for IP's and configuration.

Public:
10.220.210.19
255.255.255.0
10.220.210.1

Private
192.168.3.1
255.255.255.0

NAT Rules
Public IP --------- Private IP
10.220.210.20 --- 192.168.3.201 (PLC)
10.220.210.21 --- 192.138.3.200 PC)

Thank you!
 
Hello,

I've got a 1783-NATR installed and configured and I am currently able to connect remotely to a CompactLogix PLC added to the NAT rules. I am trying to NAT a PC running Windows 7 connected to the same ENET switch as the PLC in the electrical panel but I can't ping/see that PC from the Public Network. This is what I have for IP's and configuration.

Public:
10.220.210.19
255.255.255.0
10.220.210.1

Private
192.168.3.1
255.255.255.0

NAT Rules
Public IP --------- Private IP
10.220.210.20 --- 192.168.3.201 (PLC)
10.220.210.21 --- 192.138.3.200 PC)

Thank you!

Your PC is x.138.x.x instead of x.168.x.x
or your NAT Rule is wrong... please reverify
 
It's been awhile since I set up an 1783-NATR, but I think I remember I had to set the default gateway on the Private side of the network... PLC/HMI/etc. to the Private IP address of the NATR.
In your case the default gateway of PLC/PC would be 192.168.3.1
 
It's been awhile since I set up an 1783-NATR, but I think I remember I had to set the default gateway on the Private side of the network... PLC/HMI/etc. to the Private IP address of the NATR.
In your case the default gateway of PLC/PC would be 192.168.3.1

He is correct. You need to set gateway addresses to the devices.
 
Correct me if I am wrong but.... I usually am wrong but....

I thought the 1783-NATR Device could only translate 1 address and to do multiple address, you would need to use a 9300-ENA such as I have set up here doing multiple translations.
 
Correct me if I am wrong but.... I usually am wrong but....

I thought the 1783-NATR Device could only translate 1 address and to do multiple address, you would need to use a 9300-ENA such as I have set up here doing multiple translations.

The 1783-NATR supports up to 32 translations and the 9300-ENA supports 128.
 
Yes, I have set gateway of 192.168.3.1 to the PLC and PC. I can currently see the PLC from the Public but not the PC.

For clarification, I take it that you can "see the PLC from the Public" side is that you are using RSLinx configured Ethernet driver for the NAT translated IP of 10.220.210.20 to access PLC IP 192.163.3.201... which works fine.

Now for the "see" but not the PC. I would assume you are trying to PING the PC at IP address 192.168.3.200 (if my assumption is wrong please state so)

From what I know NAT does not allow PING from public to private (and vice versa) that is to keep the private Private and public Public. You will only be able to PING the Translated addresses and only on their side of the network.

example: If you were to PING the 1783-NATR translated public IP 10.220.210.20 and have disconnected a private side device such as the PLC Ethernet. The PING would still PING as good.
 
For clarification, I take it that you can "see the PLC from the Public" side is that you are using RSLinx configured Ethernet driver for the NAT translated IP of 10.220.210.20 to access PLC IP 192.163.3.201... which works fine.

Now for the "see" but not the PC. I would assume you are trying to PING the PC at IP address 192.168.3.200 (if my assumption is wrong please state so)

From what I know NAT does not allow PING from public to private (and vice versa) that is to keep the private Private and public Public. You will only be able to PING the Translated addresses and only on their side of the network.

example: If you were to PING the 1783-NATR translated public IP 10.220.210.20 and have disconnected a private side device such as the PLC Ethernet. The PING would still PING as good.

I can PING the PLC from the Public address and I can also see the PLC in RSlinx using the Public address. I can not PING the PC from Public or see it in RSLinx.

I've also heard in the past that NAT does not allow PING from Public to Private but I've installed a few NATR's in the past 2 years and I've been able to PING devices from Public to Private. Maybe PING does not work for the 9300-ENA?

RSlinx NATR.jpg
 

Similar Topics

Is it possible to gather OPC data through a 1783-NATR? Searching around, it sounds like OPC data might be blocked by any NAT... Is there any work...
Replies
2
Views
236
Good morning all, I have a project that has quite a few NATRs to configure. I would like to modify the generated backup config file because I...
Replies
2
Views
388
I am trying to communicating with other PLCs on a public network from a CompactLogix PLC on a private network. I have installed at 1783-NATR...
Replies
1
Views
519
Hello, I'm seeing some interesting behavior with my NATR connections on FTLinx. 2 separate cases are showing the same problem: The first NATR...
Replies
0
Views
612
Hello, I have been trying to set up a NATR with 3 connections, I am able to ping the public IP of the NATR itself off of my network, but nothing...
Replies
3
Views
652
Back
Top Bottom