SSH connection ok using windows but not with Linux

English Network/Internet
#1

Hi there,

I’ve being trying to connect from an Opensuse client to a Opensuse Server (both version 11) using SSH, although, after typing login name and password (root or any other normal user recorded on the server) the shell environment stays frozen and I can’t even use CTRL+C to release it.

I tried deactivate firewall, and restart the sshd daemon.
When I type lsof -i:ssh, i get:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sshd 2770 root 3u IPv6 7864 0t0 TCP *:ssh (LISTEN)
sshd 2770 root 4u IPv4 7866 0t0 TCP *:ssh (LISTEN)
ssh 4094 root 3u IPv4 14373 0t0 TCP 192.168.1.200:21951->192.168.1.202:ssh (ESTABLISHED)

The last line shows the case when i log on and the shell gets frozen right after typing the password.

p.s.: If I use windows client (e.g putty software) to connect to the Opensuse server via ssh it goes fine.

Any advice?

Thanks

#2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well considering your symptoms I’d get a LAN trace to see if anything
funky was happening from both sides… see if perhaps a packet is
getting dropped at an inopportune time in one case and not the other.

Good luck.

caop wrote:
> Hi there,
>
> I’ve being trying to connect from an Opensuse client to a Opensuse
> Server (both version 11) using SSH, although, after typing login name
> and password (root or any other normal user recorded on the server) the
> shell environment stays frozen and I can’t even use CTRL+C to release
> it.
>
> I tried deactivate firewall, and restart the sshd daemon.
> When I type lsof -i:ssh, i get:
>
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> sshd 2770 root 3u IPv6 7864 0t0 TCP *:ssh (LISTEN)
> sshd 2770 root 4u IPv4 7866 0t0 TCP *:ssh (LISTEN)
> ssh 4094 root 3u IPv4 14373 0t0 TCP
> 192.168.1.200:21951->192.168.1.202:ssh (ESTABLISHED)
>
> The last line shows the case when i log on and the shell gets frozen
> right after typing the password.
>
> p.s.: If I use windows client (e.g putty software) to connect to the
> Opensuse server via ssh it goes fine.
>
> Any advice?
>
> Thanks
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI9oA03s42bA80+9kRAj2WAKCATLbL8TyXv93UbxmMJuHhc2L4/gCdFEhT
OGPP+oVYokavZSdlv/9XOaw=
=ZzbJ
-----END PGP SIGNATURE-----

#3

Hi,

On the suse client, where are you initiating the ssh connection from ? console or gui app ?

If you issue something like: ssh root@serverip from the console.
You enter the password and it hangs, correct ?

if you ssh from the server to itself work ok ? i.e. ssh localhost

If it does then sshd is ok.

You say you have deactivated the firewall, did you do this for both client and server while testing ?

ta
J

#4

Along the lines of what tuxituk is saying, does it happen with multiple accounts when logging in? Say, what happens if you create a new user and log in with that account.

It is strange that putty seems to have no issue.

#5

Without the additional info requested I would hazard a guess at packets being dropped.

I’m intrigued now. lol!

#6

On the suse client, where are you initiating the ssh connection from ? console or gui app ?

I’ve been trying through shell environment. But I also tried through nautilus.

If you issue something like: ssh root@serverip from the console.
You enter the password and it hangs, correct ?

Exactly.

if you ssh from the server to itself work ok ? i.e. ssh localhost

If it does then sshd is ok.

Doing this on both client and server works ok.

You say you have deactivated the firewall, did you do this for both client and server while testing ?

Yes, I did. I deactivated the service from running at boot time aa well (on both machines).

does it happen with multiple accounts when logging in?

I tried without any user logged in on the server and also the opposite.

what happens if you create a new user and log in with that account.

I did that but also gets the same problem.

I’m intrigued now.

And so am I.

It’s pretty annoying 'cause when it gets stuck it is not possible to release the console/shell using CTRL+C , I have to reboot or kill the process.

Thanks fellas for the attention.

#7

Hi
Have you tried a packet capture (wireshark or tcpdump) to see what is
happening?

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.16-0.1-default
up 12:05, 2 users, load average: 0.07, 0.11, 0.09
GPU GeForce 6600 TE/6200 TE - Driver Version: 177.80

#8

I finally figured out the problem, not the solution though. It happens when I’m using the wireless on my laptop. If I use wired connection ssh goes fine. But there’s a mystery yet 'cause using wireless on windows Vista (installed on the same laptop on dualboot) (via putty software) the ssh connection doens’t have any problem connecting to the opensuse server machine.

Does someone know why it happens?

For me it’s preferable to use the wireless connection.

ps.: i haven’t tried to use ssh connection from a different network yet.

#9

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wild guess… a firewall in vista is causing the problem. To prove or
disprove get a LAN trace or find a way to turn up the logging levels in
SSH’s server and client as high as possible.

Good luck.

caop wrote:
> I finally figured out the problem, not the solution though. It happens
> when I’m using the wireless on my laptop. If I use wired connection ssh
> goes fine. But there’s a mystery yet 'cause using wireless on windows
> Vista (installed on the same laptop on dualboot) (via putty software)
> the ssh connection doens’t have any problem connecting to the opensuse
> server machine.
>
> Does someone know why it happens?
>
> For me it’s preferable to use the wireless connection.
>
> ps.: i haven’t tried to use ssh connection from a different network
> yet.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJBjJd3s42bA80+9kRAt+mAJ4sL5gAJK5qRip/7WEHRYR+PyL9qQCfcFV2
/uC4JUiwr7UO7rjhIu6mtWc=
=wgZn
-----END PGP SIGNATURE-----

#10

Try using konqueror’s ‘fish’ protocol to connect. I’m curious if a different client has the same issue.

fish://username@server

Is there a timeout option with ssh?