What's new

Can't route to two sites...

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Todd Price

New Around Here
Ok - I am by no means a network person - but I am trying to figure out a problem I am having.

I have two websites that I maintain for businesses. All of the sudden I can't reach them on my home network - but any other network I can reach them fine (my neighbors, via my phone with Wi-Fi turned off) - so what would be stopping just the two that I work on from routing?

When I do a ping in a command prompt I just get "request timed out" - so it is like something is stopping those from routing. It resolves the name to an IP address and then just can't route.

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Admin>ping www.spokesandbones.com

Pinging spokesandbones.com [50.28.19.107] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 50.28.19.107:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Admin>
 
Maybe a traceroute might give us a clue:
Code:
C:\Users\Colin>tracert www.spokesandbones.com

Tracing route to spokesandbones.com [50.28.19.107]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2     *        *        *     Request timed out.
  3    10 ms     8 ms     8 ms  brig-core-2a-xe-111-0.network.virginmedia.net [80.3.67.73]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    22 ms    29 ms    34 ms  manc-ic-1-ae1-0.network.virginmedia.net [62.254.42.242]
10    33 ms    28 ms    31 ms  86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
11     *        *        *     Request timed out.
12   136 ms   136 ms   137 ms  us-was03a-rd1-ae102-0.aorta.net [84.116.130.122]
13   132 ms   133 ms   149 ms  us-was03a-ri1-ae11-0.aorta.net [84.116.130.165]
14   136 ms   137 ms   136 ms  xe-5-0-3 [204.148.11.109]
15   173 ms   151 ms   153 ms  0.et-10-3-0.GW7.CHI13.ALTER.NET [140.222.237.79]
16   154 ms   152 ms   152 ms  liquidweb-gw.customer.alter.net [152.179.92.134]
17   156 ms   165 ms   156 ms  lw-dc3-core2-vlan66.rtr.liquidweb.com [209.59.157.226]
18   156 ms   155 ms   156 ms  lw-dc3-core1-po113.rtr.liquidweb.com [69.167.128.125]
19   155 ms   156 ms   155 ms  lw-dc3-dist10-po5.rtr.liquidweb.com [69.167.128.165]
20   156 ms   156 ms   156 ms  host.internetdominators.com [50.28.19.107]

Trace complete.
 
do a traceroute not ping. Trace shows the paths the packet went. Some hosts block ping and i also configure my router to dynamically block. For example one could connect to me via vpn and ping me until it ends up on the black list than even ping and vpn access is blocked.

The hosts on a traceroute could timeout but at the very least you will know where it went.
 
Usually when something just breaks like this, something somewhere changed. Did you change anything on your computer/router/network configuration lately? Did your host change anything where the sites are hosted?

I've seen issues like this when my host changed something on their server.
 
Check the firewall on these remote sites. Some servers (like those that I manage) will automatically block IPs after a number of invalid login attempts. So if you have a Linux server with something like CSF installed on them, that might be why.
 
Similar threads
Thread starter Title Forum Replies Date
J trace route shows private IP range after router Other LAN and WAN 3

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top