(ESshFatal) Network error: Connection refused

Advertisement

kaicho
Joined:
Posts:
3

(ESshFatal) Network error: Connection refused

Since installing new ISP (went to dsl from cable) and their dsl modem in front of my old router, all my NAT stuff went to "reserved IP" settings, and I forwarded ports to the web servers. This linux box pings ok and was not changed, but now WinSCP does not succeed in connecting.

What I've done:

On the server I executed
ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key
ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key
I thought this might return me to the "not cached" message in WinSCP, but no effect. I did not try copying public/private keys between computers. I did not use puttygen.

I suspect this problem is something stupid in the NAT. I have root and two user permissions on the server, gentoo linux. This log is identical when I log in as a user instead of 'root':

. Session name: root@192.168.0.5
. Host name: 192.168.0.5 (Port: 22)
. User name: root (Password: Yes, Key file: No)
. Transfer Protocol: SFTP
. SSH protocol version: 2; Compression: No
. Agent forwarding: No; TIS/CryptoCard: No; KI: Yes
. Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. Ping interval: 60 sec (0 = off); Timeout: 30 sec
. SSH Bugs: -,-,-,-,-,-,-,-,
. Proxy: none
. Return code variable: Autodetect; Lookup user groups: Yes
. Shell: default, EOL: 0
. Local directory: default, Remote directory: home, Update: No, Cache: Yes
. Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. --------------------------------------------------------------------------
. Looking up host "192.168.0.5"
. Connecting to 192.168.0.5 port 22
. Attempt to close connection due to fatal exception:
* Network error: Connection refused
. Closing connection.
* (ESshFatal) Network error: Connection refused

TIA
"Obsolete power corrupts obsoletely" -T H Nelson

Reply with quote

Advertisement

Guest

Re: (ESshFatal) Network error: Connection refused

"messages" indicates my login from that machine's keyboard, but nothing about any other attempt to log in. I don't know where any other logs are, if they exist.

I can access the webpages on that box in the normal way, and ping it both from LAN and WAN addresses. Router has open port 80 and port 22.

Reply with quote

Advertisement

You can post new topics in this forum