09-05-2017 06:39 AM
Hallo,
I am using cRIO 9039, but cannot ping it from a remote location. We tried using the Network Address Translation (NAT) to assign the cRIO an IP of our company´s network, but had no success. Do I need to change anything in the settings of the cRIO? Because other devices could be connected successfully through NAT.
Or do I need a seperate VPN connection to solve my issue?
Greetings,
09-05-2017 04:23 PM
You're going to have to clarify what you mean by a "remote location". Do you mean like you're at home and you're trying to ping a CRIO at work?
Did you see this article? Does your CRIO pick up an address? Is it something like 192.168...?
http://www.ni.com/getting-started/set-up-hardware/compactrio/dhcp
How are the other devices connected? Did IT have to setup port forwarding? What addresses are they acquiring?
09-06-2017 03:30 AM
Hallo,
what I meant by a remote location is that the cRIO is located in a different city and I am trying to ping it from my workplace. I did go through the link you sent, but we a using a static IP. As for the other devices, they were assigned IPs from our firm´s network from Scalance/Firewall. At least thats what I was told. Similarly an IP was given to the cRIO as well. But I could not ping the cRIO on this IP.
09-06-2017 12:05 PM - edited 09-06-2017 12:06 PM
FYI, this is primarily a networking question and not a CRIO question. I'm not a networking expert but I'll try and describe what I think would work. IT would probably be more knowledgeable than I am. Your network probably looks something like this
CRIO LAN (192.168.0...)---Public IP address (xx.xx...)---Public IP address---your PC on Remote LAN (192.168.1 etc)---
A VPN to the CRIO LAN or to the CRIO itself would work because it would let you see 192.168.1 from your PC.
The other option is to setup port forwarding. For example, if you get one of the web server examples working on your RIO you should be able to reach your RIO on the CRIO LAN by typing http://CRIOIP/index.html or something like that
Now, since the CRIO has a fixed IP address, IT should be able to set it up so that requests at the public address at some arbitrary port, say 12345, are forwarded to your CRIO. So then you'd be able to see your CRIO from the Remote LAN by typing http://publicIP:12345/index.html
This requires that you know what ports your CRIO is using. In the example above HTTP uses port 80.
Pinging would not work with port forwarding because you can only ping the router at the public IP address.