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:
Quote:
Quote:
Thanks. |
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.
|
Nope, two wired interfaces. I have them bonded, but only one is actually connected to a switch.
|
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. |