# NVIDIA Jetson Nano SSH problems (works with ethernet but not microUSB)

**URL:** <https://forums.developer.nvidia.com/t/nvidia-jetson-nano-ssh-problems-works-with-ethernet-but-not-microusb/188882>\
**Category:** Jetson Nano\
**Tags:** usb, ethernet\
**Created:** [September 9, 2021, 4:23pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-ssh-problems-works-with-ethernet-but-not-microusb/188882 "2021-09-09T16:23:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![praveen.elango](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@praveen.elango](https://forums.developer.nvidia.com/u/praveen.elango)\
**Post date:** [September 9, 2021, 4:23pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-ssh-problems-works-with-ethernet-but-not-microusb/188882/1 "2021-09-09T16:23:29Z")

</div>

I can ssh into my Nano using an ethernet cable (`ssh rdc@10.42.0.76)`but I am unable to do so using my microUSB cable(`ssh rdc@10.42.0.1`).  
The IP addresses are different as per `ifconfig`. When I type the same password that I can successfully ssh in with my ethernet cable for when I am ssh-ing in with my microUSB, it keeps returning `Permission denied, please try again`. When I tried `sudo service ssh status` when attempting to ssh with microUSB cable, I get the following output:

```auto
Sep 10 00:00:47 praveen-ThinkPad-T470 sshd[2045]: Invalid user rdc from 10.42.0.1 port 48836
Sep 10 00:00:49 praveen-ThinkPad-T470 sshd[2045]: pam_unix(sshd:auth): check pass; user unknown
Sep 10 00:00:49 praveen-ThinkPad-T470 sshd[2045]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.42.0.1
Sep 10 00:00:51 praveen-ThinkPad-T470 sshd[2045]: Failed password for invalid user rdc from 10.42.0.1 port 48836 ssh2

```

When I tried ssh-ing repeatedly with microUSB and checked ssh status, I noticed that the port in the `Invalid user rdc from 10.42.0.1 port 48836` always changes. I would appreciate some help, thanks!

---

<div class="post-metadata">

**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\
**Post date:** [September 9, 2021, 9:07pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-ssh-problems-works-with-ethernet-but-not-microusb/188882/2 "2021-09-09T21:07:01Z")

</div>

When the micro-B USB is plugged in to the Jetson it functions in device mode. One such device is the ethernet you are speaking of, but the Jetson’s default address on such ethernet is `192.168.55.1`. I suspect you are using the wrong IP address when I see notes about `10.42.0.1`.

Also note that if you monitor “`dmesg --follow`” on the host PC as you insert the USB cable to the host PC you will see devices discovered during the plugin. One such note will show the MAC address of the virtual USB wired ethernet device. Not all host PC installations allow USB devices without some sort of “ok” from the user, and so you might need to use an app such as “`sudo nm-connection-editor`” (if you don’t have this you can use the built in network admin apps, or else “`sudo apt-get install network-manager-gnome`”) to tell the host PC that the interface is allowed.

On your host PC, if you run commands “`ifconfig`” and “`route`”, then I suspect you don’t have an interface for the “`192.168.55.x`” network, and any routes you might have probably don’t name a route to that subnet. Once the interface is marked as usable and not forbidden this should change.

---

<div class="post-metadata">

**Author:** ![praveen.elango](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@praveen.elango](https://forums.developer.nvidia.com/u/praveen.elango)\
**Post date:** [September 10, 2021, 1:11am UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-ssh-problems-works-with-ethernet-but-not-microusb/188882/3 "2021-09-10T01:11:34Z")

</div>

Hi, I did enable the interface on the Network Manager as per your suggestion, and now the IP address of the Nano when connected using the microUSB shows `192.168.55.100` as shown in the picture below. When I ping the IP address, I am able to get the data packets. However, when I attempt to ssh in using the password that I set for my Nano, it keeps saying `Permission denied, please try again.`

 ![forumimg](https://global.discourse-cdn.com/nvidia/original/3X/1/7/17c1c31548c90bf2195a131382dee813f6e0e8eb.png)

---

<div class="post-metadata">

**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\
**Post date:** [September 10, 2021, 7:29pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-ssh-problems-works-with-ethernet-but-not-microusb/188882/4 "2021-09-10T19:29:46Z")

</div>

You’re almost there! The address `192.168.55.100` is that of your local PC, not the Nano. What you’re doing when you try to `ssh` to `192.168.55.100` is to `ssh` from your PC to your PC, which likely is not set to accept `ssh`. The address of this interface, _at the Nano side_, is “`192.168.55.1`”. So:  
`ssh 192.168.55.1`

---

<div class="post-metadata">

**Author:** ![praveen.elango](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@praveen.elango](https://forums.developer.nvidia.com/u/praveen.elango)\
**Post date:** [September 14, 2021, 7:54am UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-ssh-problems-works-with-ethernet-but-not-microusb/188882/5 "2021-09-14T07:54:00Z")

</div>

Great, I’ll try this out. Thank you!

---

<div class="post-metadata">

**Author:** ![nadeemm](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/nadeemm/32/367020_2.png) [@nadeemm](https://forums.developer.nvidia.com/u/nadeemm)\
**Post date:** [October 15, 2021, 3:19am UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-ssh-problems-works-with-ethernet-but-not-microusb/188882/6 "2021-10-15T03:19:47Z")

</div>


