06-04-2020 01:16 PM
Working from home I connect through a VPN to the VPN server of the office configured on top of ClearOS.
From home I can ping all the office except the Compact Rio.
If I connect to my office workstation with remote desktop, then locally I can ping all the office, including the Compact Rio. So it's online and responding.
What can make the CRio to respond to ping requests only from local mates and ignore my home computer through the VPN? What's the difference if connecting through VPN is the same as being locally?
Thanks for your time,
EMCCi
06-08-2020 02:43 PM
[Disclaimer: Networking is not my forte, but I'm happy to share my experience]
Hey EMCCi,
I also work with VPN and cRIO devices across the network (both using remote desktop to a local machine, as well as from my home computer). I have not had problems pinging the devices when remotely. Some things that might be worth considering:
All that being said, I think your IT support is the best bet to get this solved. You can find the common ports used by NI software here: Configuring Software and Hardware Firewalls to Support National Instruments Products
All the best,
06-15-2020 03:52 AM
Hello Oscar,
Sorry for my late response:
1. To the company's network
2. From home I can ping my workstation at 192.168.100.26 and another computer at 192.168.100.33 but I can't ping CRio at 192.168.100.32. So you can see that is the same IP type & range. Our IT service isn't blocking anything because we don't have one 😄 We are a very little company. And yes, locally in the office I can ping the CRio.
3. MAX doesn't detect anything even directly writting the CRio IP because it is inaccesible from VPN due to some obscure reason.
06-15-2020 12:00 PM
Interesting, I've never seen that specific situation with our VPN. 🤔
I guess that depending on how the VPN and internal network are setup, they will require of different settings to "make then visible". Some other ideas I can think about:
All the best,
06-16-2020 03:54 PM - edited 06-16-2020 03:56 PM
I've had some issues with VPN on our corporate network as well. I don't have the same situation as you do but maybe the same solution will work. I've been forcing the connection to my cRIO by adding the route to go through a certain network interface on the computer. To do this you need to open a command window as administrator and use the command:
add 192.168.100.32 mask 255.255.255.255 192.168.100.1
You might need to figure out what the red IP address should be, it should be whatever the VPN is using as a network adapter. Ours creates a virtual network adapter but you should be able to figure that out with ipconfig /all or going into your adapter settings.
06-18-2020 01:52 AM
1. VPN is in company's router. So if you connect to the company VPN you can reach the whole (and unique) company LAN (192.168.100.x)
2. Static. And gateway and mask are ok, I have rechecked. But I have the two ethernet ports configured as static. The primary with 192.168.3.3 (for client applications) and 192.168.100.32 for office. But this shoudn't be a problem
3. We are our own VPN provider. It is configured on clearOS. (Operative system oriented to work as router)
@stillwaiting255
add isn't recognized as internal or external command...
Anyway I can access ALL the other VPN IP's. So I don't know why this one should be different. It seems something from the own CRio... Because all the other things work good when CRio isn't present.
Thanks for your time guys!
EMMCi
06-18-2020 08:02 AM
My apologies, forgot to add the most important part at the beginning, should be:
route add 192.168.100.32 mask 255.255.255.255 192.168.100.1
04-17-2021 03:01 AM
I have exactly the same issue.
Trying with "route add" does not make any difference.
Have you been able to solve the problem? How?
01-17-2022 04:27 AM - edited 01-17-2022 04:29 AM
Sorry for the late response, I haven't read you until now. I will answer because it could be useful for future readers too.
I don't remember it perfectly right now, but if you are in the same situation as me where I could ping all the local network devices unless the cRIO, and the cRIO was pingable from the local network too, it probably indicates that the cRIO gateway isn't properly configured, so it can answer to local ping requests with their physical MAC address, but it can't respond to outside requests that are resolved through IP, the gateway IP.