Topic: Suddenly unable to reach site

[SteveW]

Greetings,

I'm suddenly unable to connect with my other SME server box, and vice versa. They're both running SME 6.0.1-01, and have unique static IP addresses: 66.11.164.76 and 216.138.229.239 respectively.

When I run tracert I find that the request to reach the others' site doesn't even make it to my ISP - in other words it appears that SME itself is blocking it. It tells me that the destination host in unreachable.

I have always been able to connect to these servers until recently. The only change I made was installing the e-smith-antivirus-6.0.4-01dc package via YUM onto one of these servers.

After reading some of the posts here I tried the iptables -L command and looked to see if these IP's were listed as DROP, but it is not listed there in any fashion.

I'd appreciate any help you guys can offer. Thanks a lot.
-
Steve

[ergozd]

Well, your server responds to ping

Code: [Select]

ping 216.138.229.239
PING 216.138.229.239 (216.138.229.239) from 192.168.1.4 : 56(84) bytes of data.
PING 216.138.229.239 (216.138.229.239) from 192.168.1.4 : 56(84) bytes of data.
64 bytes from 216.138.229.239: icmp_seq=1 ttl=46 time=149 ms
64 bytes from 216.138.229.239: icmp_seq=2 ttl=46 time=147 ms
64 bytes from 216.138.229.239: icmp_seq=3 ttl=46 time=149 ms
64 bytes from 216.138.229.239: icmp_seq=1 ttl=46 time=149 ms




and your webserver(-s) is/are active.

Do you still have the problem?

[SteveW]

I do still have the problem. For some reason my SME boxes are not letting me communicate w/ eachother. When I attempt to ping I get "Destination Host Unreachable."

Do you have any ideas where I'd look on the server to see where the block is occurring? Or can you suggest something else to try?

Thanks so much for helping, I truly appreciate it.
-
Steve

[SteveW]

Problem solved,

I was able to solve this one on my own - turns out is was a kernal ip routing config problem - thanks to all who attempted to assist me on and offline. For the record, I'm not sure why this happened, but I can tell you what I needed to do on both my machines to get them to connect to one another. I'm not sure if this is a bug, or something screwy that I did.

I connect to the internet identically on both my boxes using a DSL connection and a static IP address.

Firstly, even though I only had one local network (my own: 192.168.0.0) listed in the server manager's Local Networks panel, upon viewing the file /etc/e-smith/networks I noticed that there was another one listed there that I had removed from the server manager, but apparently did not remove from this file. That network in question was my opposite SME box.

I edited and removed the line referring to my opposite box. Also I noticed in the file /etc/sysconfig/static-routes that it referred also to my other box's network. So, I erased that file completely.

I restarted the network (/etc/init.d/network restart) and repeated this process on the other computer, which had the identical setup and BLAMMO everything worked like a charm.

I don't know what happened to both these machines, but I'm thankful everything is working again normally.
-
Steve