I installed NVIDIA Sync and AI Workbench on a Windows 11 Pro system without any problems. I was able to connect it to my DGX Spark and successfully opened a terminal exactly once. Since then, I am unable to open a terminal (the terminal window pops open and immediately closes). I am still able to use the AI Workbench both locally with docker on the Windows 11 Pro system and connected to the DGX Spark.
I have found the logs on the Windows 11 side of the conversation but don’t immediately see anything that tells me anything other than it opened and closed a connection successfully (if I’m reading the logs correctly).
While I have other SSH tools that can connect to the DGX Spark from the same Windows 11 Pro system, I would like to understand what changed to make the NVIDIA Sync terminal stop working.
I had the similar issue when running the Nvidia Sync APP on MacBookPro. I solved the problem by removing the DGX host MAC_ADDRESS entry from .ssh\known_hosts.
Not sure
Thanks. I tried your suggestion with the corresponding file under Windows 11. Unfortunately it didn’t work. I even removed the device (and cleared it out of the AppData…NVidia Corporation…ssh_config file so Sync would complain about the device still being there after I deleted it). The terminal window still opens and closes without displaying anything other than the window borders (and the Command Shell wrapper).
I noticed some logs in the path where the ssh_config file was under Sync, so I’ll go have a look there for any clues and report back if I find anything.
Adding a bit more to the mystery: On a different Windows 11 Pro system (an Intel NUC), I installed NVIDIA Sync without any problem, and it connects with the terminal flawlessly. I decided to connect both systems and observe the changes to the NVIDIA Sync-desktop log files. Both of them are identical in their responses to a terminal connection request. (They both look like they are reporting success, however I am making some assumptions based my interpretation of what’s written in the log responses.) I can say, however, that both are identical, even though one system is connecting via a terminal, and the other is not.
I am seeing the same behavior on Ubuntu as well. If I open a terminal manually and ssh in, it works fine. If I open the Sync tool and click the Terminal icon in it, the terminal pops up and closes immediately. No logs are written to nsync.log when it happens. The NVIDIA\ Sync-desktop.log shows that it opened successfully, with no errors reported. If I run the command listed on the spawnProcess log line, I get the same behavior. I temporarily changed gnome-terminal to not auto-dismiss the windows, and it looks like it is exiting with code 255 because of “Too many authentication failures”. Odd since manually calling ssh from a open terminal connects successfully… but maybe it is a similar reason for all of you.