After Trace route whats the next thing to do ? When my ISP dynamic IP address is some like and starts with 188.8.131.52 I cannot see all sites on the server. So what I did run a tracert on DOS prompt. After 9 hops and reach this IP 184.108.40.206 everything timed out and it cannot reach my server.
I already tested several Internet access and its reaching the server except my home DSL with the IP 112. I also checked if the IP is block on the firewall but its not present on the block list. I also mentioned this with my internet provider and still waiting for notification.
I assume you are trying to tracert to your server. 9 hops sounds like you reached the open net but had trouble getting through the DC. A bad vLan, wrongly configured NIC even a Null-Routed port could all account for this. The support on the other end has to handle this issue unless you have IPMI or KVM.
█ eSited LLC - Dedicated Servers, VPS, Managed Hosting
█ Nullivex LLC - Web Services, PHP Development, System administration.
█ Visit http://www.esited.com/ or Email contact[at]nullivex.com
Are you sure that got blocked with ISP. ask your host to check in server firewall....
Thank you for the reply. My suspicion about this when one day my home DSL IP suddenly changed to this 112.xxx.xxx.xxx. This is the time I get complain also from my other clients who also inform me their DSL ip starts with 112.
no its not showing anything when I execute
iptables -nL|grep 112
but when I run the command below it says
apf -a 220.127.116.11/16
18.104.22.168/16 already exists in /etc/apf/allow_hosts.rules
I still not found the solution to this. My IP that starts with 112.203 range cannot still access my server whenever the apf is up. In my previous posts all range from 22.214.171.124/8 was added to allow host rules but still no luck. No 112.203 on the deny file as well.
network-tools.com shows no timeout. meaning it an reach my server even apf is up. Like what I've said only ip that starts with 112.203 cannot access my server.