Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
How do I get my tower system to see my netbook using Mandriva 2010 & Gnome on both machines. When I click the Network in Nautilas, and choose the netbook, I get "server refuse to connect message".
I also have an imac with osx and the tower connects to the imac without problems. Am I missing some software for this?
When I tried ssh into the netbook I get "refuse to connect". Both PC machines have the ssh-server & client installed. Pinging both machines work.
the only idea: ssh is down?
connection refused means there is no service running on port.
do netstat -antp | grep :22 at your netbook and see if it listens.
optionally try connecting other port if you run something else there(for instance webserver listening tcp port 80) and see if it also refuses connection, that will tell then that wireless connection not working as expected.
Run "sudo /sbin/chkconfig sshd" on the server to see if the ssh daemon is running.
Check the permissions of your home directories and your ~/.ssh directories. They can't be world readable.
Check your /etc/ssh/sshd_config settings. After fresh installing a new distro, I had a problem connecting. The problem is that my "AllowUsers" configuration entry had my hostname instead of the hostname.domainpart that was in /etc/hosts. Using ssh user@host.domain worked.
To double check connectivity, try "telnet hostname 22". If you see something like:
telnet hpmedia 22
Trying 192.168.1.101...
Connected to hpmedia.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.2
Then the service is running. If you can't connect, look at your firewall settings.
Try "ssh -vv user@host". This will print debug information.
Last edited by jschiwal; 11-21-2009 at 05:05 AM.
Reason: typo fix
good advice but anyway "connection refused" is "connection refused", telling us there is no actual service on port so there may be three reasons for that:
1. network link is broken... in a real weird way but since it's wireless this is not so weird;
2. no SSHd running on netbook;
3. SSHd runs on other port! see what jshiwal suggests. ssh user@host -p <PORT> or telnet host <PORT> or nc host <PORT>(netcat, additional utility not in standard utils list) with port 22 will tell for sure. If sshd is really running on port 22 then there must be something with link, it can't be other way. i give up if it is. ^_^
I checked mandriva control center and it seems sshd was not started on both the tower & netbook, so I started them.
I did uncomment port 22 and added the IP addresses to both machine's /etc/ssh/sshd_config
Below is from netbook
[ghostdawg@localhost ~]$ netstat -antp | grep :22
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
[ghostdawg@localhost ~]$ su -
Password:
[root@localhost ~]# netstat -antp | grep :22
[root@localhost ~]#
This is using the tower. When I use nautilas to access the imac, which will connect using nautilas, then I type the netstat command, I get information.
what are the results of testing this on other port/testing other service with telnet? did you restart sshd service after config update?
the general rule is to provide as more information as possible. paste of sshd_config would be in place.
--
upd:
2 jschiwal: yeah, right. but configuration of firewall that rejects(TCP*RST) not drops packets is for advanced needs and usually made by hand =) so we'd already knew about it from FredGSanford.
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin
# 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 change a
# default value.
Port 22
#AddressFamily any
ListenAddress 192.168.1.107
#ListenAddress ::
# Disable legacy (protocol version 1) support in the server for new
# installations. In future the default will change to require explicit
# activation of protocol 1
Protocol 2
# 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
# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024
# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO
# 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 yes
# 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 no
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin
# 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 change a
# default value.
Port 22
#AddressFamily any
ListenAddress 192.168.1.102
#ListenAddress ::
# Disable legacy (protocol version 1) support in the server for new
# installations. In future the default will change to require explicit
# activation of protocol 1
Protocol 2
# 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
# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024
# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO
# 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 yes
# 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 no
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.