Jetson Xavier NX Dev kit – could not connect from windows to NX via SSH

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

When using SshClient, I got below errors.
SSH_Fail

I can ping it successfully, but there are packets loss.
SSH-Fail-2

In the command line, I can connect successfully for a while, but the connection will be lost soon, and shown as ‘reset’.

SSH-Fail
SSH-Fail652×859 16 KB

I want to connect via USB.

I did not connect it via wifi or either net, since my windows and the Xavier NX is connected to different wifi.

I disconnected the wifi on Xavier NX.

Please help to let me know how to connect to it via SshClient, thank you.

5

Please remove the micro usb cable and connect it again.

6

Thank you WayneWWW,

I want to connect via USB.

I did not connect it via wifi or either net, since my windows and the Xavier NX is connected to different wifi.

I disconnected the wifi on Xavier NX.

7

The micro-USB is “hot plug”. You could disconnect it and reconnect the cable and the problem might go away.

If you are not using the cable which comes with the dev kit, then I would be suspicious of cable quality (charger cables very rarely work well for data).

You could also test the same thing to another computer and find out if the problem transfers to other computers as well.

8

This happened to me too. NX is running a DHCP server that automatically assign IP address 192.168.55.100 to your Windows host when connecting with the USB. I don’t know it is Windows driver issue or not but I ran into the same issue in some Windows 10, particularly those Windows 10 that has been upgraded to 1903 or later version. What I did to get around this issue is to assign a static IP address on the Windows end, for example, 192.168.55.55, and that works fine.

It is also came to my attention that this issue may happen more often if the Windows end USB is a USB-C. You may try connect to a USB-A port to see if that mitigate the problem.

9

You are probably in the right area for the topic, but rather than being a driver issue, I think it is a security setup issue. If the host PC (regardless of being Linux or Windows or Mac) is set up to not allow plugging in network devices and configuring them by default for security reasons, then the host PC would need a setting change for this. Setting up as DHCP or static is probably part of that setup.