Brandon M's community posts

I posted the code above, that's exactly what I did. The password is saved in the connection. It doesn't work, it just opens up the UI, because the connection isn't "logged in" and there is no CLI command that I could find to get the connection to logon before trying to use it. But for some reason, double clicking on the connection in the UI takes care of this automatically, but the CLI does not.

I'm currently evaluating this software for a project, where one of our computers needs to duplicate the screen of  a terminal on a robot arm system. Everything is running windows 10.

I can manually connect the two systems, running the Viewer UI and double clicking on the connection. That works just fine. However running the command:

rutview /navsystem /fullcontrol

brings up the the Viewer UI, but does not connect to the other system. The remote system is shown as offline until I manually connect by double clicking on the saved connection in the UI.

Is there a way to get the commandline interface to do this automatically? I didn't see any "logon" command for the CLI like there is in UI.

I'm also kinda confused, what's the point of having the CLI options to connect to a system, if it won't do that until after you've manually run the UI and selected "Logon"?