Able to interact with a cRIO remote front panel from one computer but not another

[WNM]

I have a cRIO application that publishes a remote front panel for monitoring and control of the application. From one PC (Win7 & firefox) I can see, interact and control the cRIO through the published remote front panel. From a second PC, also Win7, I can see and monitor the cRIO's state, but the remote panel that is opened does not allow for any interaction and this is true whether I'm using IE, FF or Chrome as the browser. When either PC is connected to the cRIO, it is via a dedicated Ethernet link and only the cRIO and the one PC are on that network. For this two-device private network, the PC is always at address 192.168.1.1 while the cRIO always uses 192.168.84.199 (port 8000).

The firewall rules on both PCs are setup to allow all incoming and outgoing programs/ports/protocols to be used between these two IP addresses.

Both PC's have up-to-date LabVIEW development systems installed on them (which more or less guarantees they have the minimum require LV runtime needed to see and use a remote front panel).

What might be different on the PC that view but cannot interact with the remote panel?

[natasftw]

Is the mask 255.255.0.0 on both computers?

[WNM]

---

@natasftw wrote:

Is the mask 255.255.0.0 on both computers?

---

Yes it is.

[Sam_Sharp · Accepted solution]

Right click on the second one and select "take control of this VI".

As far as I am aware - only one viewer of the remote front panel can control the panel at any time - the rest can only view.

[WNM]

---

@Sam_Sharp wrote:

Right click on the second one and select "take control of this VI".

As far as I am aware - only one viewer of the remote front panel can control the panel at any time - the rest can only view.

---

As I tried to say in my original post, there was only one host physically connected to the private network at any given time (by virtue of the fact that the one Ethernet cable connection to the private network was being moved back & forth between the two hosts) so there was no way both hosts could be trying to control the cRIO at the same time. I even went so far at one point of restarting the cRIO while it was connected to the problem host to see if would render it functional, but it did not.

But I did not know that it was possible to do what you suggested, much less that there was a right-click context menu associated with a remote panel, so I tried it and it worked!    Thank you!