Hi Guys
I am not able to ssh to my serve anymore any ides as to how to resolver this problem


example:-
:~>ssh 192.168.0.100 -p 222 -1 root

No response received or time out

Cnt C and exit

:~>
Can any one help her please.

System
AMD D/Core
2 G Ram

Is ssh running on port 222 (the standard is 22, but I assume you know that since you are specifying 22) on that system? Is a firewall blocking port 222 between your system and that one (including either end)?

Forrest

how about doing a netstat or lsof and see if its listening on port222?thats the first i do in such cases.

Hi Forrest
Thanks for getting back to me, I have tried both and this is the result for p 22

ssh 192.168.0.100 -p 22 -1 root
Protocol major versions differ: 1 vs. 2

How do i check if the firewall is blocking this connection? and to how to make any changes?
Thanks

Hi kdelover
carried out your suggestion as above and checked to see if i can see port 222 or 22 this is no where to be found on the list only 5 dig and 4 dig port numbers.

OK, you are getting a response from the server on port 22. It is complaining though since you are trying to force a ssh version 1 type connection (most ssh servers are configured to no longer accept these insecure connection types). You may still not be able to connect as root is also often blocked from ssh connections by the server. You should just be able to run "ssh root@192.168.0.100" and connect if root is allowed. If not, you will need to log in w/ a different user and then become root.

HTH

Forrest

Try without -1:

Ok. Forrest
Tried your suggestions still no access, reply below
also w/ - not sure if i have used this correctly

:~> su
Password:
# ssh root@192.168.0.100
ssh: connect to host 192.168.0.100 port 22: No route to host
# w/
bash: w/: No such file or directory
# exit

thanks

Thanks hua

point noted, i have tried your suggestion also but failed no access

Thanks anyways

This means that something is wrong with your IP.

It seems that there are some basic network problems.
1. What is the OS on the desktop from which you are trying to connect to the server? Have you access to the server locally (monitor, keyboard)?
2. You need to know that your network configuration is valid on both PCs.ifconfig should tell you the IP settings (if your desktop is SUSE).
3. Then you need to find if you can see the server IP. You can ping it but sometimes it does not work. In this case portscan can help.
4. You need to know on what port the server listens for ssh. I usually use portscan if I don't know such things.
BUT BE CAREFULL:
If you are on your own network and the server is yours there should be no problem. I use nmap fo portscan but thats on slackware - On suse I don't know. Some suse users can post that for you.
Or you can guess the port.
When you know the IP and the port of ssh - use the command:
ssh <ipaddress> -p <port>

Hi Hua
1. Currently running Suse Linux 11.1 with KDE 4.3 with (QT 4.5.2 not sure if this may be my problem since migrating from Qt4.43)
I can only access the server through Xp no problem but bot linux and locally keyboard.
2. on my Pc ipconfig shows only the following my ip address eth0 and

lo loopback 127.0.0.1
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:519 errors:0 dropped:0 overruns:0 frame:0
TX packets:519 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20081 (19.6 Kb) TX bytes:20081 (19.6 Kb)
This is the only issue i see is this correct to have as many errors as this

3. Used Angry IP Scanner confirm ip address is there and can be seen
NEWS
Just tried Angry IP Scanner and ssh to the server no problem - did not know this. However it dos not show a port - but it will do for the time being untill we can get to the bottom of this issue.

4. Used nmap confirm port is 22 for ssh
PORT STATE SERVICE
22/tcp open ssh

RESOLVED - It Works- It works - it works -

# ssh 192.168.0.100 -p 22
The authenticity of host '192.168.0.100 (192.168.0.100)' can't be established.
RSA key fingerprint is xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.100' (RSA) to the list of known hosts.
Password:
Last login: Fri Aug 28 23:32:23 2009 from 192.168.0.200
Have a lot of fun...
#


Many Thanks hue

if i was her i would take you for a pint man.

Thanks again for your help you are a major Guru man.

I am happy to see it works. Just a little detail - If your ssh runs on port 22 (default) you don't need to specify the port just use:
ssh 192.168.0.100

Have fun

Many Thanks Hua

I believe your problem was how you were trying to pass the username. It's -l not -1, that is l for login not the number 1. However their is an alternative way to pass this by doing user@domain what the command can also handle. As you have said above -1 enforces ssh protocol level 1 (what is generally not used anymore)

ie
ssh root@192.168.0.100
is a valid way to attempt to login as root at 192.168.0.100.

Point noted r3sistance
Many Thanks for that adding to my notes