Network Error Connection Refused Ssh Centos
Contents |
2nd NIC - "Network Error: Connection Refused" Issues related to configuring your network Post Reply Print view Search Advanced search 10 posts • network error connection refused putty Page 1 of 1 Klio Posts: 4 Joined: 2012/05/24 18:06:48 SSH Access
Putty Network Error Connection Timed Out
from 2nd NIC - "Network Error: Connection Refused" Quote Postby Klio » 2012/05/24 18:13:47 Hello,Firstly I'm a Windows
Putty Connection Refused Windows 10
admin a few months into CentOS so excuse me if this is a simple issue.I've got a server with 2 NIC on different ranges:192.168.0.245192.168.100.245I can view web pages served
Putty Network Error Connection Refused Raspberry Pi
by the server over both IP Addresses.I can SSH into the server from the 192.168.100.x network to server address 192.168.100.245I cannot SSH into the server from the 192.168.0.x network to the server address 192.168.0.245, I get the simple error: "Network Error: Connection Refused".I'm using IP Tables and this is the result of iptables -L --line-numbers:Chain INPUT (policy ACCEPT)num target putty network error software caused connection abort prot opt source destination1 RH-Firewall-1-INPUT all -- anywhere anywhereChain FORWARD (policy ACCEPT)num target prot opt source destination1 RH-Firewall-1-INPUT all -- anywhere anywhereChain OUTPUT (policy ACCEPT)num target prot opt source destinationChain RH-Firewall-1-INPUT (2 references)num target prot opt source destination1 ACCEPT all -- anywhere anywhere2 ACCEPT icmp -- anywhere anywhere icmp any3 ACCEPT esp -- anywhere anywhere4 ACCEPT ah -- anywhere anywhere5 ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns6 ACCEPT udp -- anywhere anywhere udp dpt:ipp7 ACCEPT tcp -- anywhere anywhere tcp dpt:ipp8 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED9 ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:smtp10 ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:http11 ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:https12 ACCEPT tcp -- 192.168.100.0/24 anywhere state NEW tcp dpt:netbios-ssn13 ACCEPT tcp -- 192.168.100.0/24 anywhere state NEW tcp dpt:microsoft-ds14 ACCEPT tcp -- 192.168.100.0/24 anywhere state NEW tcp dpt:mysql15 ACCEPT tcp -- cpc1-woki6-2-0-cust932.6-2.cable.virginmedia.com anywhere tcp spts:1024:65535 dpt:ssh state NEW16 ACCEPT tcp -- 188-39-44-176.static.enta.net/28 anywhere tcp spts:1024:65535 dpt:ssh state NEW17 ACCEPT tcp -- 192.168.100.0/24 anywhere tcp spts:1024:65535 dpt:ssh state NEW18 ACCEPT tcp -- 192.1
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any putty connection refused raspberry pi questions you might have Meta Discuss the workings and policies of putty network error connection refused windows 10 this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers network error connection refused gns3 or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and http://www.centos.org/forums/viewtopic.php?t=27036 developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How to solve 'Connection refused' errors in SSH connection? up vote 50 down vote favorite 14 I have an Ubuntu Server http://askubuntu.com/questions/30080/how-to-solve-connection-refused-errors-in-ssh-connection 10.10 32-bit in my home. I'm making SSH connections to it from my PC via Putty. The problem is, sometimes I'm able to login seamlessly. However, sometimes it gives me an error like this: Network error: Connection refused. Then, I dont't change anything, try to login a few times more, wait a while and try again. Sometimes I can log in, sometimes I cannot. It seems pretty random to me. What can I do to solve this? Edit: And Sometimes, Putty gives Network error: Software caused connection abort error after displaying login as: text. Here is the ping -t output: Pinging 192.168.2.254 with 32 bytes of data: Reply from 192.168.2.254: bytes=32 time=6ms TTL=64 Reply from 192.168.2.254: bytes=32 time=65ms TTL=6 Reply from 192.168.2.254: bytes=32 time=88ms TTL=6 Reply from 192.168.2.254: bytes=32 time=1ms TTL=64 Reply from 192.168.2.254: bytes=32 time=3ms TTL=64 Reply from 192.168.2.254: bytes=32 time=1ms TTL=64 Reply from 192.168.2.254: bytes=32 time=1ms TTL=64 Reply from 192.168.2.254: bytes=32 time=1ms TTL=64 Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of http://unix.stackexchange.com/questions/243170/ssh-connection-refused-in-centos this site About Us Learn more about Stack Overflow the company Business Learn http://unix.stackexchange.com/questions/21302/ssh-connection-refused-how-to-troubleshoot more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it network error works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SSH Connection Refused In CentOS? up vote 1 down vote favorite For a week, SSH was working perfectly. Today I restarted my server and I got this error in my Mac terminal: ssh: connect to host 162.243.7.7 port 22: Connection refused This is very odd... network error connection I am not sure if I installed anything yesterday that would interfere with port 22. I installed vsftpd, but that uses port 21. I ran the command ssh -vvv dougieb36@162.243.7.7 in the terminal to get more information. Here are my results: OpenSSH_6.9p1, LibreSSL 2.1.7 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 162.243.7.7 [162.243.7.7] port 22. debug1: connect to address 162.243.7.7 port 22: Connection refused ssh: connect to host 162.243.7.7 port 22: Connection refused Next, I went to my actual server and typed service sshd status and got this(sorry that I couldn't get this in text. DigitalOcean doesn't let me copy from their terminal): Here is part of what journalctl -u sshd.service outputs: Anyone know what is happening? My config file didn't change at all. This is a bit frustrating. centos ssh terminal sshd openssh share|improve this question edited Jun 18 at 20:31 Jakuje 8,50831536 asked Nov 15 '15 at 18:28 Doug Beney 3516 what is in server log (/var/log/secure)? –Jakuje Nov 15 '15 at 18:56 Where should I look in the file? It is huge. I'm not quit
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top ssh Connection refused: how to troubleshoot? up vote 11 down vote favorite 3 I'm trying: $ ssh eric@myserver where myserver is a machine in the intranet. I can ping myserver or respond to HTTP on port 8080, etc, but when I try ssh, I get ssh: connect to host myserver port 22: Connection refused I'm somewhat new to linux, and I don't know how to troubleshoot this. I'm using Ubuntu 10 if that matters. Edit: trying ps -ax, as suggested gives: eric@Isaiah:~$ ps -ax | grep ssh Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html 1641 ? Ss 0:04 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session gnome-session 18376 pts/3 S+ 0:00 grep --color=auto ssh ssh share|improve this question edited Sep 23 '11 at 11:10 asked Sep 23 '11 at 10:50 Eric Wilson 1,37851937 add a comment| 5 Answers 5 active oldest votes up vote 12 down vote accepted You don't have an SSH daemon running. If you look at the output from the ps ax command, you see that the only two processes with 'ssh' in the description are ssh-agent (which does something entirely different from sshd) and the grep ssh process that you're using to filter the output of ps. Depending on what distribution installed, you may need to install or run the ssh server, usually called openssh-server or sshd depending on your package manager. share|improve this answer answered Sep 23 '11 at 11:41 Shadur 12.3k52742 add a comment| up vote 8 down vote Steps for debugging the above problem: Use nmap tool to know which ports are open in that server. nmap is a port scanner. Since it may be possible that ssh server is running on a different port. nmap will give you a list of ports which are open. $ nmap myserver 2 . Now you can check which server is running on a given port. Suppose in the o