Help setting up an X server and SSH on windows
I have slackware setup so I can SSHin using Putty... this works great for administrative stuff, but I'd id like to be able to get my KDE desktop over SSH using some sort of X-Server... I havent found any solid how-to's or tutorials that walk you through this... can anyone give me a hand please?
|
The standard way is to run something like Exceed (pay) or CygWin/X (free) on your Windows box.
I would recommend looking at FreeNX however. It's a heck of a lot faster. Running X remotely is slow, and pretty much requires LAN speeds to be at all useable. Free Windows client availabe from: http://www.nomachine.com/ Free Linux Server: http://freenx.berlios.de/ |
Ugh thats so disheartening since my work connection sucks
I did try cygwin but lemme tell you... that did nothing for me... I couldnt figure out a damn thing nor could i find much documentation that did a whole more than confuse me all im really looking for a is a rich text editor...i dont mind using pico, but its a pain in the ass to develope with... moving code blocks, syntax hilighting and all that stuff... unless im oblivious to a good shell editor that is a little richer than the ones that come with slackware |
This is actually not a linux question, but...
There are no free X servers for Windows that I know of. You could try running X.org or Xfree86 under Cygwin, but my experience with that was less than ideal. The other alternatives are feeware: Excede from Hummingbird Software, X-Win32 (may be a newer name than that now). There are probably others. I have used Excede for years, and I found it to be a good package. --- rod. |
Quote:
--- rod. |
Quote:
|
Quote:
|
As I reread your original post, I can't tell exactly what your setup is. Are you running Slackware at home and want to edit files hosted on some Linux/Unix server at work via an Internet connection? I initially assumed you were running Windows at home and were trying to access a Slackware server at work (since you mentioned putty - why would you need that at home if you're running Slackware?)
If you are running Slackware at home, full featured editors you probably already have installed there are vi and emacs. If not, they should be easy to install. Both come with a rather steep learning curve and are not GUI-based. These would probably also be installed on your work target Linux/Unix server as well. If you are running Slackware at home (please tell us specifically what your setup is), then rather than running X over the Internet (yeuch - SLOW!) you could use sshfs to mount your remote server to your home box (no setup on the server end - good!) and then do all your editing locally on your Slackware box. |
@ Home:
Slackware 10.2 Server --desktop shared internally to my workstations IP only --htdocs shared with samba to one user on my workstation Windows XP SP2 workstation --use desktop via RealVNC --use PuTTY for CLI access --htdocs edited over local network @ Work I currently use PuTTY to remote home to make any changes to stuff but would like a better remote editing environment... I'll have to look into the FTP server and set my router up accordingly and then use UE32 from work... unless there is a better solution |
an other option you have is to install VIM on the windows box, install winSCP on the windows box and do things that way.
winSCP is a GUI scp tool for windows that looks and acts a lot like cuteFTP. so no need to run the risk of opening up FTP when you can stay behind the more secure ssh/scp for moving files back and forth between linux and windows. then once you have the file moved, just edit it with vim and send it back. as long as the files are not HUGE you should be ok. |
i just use vim via ssh though *grins*, but im no coder and only do limited html work.
|
You didn't say what you're running at work. Is that a Windows box?
Also, when you "remote home" are you remoting into your Slackware box, or do you need to remote to your Windows box too? I would recommend against setting up an ftp server at home. ftp is not secure or encrypted. If you can very tightly setup a firewall or router at home to limit access to this ftp server to ONLY your computer at work - MAYBE. But it's best to never go back to the old unsecure protocols - telnet, ftp, any of the "R" commands (rlogin, rsh, rcp), etc. Setting up an ftp server accessible over the general Internet is akin to bending over to pick up your dropped soap bar in the prison shower room. You never want to put yourself in that unprotected position! |
Moved: This thread is more suitable in General (as it's really a Windows question) and has been moved accordingly to help your thread/question get the exposure it deserves.
|
All times are GMT -5. The time now is 04:34 PM. |