Lacking prior experience with NX, I initially found the product matrix confusing: there are free downloads for NX Free Edition, NX Server, NX Node, NX Client, NX Server Manager, NX Web Companion, and NX Builder. You can download several varieties of NX software from. NX 3.0 has some interesting advantages over similar products - but also some pitfalls for inexperienced users. and your password, you should be at a remote prompt.) The local port 5902 is forwarded to remote port 5901 so you would point your local client at port 5902.NoMachine recently released version 3.0 of its remote desktop product line. I'm not seeing the error? Note that vncserver :1 is run on the remote side (probably should have made that clearer-if you typed ssh. and your password, you should be at a remote prompt.) The local port 5902 is forwarded to remote port 5901 so you would point your local client at port said: ssh -L5902:localhost:5901 I also find that I frequently use different local and remote ports sometimes for organizational reasons, sometimes because the local port is already in use. You are correct that many would use the same port for simplicity sake, but I wanted to use different ports in hope that my Putty example would be less confusing. In fact, to keep it simpler, why not use 5901 for both the source and the destination port? In other words: -L 5901:localhost:5901 (start your vnc client and point it to localhost: 5902)īased on your example, the second instance of 5902 should be 5901. Ssh might also have an advantage because (other than ssh itself, which has seen a lot of "trial by fire") your remote services are typically only running while you are connected or only accessible from the local network or even just said: ssh -L5902:localhost:5901 A VPN is set and forget, but typically takes a lot more upfront time to configure and debug. Someone else mentioned using a VPN, which is totally valid, but personally I find it easier to make a quick ssh connection with only the ports that I need. Has a built in Xserver, which is great for quick little things like xfe &, but don't expect to watch video on an xclient running over a network-even a local network.) (MobaXterm is excellent as well, but for some reason they separate tunnels from the terminal connection. it doesn't have an ssh server or external port.) Also note that you type vncserver :1 on the remote after you are logged in. Note that Destination is relative to the remote host and it is also common to use the ssh connection to one machine as a gateway to another machine on the same network, if i.e. (To configure the local forwarding in the putty UI, go to Connection\SSH\Tunnels Source port is the local port (5902 in the above) and Destination is host:port (the localhost:5901 from above.) Putty (terminal emulator/ssh client) and it's related programs are quite usable in a Windows environment. (start your vnc client and point it to localhost:5902) (enter your password - unless you use ssh-keygen, pagent, etc.) (Although Nomachine and x2go already use ssh/encryption by default.) Using ssh, with a local port forward, to start up a vnc session and connect to said vnc session is going to be much more secure than vnc by itself, for example. Windows, Linux, rdp, vnc, whatever, be careful exposing any remote access to the internet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |