Forum Discussion

LinuxKLowell's avatar
LinuxKLowell
New Contributor

Unable to reach specific IP addresses

Good Morning,

Starting yesterday afternoon I have been experience connectivity issues with a specific site, doesn't matter the protocol. I've contacted the service owner and they state it is a misconfiguration on my ISP's side.  If I connect to my corporate VPN and I can use this site just fine.

Here's some traceroutes:

From Cox in Henderson, NV - No VPN

lowell@hoth /h/lowell> traceroute -T server36.web-hosting.com
traceroute to server36.web-hosting.com (198.54.126.93), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  0.361 ms  0.512 ms  0.722 ms
 2  * * *
 3  100.127.2.82 (100.127.2.82)  10.928 ms  11.863 ms  14.868 ms
 4  24-234-6-192.ptp.lvcm.net (24.234.6.192)  22.343 ms  13.843 ms  22.659 ms
 5  sanjbprj02-ae0.0.rd.sj.cox.net (68.1.5.186)  41.099 ms  42.097 ms  42.048 ms
 6  ae-25.r01.snjsca04.us.bb.gin.ntt.net (129.250.192.117)  34.641 ms  29.668 ms  32.824 ms
 7  ae-10.r23.snjsca04.us.bb.gin.ntt.net (129.250.3.174)  38.967 ms  39.921 ms  39.995 ms
 8  192.80.16.178 (192.80.16.178)  35.247 ms  36.213 ms  35.969 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

From Cox in Henderson, NV WITH corporate VPN:

lowell@hoth /h/lowell> traceroute -T server36.web-hosting.com
traceroute to server36.web-hosting.com (198.54.126.93), 30 hops max, 60 byte packets
 1  * * *
 2  ussngr50-v3000.ca.com (138.42.113.1)  31.739 ms  31.991 ms  30.889 ms
 3  svl-edge-22.inet.qwest.net (65.115.64.241)  32.221 ms  32.021 ms  32.623 ms
 4  sjp-brdr-04.inet.qwest.net (67.14.34.38)  32.249 ms  32.714 ms  33.013 ms
 5  63.146.27.214 (63.146.27.214)  33.357 ms  32.773 ms  33.097 ms
 6  ae-10.r23.snjsca04.us.bb.gin.ntt.net (129.250.3.174)  32.378 ms  31.137 ms  36.898 ms
 7  192.80.16.178 (192.80.16.178)  36.702 ms  37.263 ms  36.546 ms
 8  * * *
 9  * * *
10  s36.web-hosting.com (198.54.126.93)  81.664 ms  82.299 ms  77.893 ms

Any suggestions?  Doing a little searching there does seem to be a lot of issues with this server owned by NTT.

Thanks,

Lowell

7 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • LinuxKLowell's avatar
    LinuxKLowell
    New Contributor

    Update.. by "this server owned by NTT" I mean the last hop - 192.80.16.178

  • Bruce's avatar
    Bruce
    Honored Contributor III

    198.54.126.93 doesn't seem to be blacklisted.

    Do you have McAfee?  Perhaps McAfee is blocking it and you missed its pop-up window.  Check its Security History for blocks.  You could also check Net Guard for blocks.  If it isn't listed, turn off Net Guard and try to connect.

  • LinuxKLowell's avatar
    LinuxKLowell
    New Contributor

    Using Linux... no anti virus software in use.  No firewall rules in place that would prevent this connection.

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @LinuxKLowell

    Both results appear to show the destination and the problem being within the NTT network. It may be worth reaching out to the technical contact for the site you're trying to reach for further assistance.

  • LinuxKLowell's avatar
    LinuxKLowell
    New Contributor

    Hi Chris,

    That was my first step.  They say it is my ISP's problem, not theirs.  Three weeks on and the problem is getting progressively worse.  I feel like I am caught in the middle, the hosting provider saying the problem is on the ISP side and the ISP (you) saying it is on the host's side.

    So my solution?  I'm leaving both the hosting provider and the ISP.  If neither of you wants to man up and even attempt to investigate or solve the problem, I'll solve it my way by taking my business elsewhere.

    Thanks,

    Lowell

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @LinuxKLowell

    I'd suggest contacting them again and reminding them that you're trying to reach a site hosted within NTT's network and your traffic reaches their network and dies. This is not something we'd be able to assist with unfortunately.

  • LinuxKLowell's avatar
    LinuxKLowell
    New Contributor

    Unfortunately for Cox it works on every other network I connect to.  Century Link, work VPN, AT&T Mobile... it only fails on Cox. 

    Cox is extremely overpriced anyways.. going back to CenturyLink.