Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I use a rather unpopular solution. A few of my servers are windoze (unfortunatelly). They are running a Remote Administrator programme (which is a commercial one). It is a really good server/client programme but it doesnt run on Linux. Fortunately it runs perfectly using winex (which is commercial too - damn), but you could try WINE which is free. This solution lets me do the job both ways. See Windows from Linux and vice versa.
You can achieve the same results by installing tightvnc on your windoze boxes, then running the tightvnc server in 'Listen' mode. On the Linux side you can use the tightvnc viewer or the Remote Desktop app to get your remote windoze desktops in Linux. Works a treat :-)
Cygwin X will let you do an ssh session with X forwarding.
Install Cygwin, download PuTTY, execute xinit from Cygwin bash, execute PuTTY from the shell there enable X forwarding, and you should be good. From there (the PuTTY shell) you can "startkde &" or "gnome-session &" or "(whatever you do to start your window manager) &", and you have a *nix GUI on windows. Congratulations.
You can also use this program, called PuTTY. Just type the IP address to connect to, set it to SSH on port 22 (you can also use different protocols if you want, but as far as I know they're all worse.)
You'll also need to enable X11 forwarding under the SSH properties.
You should be able to get the program at these sites:
There is SSH with X forwarding. You need an X server to use X forwarding. The main X servers on Windows are Cygwin/X (the X server in Cygwin) or Xming (the same X server but without Cygwin). Keep in mind that X is REALLY slow over the Internet. Enabling compression on the SSH connection helps a little, but not much. Also, keep in mind that you are forwarding X to the local X server, so you may not be able to get a "desktop" environment since it may conflict with the local one.
VNC allows you to get a desktop. Also, it is usually faster than X because it can perform compression. The main implementations of VNC are RealVNC and TightVNC. You may want to tunnel VNC traffic over SSH for security.
Another technology that is much, much faster than X and VNC is NX, which gives near local speeds over really slow connections like modems. It also includes SSL encryption. There is FreeNX server for Linux. I use this to connect to my machine from home.