[rguin]

I've seen that EOFException. You've gone to the cert manager and approved it? Sometimes the cert can change, maybe if the IP changes or something, can't remember exactly but you need to acknowledge the change by double clicking and select the button.

When you say it pings then disconnects. That seems normal. It doesn't stay connected all the time, just when it needs to pass info.
On the property sheet of the station, located in the supers Niagara network, what does it say about the health? Last connect time, last disconnect time and last disconnect cause?

Did the IP or station name change?

Sorry, it could be a million things. These poped into my head. More info would be helpful.

 

[rguin]

Also, if the Supervisor/JACE connection is good. And the problem is discovering points, make sure the user you use for station to station coms has proper permission.

 

[rguin]

It sounds like your connection is solid. Is the problem discovering points?

 

[rguin]

I wish I could pick something out of that exception, knowledge gaps. Could it be the versions? Missing module? Probably not the user but don't overlook.

There's your VPN, Fox port is open? My guess at where to check would be to ping each station on that port in the console. 4911 for foxs

 

[rguin]

You know, the Fox port would be in error if it blocked, probably dumb. It could be something in the config though. Are you able to bypass vpn to any degree, or be inside that network?
You can look through the app director, see if it gives a clue. You can change the log level of the driver or service in question from the spy view of config or station.

Also, you have both open in workbench, looking at it from the station end?