LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Ubuntu Server Does Not Accept Incoming Network Connections Like SSH (https://www.linuxquestions.org/questions/linux-networking-3/ubuntu-server-does-not-accept-incoming-network-connections-like-ssh-864992/)

Subject16 02-25-2011 09:24 AM

Ubuntu Server Does Not Accept Incoming Network Connections Like SSH
 
Hi. I'm looking for tips/suggestions on how to best troubleshoot this, otherwise I'm going to have to try reinstalling the OS.

I have a bunch of Ubuntu boxes on one subnet, 192.168.1.0. I have a Windows 7 box on another subnet, 192.168.2.0. I am able to ping and SSH to all servers on the .1 subnet except for one server, which I will call PITA.

I will attempt to SSH to PITA, and it won't respond, nor does it respond to pings. I will the SSH to PITA from another of the test servers, successfully connect, and then when I SSH from my Windows 7 machine I can connect successfully. If I first connect via console to PITA and send some pings out (to anywhere, like 4.2.2.2), I can also connect from my Windows 7 machine. I've never seen anything like this.

One of the weird things is that I used PITA to create an image that I then used to create many of the other test servers, and they work fine, so I'm not sure what the problem is. I've checked /var/log/messages and syslog and there's nothing in them that indicates a problem. I've rebooted this server, restarted SSH, changed the IP in case it was conflicting with something else, forced an ARP update in case it was cached (since I had bonded the interfaces), cleared the ARP cache on my own machine, verified Network Manager is not installed...and I still have this issue. Is there anything else I can check?

Here are some network-related configs if it helps:

/etc/network/interfaces
Quote:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface

#auto eth0
#iface eth0 inet dhcp

#auto eth1
#iface eth1 inet dhcp

auto bond0
iface bond0 inet static
address 192.168.1.14
netmask 255.255.255.0
gateway 192.168.1.1
post-up ifenslave bond0 eth0 eth1
pre-down ifenslave -d bond0 eth0 eth1
/etc/udev/rules.d/70-persistent-net.rules

Quote:

# PCI device 0x14e4:0x165a (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:29:f3:9c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x14e4:0x165a (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:29:f3:9b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
ifconfig:

Quote:

bond0 Link encap:Ethernet HWaddr a4:ba:db:29:f3:9b
inet addr:192.168.1.14 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a6ba:dbff:fe29:f39b/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:375759 errors:0 dropped:0 overruns:0 frame:0
TX packets:1385612 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:43385620 (43.3 MB) TX bytes:916919735 (916.9 MB)

eth0 Link encap:Ethernet HWaddr a4:ba:db:29:f3:9b
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:375759 errors:0 dropped:0 overruns:0 frame:0
TX packets:1385612 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:43385620 (43.3 MB) TX bytes:916919735 (916.9 MB)
Interrupt:16

eth1 Link encap:Ethernet HWaddr a4:ba:db:29:f3:9c
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1008 (1.0 KB) TX bytes:1008 (1.0 KB)
I appreciate any suggestions.

Thanks.

marco18 02-25-2011 09:53 AM

What kind of interface is connected to the network? Is it a wireless one? I used to have problems with them as they seemed to enter some sleep mode and until I did not start activity from it, it wouldn't respond to any request. Something to do with drivers I guess.

Subject16 02-25-2011 10:10 AM

Nope, two wired interfaces. I have them bonded, but only one is actually connected to a switch.

Subject16 02-25-2011 03:37 PM

I just re-imaged this server, same issue. Then I switched to a different ethernet port. Same issue. In fact, while I am SSH'd into this server it eventually times out and I get a connection aborted message in Putty, after which I am unable to connect again without jumping through the above hoops.


All times are GMT -5. The time now is 10:18 PM.