You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connecting the first time with a windows machine to a remote ssh server within the MCX studio will result in a deadlock.
The server will respond with the usual add fingerprint dialog awaiting input, but commands entered in the user input box of MCX Studio will not be recognized by remote terminal. This results in a deadlock, MCX studio will no longer respond.
Prompt:
"If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n)"
Solution:
Open cmd and paste the pwlink command, e.g. "plink -pw ### -ssh user@## -P ## mcx -L". Add the key to your cache and you no longer get the message. Next you see the remote output in MCX Studio. If mcx is not found on the remote machine, add it to path variable. Force close MCX studio and try again. Now you get the next error message
"-- Executing Simulation --"
MCX ERROR(-2):can not load the specified config file in unit mcx_utils.c:1074
"-- Task completed --"
At least the pwlink is working
The text was updated successfully, but these errors were encountered:
As explained, if I try to do input in the command input box and click send, the string is copied to the output log. But nothings happening. If you press several times enter only a new line appears in the log. I think the string is never sent. Maybe the string is not terminated right. CRLF vs LF vs NL
Connecting the first time with a windows machine to a remote ssh server within the MCX studio will result in a deadlock.
The server will respond with the usual add fingerprint dialog awaiting input, but commands entered in the user input box of MCX Studio will not be recognized by remote terminal. This results in a deadlock, MCX studio will no longer respond.
Prompt:
"If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n)"
Solution:
Open cmd and paste the pwlink command, e.g. "plink -pw ### -ssh user@## -P ## mcx -L". Add the key to your cache and you no longer get the message. Next you see the remote output in MCX Studio. If mcx is not found on the remote machine, add it to path variable. Force close MCX studio and try again. Now you get the next error message
At least the pwlink is working
The text was updated successfully, but these errors were encountered: