LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   To install ZipSlack, and need to remote login in WinXP to the Linux machine (http://www.linuxquestions.org/questions/slackware-14/to-install-zipslack-and-need-to-remote-login-in-winxp-to-the-linux-machine-318518/)

sandugo 04-29-2005 03:40 PM

To install ZipSlack, and need to remote login in WinXP to the Linux machine
 
Currently I have a Win2000 desktop and a WinXP laptop on my network using a router connected to a DSL. I plan to add a linux box (STB1030N set-top-box) running ZipSlack (..for now since I have no FDD and time to make a full install). I have no extra monitor for the linux box... so I have to borrow from my desktop temporarily. Having said that, I need to quikly install the Zipslack and be able to use my laptop to remotely control the linux machine.

My question now are: Is it possible with Zipslack?, If yes, what do I need to configure or install to do this?

thanks.

killerbob 04-29-2005 05:44 PM

Zipslack supports SSH, doesn't it?

If you want X, you'll need to use VNC, because there aren't any free X clients for Windows that support XDMCP.

sandugo 05-01-2005 08:25 AM

thanks for the reply. i've installed zipslack and now figuring out how to install vnc. ...BTW whats the use of ssh. do i need it to run vnc.

Currently i.m looking at tightvnc... seems to have a good review. They have installer for both windows and linux (RedHat). Is this the best way to go? Is there any slack vnc installer?

sandugo 05-01-2005 08:34 AM

Also, no X installed in Zipslack (plain text will do for me now). I just need access to command line. Do i still need vnc?

killerbob 05-01-2005 12:38 PM

If you just want command line, then use SSH. VNC is only useful because it's a free client that lets Windows machines remote control X.

gbonvehi 05-01-2005 01:02 PM

Quote:

Originally posted by sandugo
BTW whats the use of ssh. do i need it to run vnc.

Code:

man ssh
said:
Quote:

ssh - OpenSSH SSH client (remote login program).
If you used telnet sometime well, it's basically the same, it let's you login on your pc using your account from a remote place and use the command-line like if you where working on your pc (can do more things actually, but this is what most users use most).

It's not needed to run VNC, they're different protocols and use different servers/clients.

sandugo 05-01-2005 07:40 PM

In that case I'll try SSH first, which brings me to the question... is it included in zipslack?

I'm really new to the system admin of linux, even though i've been using applications running on UNIX and Linux for years now. So, if you could give me some tips on how to do it the easy way, I'd be very happy . Basically, what I need is to logon remotely to the linux machine (zipslack) from windows XP.

killerbob 05-01-2005 08:08 PM

I'd be surprised if it isn't. I've seen SSH on single floppy distros. Compiled without comments, it takes virtually no space at all.

gbonvehi 05-01-2005 10:09 PM

Yes it ships with it. A good, free and well known SSH client for windows is called Putty, you can get it from: http://www.chiark.greenend.org.uk/~s.../download.html
By the way, you can see which packages you've installed on your machine with pkgtool (select View inside it) or by checking the files in /var/log/packages/.
You can find this and more info in http://slackware.com/book/ (it's a bit outdated but most still applies).

sandugo 05-01-2005 11:24 PM

I guess it is nstalled. i tried to run sshd but got an error..."could not load host key". How do i create this? Also the rsa and dsa keys.

I run ssh localhost and got "Connection refused"

What am i missing here?

gbonvehi 05-01-2005 11:47 PM

Try running the server using this command:
Code:

/etc/rc.d/rc.sshd start
That startup script will autogenerate host keys if they're not created like in your case.
If you want it to be started on boot use this:
Code:

chmod +x /etc/rc.d/rc.sshd
In case you don't want to use the startup script these are the lines the script uses to generate the keys:
Code:

/usr/bin/ssh-keygen -t rsa1 -f /etc/ssh/ssh_host_key -N ''
/usr/bin/ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key -N ''
/usr/bin/ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key -N ''

Oh, be sure it's not running before, type:
Code:

ps -A | grep sshd
If it prints a line then the server is already running.

sandugo 05-02-2005 01:01 AM

I tried it, and it autogenerate the keys. :D :D :D It works. I am now remotely logon to the linux machine using 'root'.... I think its time to create an ordinary account.

THANK YOU!!

Next question: Will it work outside the LAN? I just gave the 192.168.0.102 IP address to connect. I've read from other threads that you need to set up the router to set it to forward something and use Port 22... I dont really understand it. I have a D-link router and I browse the setup but could not find these things.

killerbob 05-02-2005 07:48 AM

Which d-link router?

I had a dl-704p lying around (used it as a print server before switching to CUPS), and on that thing, it's under "Advanced". The d-link configuration page is a bit weird, as it's got options across the top and along the side. Advanced is one of the options across the top.

http://killerbob.ca/lq.org/snapshot1.png

From there, it's pretty easy to set up port forwarding.

sandugo 05-02-2005 09:16 AM

Thanks for the response. I think I have the same setup menu. But I have to be honest I know nothing about these things. So, I assume I need to click 'Enabled' and need to enter any name in the 'Name' field. How do I know the IP address (my router is connected to a DSL-sympatico)?, and the Private and Public Ports, should I enter '22' to both? ... And which Virtual Server List to activate?

I'm at the office so I won't be able to try these until the evening (I didn't know how to activate the remote admin of the router). thanks again.

killerbob 05-02-2005 11:05 AM

If you've got the same setup, then it's fairly simple...

For "name" that doesn't really matter. Put something like "ZipSlack SSH" so you know what it is without having to read the whole thing a year from now.

For IP address, that's the *internal* IP address of your box. 192.168.0 (this far you shouldn't be able to change) .102.

For port, put 22 on both of them.

For "schedule", you can put "always", or you can set it so it's only available while you're at work by setting up the schedule accordingly.

For everything else on the bottom, you don't need to check them. They're there as examples, more than anything else.


And as for knowing your IP address, shitpatico has a habit of changing your IP address, and last time I looked at them, they didn't offer static IP addresses. You'd have to pay more for a static anyway. Probably the easiest and cheapest way to get around this is to register at http://dyndns.org ... they give out free subdomains, so you could have sandugo.dyndns.org. The d-link router supports updating to dyndns and it'll take care of your IP address all the time. That way, you just have to SSH to ssh://sandugo.dyndns.org:22. Under "Advanced", click on "DDNS" to set it up.


gl.


All times are GMT -5. The time now is 01:58 AM.