ssh conection refused

ginobvhc · 2012-08-11 21:55:22

Hello!!
i have read the post of this forum trying to found a solution to this problem

i try to set up a ssh server but i got the follow error

$ ssh -vvv  ginobvhc@181.95.***.***
OpenSSH_6.0p1, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 181.95.***.*** [181.95.***.***] port 22.
debug1: connect to address 181.95.***.*** port 22: Connection refused
ssh: connect to host 181.95.***.*** port 22: Connection refused

i also try changin the port to 2222 but i have the same problem

cat /etc/ssh/ssh_config
#	$OpenBSD: ssh_config,v 1.26 2010/01/11 01:39:46 dtucker Exp $

# This is the ssh client system-wide configuration file.  See
# ssh_config(5) for more information.  This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.

# Configuration data is parsed as follows:
#  1. command line options
#  2. user-specific file
#  3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# Site-wide defaults for some commonly used options.  For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.

Host *
#   ForwardAgent no
#   ForwardX11 no
ForwardX11 yes
#   RhostsRSAAuthentication no
#   RSAAuthentication yes
#   PasswordAuthentication yes
#   HostbasedAuthentication no
#   GSSAPIAuthentication no
#   GSSAPIDelegateCredentials no
#   BatchMode no
#   CheckHostIP yes
#   AddressFamily any
#   ConnectTimeout 0
#   StrictHostKeyChecking ask
#   IdentityFile ~/.ssh/identity
#   IdentityFile ~/.ssh/id_rsa
#   IdentityFile ~/.ssh/id_dsa
#   Port 22
#   Protocol 2,1
#   Cipher 3des
#   Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
#   MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
#   EscapeChar ~
#   Tunnel no
#   TunnelDevice any:any
#   PermitLocalCommand no
#   VisualHostKey no
#   ProxyCommand ssh -q -W %h:%p gateway.example.com
Protocol 2,1

cat /etc/ssh/sshd_config
#	$OpenBSD: sshd_config,v 1.84 2011/05/23 03:30:07 djm Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options override the
# default value.
#Port 2222
Port 22
#AddressFamily any
ListenAddress 0.0.0.0
#ListenAddress ::

# The default requires explicit activation of protocol 1
Protocol 2,1

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
LoginGraceTime 120
#PermitRootLogin yes
PermitRootLogin no
#StrictModes yes
MaxAuthTries 2
#MaxAuthTries 6
#MaxSessions 10

#RSAAuthentication yes
#PubkeyAuthentication yes

# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
# but this is overridden so installations will only check .ssh/authorized_keys
#AuthorizedKeysFile	.ssh/authorized_keys

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# Set this to 'yes' to enable PAM authentication, account processing, 
# and session processing. If this is enabled, PAM authentication will 
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
#UsePAM yes

AllowAgentForwarding yes
AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /run/sshd.pid
#MaxStartups 10
#PermitTunnel no
#ChrootDirectory none

# no default banner path
Banner none
#Banner /etc/issue
# override default of no subsystems
Subsystem	sftp	/usr/lib/ssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#	X11Forwarding no
#	AllowTcpForwarding no
#	ForceCommand cvs server
AllowUsers ginobvhc

$ ps aux | grep ssh
root     12885  0.0  0.0  41996  1436 ?        Ss   18:38   0:00 /usr/sbin/sshd
ginobvhc 13667  0.0  0.0   3080   184 pts/2    D+   18:55   0:00 grep --color=auto ssh
ginobvhc 24898  0.0  0.0  15028   160 ?        Ss   14:58   0:00 /usr/bin/ssh-agent -s

i cant set up this server ans i really need
Sorry my bad english :S

dschrute · 2012-08-11 22:21:36

Anything in /etc/hosts.deny or /etc/hosts.allow ?

ginobvhc · 2012-08-11 23:47:59

#
# /etc/hosts.allow
#
#rpcbind: 192.168.0.100/255.255.255.255

sshd: ALL

# End of file

#
# /etc/hosts.deny
#

ALL: ALL

# End of file

cat /etc/host.conf 
#
# /etc/host.conf
#

order hosts,bind
multi on

# End of file

ginobvhc · 2012-08-11 23:52:31

also nmap-online.com

22/tcp open ssh

but still
and
tryin to conect from my public ip

$ ssh ginobvhc@*.*.*.*
 ssh: conect to host *.*.*.* port 22: conection refused

but whe i try to conect to localohst, 127.0.0.1 or 192.1.1.4 (internal ip)
nothing goes wrong :S

but i need to conect from outside

skunktrader · 2012-08-11 23:56:53

/etc/hosts.deny and /etc/hosts.allow are no longer used
http://www.archlinux.org/news/dropping- … s-support/

If you are using a router, have you forwarded port 22 (or 2222) to to your machine?

ginobvhc · 2012-08-12 00:24:05

ohhh i didn't know about hosts.*
how should i can allow my ssh?

yes i forwarded both 22 and 2222

tomk · 2012-08-12 00:49:10

Check the server's logs for clues.

.:B:. · 2012-08-12 00:59:50

Is your server behind a router? If so, make sure the SSH port is forwarded.

ginobvhc · 2012-08-12 01:25:59

i hope you can understand spanish or maybe can interpret the img

tomk wrote:

Check the server's logs for clues.

did you mean

grep -Ri /var/log/*

??

-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

tomk · 2012-08-12 08:32:03

I meant what I said, so I'll say it again in a different way:

Read your logs, looking for any entries that match the time of your connection attempt. The 'tail' command can be useful for this.

ploub · 2012-08-13 11:14:22

@OP: Any luck with your ssh server yet? I'm trying to do exactly the same thing, port 22 is open in the router, but always connection refused via internet. I can ssh in from the LAN, and nothing relevant in logs. I'm sure I'm overlooking something really obvious...

Zancarius · 2012-08-13 22:28:02

ploub wrote:

@OP: Any luck with your ssh server yet? I'm trying to do exactly the same thing, port 22 is open in the router, but always connection refused via internet. I can ssh in from the LAN, and nothing relevant in logs. I'm sure I'm overlooking something really obvious...

Open != forwarded.

If you're attempting to connect from off-network, you must make certain that the port isn't simply open, it must be forwarded to the IP address of the machine you wish to connect to. It helps to set the target machine to use a static IP address.

If you're uncertain how to forward the port or your router's manual isn't very clear, this site can often be helpful.

Arch Linux

#1 2012-08-11 21:55:22

ssh conection refused

#2 2012-08-11 22:21:36

Re: ssh conection refused

#3 2012-08-11 23:47:59

Re: ssh conection refused

#4 2012-08-11 23:52:31

Re: ssh conection refused

#5 2012-08-11 23:56:53

Re: ssh conection refused

#6 2012-08-12 00:24:05

Re: ssh conection refused

#7 2012-08-12 00:49:10

Re: ssh conection refused

#8 2012-08-12 00:59:50

Re: ssh conection refused

#9 2012-08-12 01:25:59

Re: ssh conection refused

#10 2012-08-12 08:32:03

Re: ssh conection refused

#11 2012-08-13 11:14:22

Re: ssh conection refused

#12 2012-08-13 22:28:02

Re: ssh conection refused

Board footer