hi guys, recently a client has reported that he cannot access my server if going online through a certain ISP... at first I ignored this issue for a few days as we have issues like these from time to time... but now I realized this might be a server problem and not a ISP routing problem, as I tried the following: the client gave me an IP from which he cannot acces the server and I tried a traceroute and a ping from my server: Code: h898552:/var/www/web5/web/wp-content/themes# ping 89.122.175.179 PING 89.122.175.179 (89.122.175.179) 56(84) bytes of data. ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted --- 89.122.175.179 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3009ms h898552:/var/www/web5/web/wp-content/themes# traceroute 89.122.175.179 traceroute to 89.122.175.179 (89.122.175.179), 30 hops max, 38 byte packets traceroute: sendto: Operation not permitted 1 traceroute: wrote 89.122.175.179 38 chars, ret=-1 *traceroute: sendto: Operation not permitted traceroute: wrote 89.122.175.179 38 chars, ret=-1 *traceroute: sendto: Operation not permitted traceroute: wrote 89.122.175.179 38 chars, ret=-1 h898552:/var/www/web5/web/wp-content/themes# now thsi looks to me like an internal server issue, googling has not brought me the answer so here I am - any hints?
I can ping your server, but traceroute dies. I tried to connect to your ISPConfig on port 81 with a browser, both http and https and both gave me a timeout. It also times out when trying to connect to port 80.... I tried to find your hostname, but rDNS is not setup, so it ends for me here. Code: :~# ping 89.122.175.179 PING 89.122.175.179 (89.122.175.179) 56(84) bytes of data. 64 bytes from 89.122.175.179: icmp_seq=1 ttl=117 time=221 ms 64 bytes from 89.122.175.179: icmp_seq=2 ttl=117 time=86.6 ms 64 bytes from 89.122.175.179: icmp_seq=3 ttl=117 time=115 ms 64 bytes from 89.122.175.179: icmp_seq=4 ttl=117 time=80.5 ms 64 bytes from 89.122.175.179: icmp_seq=5 ttl=117 time=71.1 ms 64 bytes from 89.122.175.179: icmp_seq=6 ttl=117 time=72.5 ms 64 bytes from 89.122.175.179: icmp_seq=7 ttl=117 time=71.1 ms 64 bytes from 89.122.175.179: icmp_seq=8 ttl=117 time=71.3 ms 64 bytes from 89.122.175.179: icmp_seq=9 ttl=117 time=72.3 ms 64 bytes from 89.122.175.179: icmp_seq=10 ttl=117 time=71.2 ms 64 bytes from 89.122.175.179: icmp_seq=11 ttl=117 time=70.8 ms 64 bytes from 89.122.175.179: icmp_seq=12 ttl=117 time=72.1 ms --- 89.122.175.179 ping statistics --- 12 packets transmitted, 12 received, 0% packet loss, time 11015ms rtt min/avg/max/mdev = 70.857/89.687/221.146/41.472 ms ~# traceroute 89.122.175.179 traceroute to 89.122.175.179 (89.122.175.179), 30 hops max, 40 byte packets 1 adslgw.tiempo.loc (172.16.3.254) 48.776 ms 75.056 ms 98.056 ms 2 84.245.2.1 (84.245.2.1) 10.838 ms 10.367 ms 11.973 ms 3 extreme-vlan211.tc1.cambrium.net (82.197.223.25) 15.837 ms 9.266 ms 9.130 ms 4 Vlan185.msfc1.AD1-Amsterdam.teleglobe.net (80.231.82.225) 10.994 ms 16.106 ms 15.722 ms 5 if-1-0.core2.AD1-Amsterdam.teleglobe.net (80.231.82.186) 9.565 ms 8.928 ms 9.206 ms 6 if-2-0.core1.FR1-Frankfurt.teleglobe.net (80.231.81.14) 15.460 ms 15.510 ms 15.794 ms 7 if-0-0-0-0.bb1.W1T-Warsaw.teleglobe.net (80.231.64.18) 47.092 ms 46.106 ms 45.649 ms 8 * * * 9 * * * <snipped. keeps timing out from here> :~# dig -x 89.122.175.179 ; <<>> DiG 9.3.2 <<>> -x 89.122.175.179 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51410 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;179.175.122.89.in-addr.arpa. IN PTR ;; AUTHORITY SECTION: 122.89.in-addr.arpa. 3248 IN SOA ns1.romtelecom.net. dnsadmin.romtelecom.net. 2006112305 10800 600 864000 3600 ;; Query time: 2 msec ;; SERVER: 172.16.3.70#53(172.16.3.70) ;; WHEN: Mon Jan 22 10:20:02 2007 ;; MSG SIZE rcvd: 108
thx for trying to help but you understood me wrong, the ping and traceroute I gave above was to test conectivity FROM my server to a sample IP that could not connect to my server. If you want to try my server this is the IP 85.214.51.208 although the server performs well, its just not reachable from that IP and that IP is not reachable from my server, but I can ping and traceroute any other IPs why not this one? And waht does ping: sendmsg: Operation not permitted and traceroute: wrote 89.122.175.179 38 chars, ret=-1 mean?
Sorry, your server (on the IP you provided for it) is fine. A quick google for the error messages seem to indicate either a firewall or routing problem on the other end (aka at your customer complaining). It seems to be in 'his' network.
I tested severall PCs which connect through the same ISP and some were able to connect to my server some were not - I do not know what to do, I just want to make sure its not my fault, but I an not using the deny.hosts file just using some blacklisting with an apache module, but that only lasts for 10 mins....
Well maybe the ISP providing the network link to your customer has something wrong? The rDNS is not setup correctly for this customer IP. That's not the cause of this network error, but maybe it's an indication they can make mistakes ?
what results do you get if you do: ping 89.122.175.179 traceroute 89.122.175.179 ? same as me above or deos it work for you?
Code: ~# ping 89.122.175.179 PING 89.122.175.179 (89.122.175.179) 56(84) bytes of data. 64 bytes from 89.122.175.179: icmp_seq=1 ttl=117 time=240 ms 64 bytes from 89.122.175.179: icmp_seq=2 ttl=117 time=240 ms 64 bytes from 89.122.175.179: icmp_seq=3 ttl=117 time=132 ms 64 bytes from 89.122.175.179: icmp_seq=4 ttl=117 time=150 ms 64 bytes from 89.122.175.179: icmp_seq=5 ttl=117 time=111 ms 64 bytes from 89.122.175.179: icmp_seq=6 ttl=117 time=223 ms 64 bytes from 89.122.175.179: icmp_seq=7 ttl=117 time=126 ms 64 bytes from 89.122.175.179: icmp_seq=8 ttl=117 time=112 ms 64 bytes from 89.122.175.179: icmp_seq=9 ttl=117 time=180 ms 64 bytes from 89.122.175.179: icmp_seq=10 ttl=117 time=198 ms 64 bytes from 89.122.175.179: icmp_seq=11 ttl=117 time=214 ms 64 bytes from 89.122.175.179: icmp_seq=12 ttl=117 time=144 ms 64 bytes from 89.122.175.179: icmp_seq=13 ttl=117 time=311 ms 64 bytes from 89.122.175.179: icmp_seq=14 ttl=117 time=230 ms 64 bytes from 89.122.175.179: icmp_seq=15 ttl=117 time=283 ms --- 89.122.175.179 ping statistics --- 15 packets transmitted, 15 received, 0% packet loss, time 14000ms rtt min/avg/max/mdev = 111.092/193.429/311.739/60.668 ms ~# traceroute 89.122.175.179 traceroute to 89.122.175.179 (89.122.175.179), 30 hops max, 40 byte packets 1 adslgw.tiempo.loc (172.16.3.254) 59.651 ms 64.896 ms 99.827 ms 2 84.245.2.1 (84.245.2.1) 8.809 ms 8.323 ms 9.157 ms 3 extreme-vlan211.tc1.cambrium.net (82.197.223.25) 16.013 ms 9.648 ms 8.525 ms 4 Vlan185.msfc1.AD1-Amsterdam.teleglobe.net (80.231.82.225) 8.817 ms 18.002 ms 15.943 ms 5 if-1-0.core2.AD1-Amsterdam.teleglobe.net (80.231.82.186) 15.894 ms 19.596 ms 9.407 ms 6 if-2-0.core1.FR1-Frankfurt.teleglobe.net (80.231.81.14) 15.305 ms 15.671 ms 15.437 ms 7 if-0-0-0-0.bb1.W1T-Warsaw.teleglobe.net (80.231.64.18) 46.373 ms 45.680 ms 45.519 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * To me, this looks like a problem at teleglobe in Warsaw.
ok and seing now that it works from your server, does that not indicate that something is wrong on my server seeing as I do get: ?
The ping's not working for me: Code: mh1:~# ping -c4 89.122.175.179 PING 89.122.175.179 (89.122.175.179): 56 data bytes --- 89.122.175.179 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss and the traceroute seems to indicate a problem at teleglobe in Warsaw, as martinfst posted already: Code: mh1:~# traceroute 89.122.175.179 traceroute to 89.122.175.179 (89.122.175.179), 30 hops max, 38 byte packets 1 85.214.1.5 (85.214.1.5) 0.501 ms 0.407 ms 0.347 ms 2 85.214.0.109 (85.214.0.109) 2.998 ms 1.523 ms 1.051 ms 3 ae3-0.hnv2-j2.mcbone.net (62.104.199.89) 4.247 ms 4.258 ms 4.242 ms 4 lo0-0.hnv2-j.mcbone.net (62.104.191.205) 4.520 ms 4.515 ms 4.481 ms 5 ge-3-0-0-0.dus2-j.mcbone.net (62.104.191.188) 8.719 ms 18.237 ms 8.735 ms 6 ge-2-0-0-0.ffm4-j.mcbone.net (62.104.191.197) 19.327 ms 12.608 ms 12.551 ms 7 if-5-1.core2.FR1-Frankfurt.teleglobe.net (80.231.65.1) 12.819 ms 12.780 ms 12.725 ms 8 if-5-0.core1.FR1-Frankfurt.teleglobe.net (80.231.64.1) 12.876 ms 12.823 ms 12.899 ms 9 if-0-0-0-0.bb1.W1T-Warsaw.teleglobe.net (80.231.64.18) 44.798 ms 44.999 ms 44.644 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * *
it seems the problems are fixed and everything is workign again - I have no clue why. the ping was not supposed to work all the time, as the ISPs are a little bit strange here, you get your IP by DHCp but nevertheless you'll get a real IP, no private one, so this one might not be "in use" 100% of the time, but when I tested it was...
