In Linux it is easy to see a log of what happens when you plug in the USB to see why the network is or is not working.
It is a simple security thing that you might need to somehow tell Windows that it is ok to use that device and to set up that network even if everything is otherwise 100% correct. However, Windows (and Linux and most every operating system) has the possibility that it won’t accept the USB network device with the address of 192.168.55.1. Going back to the actual problem, ssh will work with Windows if you have the network route. The whole point of going through that is that if you only need text-based command line it is really simple to do with ssh, but if you need a graphical tool, then you have multiple options and you might ask based on your specific case/situation the best way to work via a remote computer.
X with ssh forwarding forwards events, whereas a virtual desktop runs everything on the Jetson and a program basically copies the desktop to another computer, and you’d need that separate client, but it would also become independent of operating systems so that Windows could have the Linux desktop, or Mac could, and it would be much easier than normal remote work (setting up a virtual desktop server though is more involved than simply forwarding through ssh).
Or you could install virtual desktop software. If you don’t have an X server to forward to, then you’d need to run the app on the Jetson’s local display.
You could run several such applications from several Linux systems and have them bring up display on your single host computer as if they were all running there. Ssh -Y if you open a GUI application, e.g., gimp (which is a great graphical artist tool), the Jetson would be running Gimp, but the graphical display would magically appear on the local Linux X server.
You can’t forward to Windows unless you’ve set up an X server with some sort of Linux emulation, e.g., WSL2, but if this were Linux, then with no monitor on the Jetson, you could connect like this (assuming name is “ubuntu” and IP is 192.168.55.1):
The reason it matters is that using ssh means you can forward the events to your local computer, and have it run those events. X has an interesting ability you won’t find in Windows: It works by seeing “events” (such as a mouse click or movement), and then the server interprets that to display it. Nowadays there has been development of Vulkan, which will likely one day replace X, but is now often used basically as a plug-in to X. So one can completely change the GUI environment login feel without actually needing a new X server.
The look and feel are a separate program, the desktop manager. With Windows you would typically be married to graphical with no ability to “partially but normally boot” and have text only (which is useful when updating graphics or debugging graphics since you can do so on Linux without rebooting the system…you can reboot just graphics).įor a long time the program providing graphics is the X11 protocol “X server”. Linux boots up in stages, and one stage is for text entry only (“multi-user.target” in the program controlling this), another is graphical (“graphical.target”). The graphical environment in Linux is actually a separate program on top of the running operating system. Some background might be useful to you (not necessarily needed here, but you’ll find it useful in the future, don’t read this as a solution)…