Advanced Search Options


We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.
Before posting a new question, please check out our Internet / WiFi and Spectrum TV App troubleshooting pages for common issues, as well as useful information to include in your post.

Unable to connect to one particular Minecraft server after new modem installed. Tracert oddity.

StrandwellStrandwell Posts: 3 ✭✭
edited October 28 in Connectivity Oct 26, 2021

Would there be some reason the OVH servers would route traffic from my endpoint differently?

  1. I was connected to Minecraft server 51.222.203.211 on October 16, 2021.
  2. I disconnected my Spectrum modem (the Minecraft client lost connection as you'd expect).
  3. I connected my new Spectrum modem.
  4. I've been unable to connect to that server since, or even see server status in the selection list of the game client.
  5. I've rebooted my computer, router, cable modem, and flushed DNS with no change.
  6. Other online Minecraft servers continue to work just fine.
  7. I installed the old modem again, but was still unable to connect to that single server even though others worked fine. I switched back to the new modem again.
  8. I'm on a discord with over a hundred other players on that server and none report any issue connecting to the server.

A tracert from my my computer looks like:

[some normal local hops omitted]

 4  12 ms   9 ms   7 ms 096-034-116-050.biz.spectrum.com [96.34.116.50]

 5  13 ms   7 ms   8 ms bbr01renonv-bue-4.reno.nv.charter.com [96.34.121.50]

 6  21 ms  15 ms  15 ms bbr02oxfrma-tge-0-2-0-6.oxfr.ma.charter.com [96.34.0.181]

 7  19 ms  14 ms  15 ms prr02snjsca-bue-2.snjs.ca.charter.com [96.34.3.93]

 8  15 ms  14 ms  14 ms be100-103.sjo-sv5-bb1-a9.ca.us [178.32.135.92]

 9  38 ms  40 ms  38 ms be102.pdx-pdx02-sbb1-nc5.oregon.us [198.27.73.197]

 10  28 ms  28 ms  28 ms 142.44.208.227

 11   *    *    *   Request timed out.

 12   *    *    *   Request timed out.

 13   *    *    *   Request timed out.

[repeats]

30   *    *    *   Request timed out.

For a comparison, I used https://tools.keycdn.com/traceroute to get results from another endpoint. The one from San Francisco was interesting:

1.|-- 104.236.128.254      0.0%   4  1.4  2.4  1.3  5.5  2.1

 2.|-- 138.197.248.214      0.0%   4  1.4  1.6  1.4  1.9  0.2

 3.|-- 138.197.244.237      0.0%   4  3.7  3.9  3.7  4.1  0.1

 4.|-- ???            100.0   4  0.0  0.0  0.0  0.0  0.0

 5.|-- 198.27.73.197       0.0%   4  39.1 39.1 39.0 39.1  0.1

 6.|-- 142.44.208.227       0.0%   4  29.0 29.0 28.9 29.3  0.2

 7.|-- ???            100.0   4  0.0  0.0  0.0  0.0  0.0

 8.|-- 147.135.34.8        0.0%   4  28.3 28.4 28.3 28.6  0.2

 9.|-- 147.135.34.9        0.0%   4  29.5 29.5 29.5 29.6  0.0

 10.|-- 147.135.34.7        0.0%   4  29.6 29.6 29.6 29.6  0.0

 11.|-- ???            100.0   4  0.0  0.0  0.0  0.0  0.0

Despite going through the same 142.44.208.227 hop, a trace from another starting point got a response from servers downstream of there. The trace from Sydney also went through 142.44.208.227 with the same downstream responses as the SF run.

Whois reports OVH as the holder of 142.44.208.227 as well as hops on either side of that one all the way back to a Spectrum hop. They don't seem to have contact information, and their community reporting option (similar to this) requires an active user account.

I used ProtonVPN to test changing just my my endpoint, and it actually returns server data to the game client with that enabled. Connecting the game through the VPN doesn't work, though game servers sometimes refuse connections through known VPNs to prevent IP-ban circumvention, so I can't be certain it wouldn't otherwise work.

I'm not interested in hunting obscure VPNs to avoid that reasonable server measure, but I have no more networking knowledge to unravel how to make OVH allow connection from my Spectrum endpoint. Since it looks like the connection goes directly from Spectrum hops to an OVH hop, is there a way Spectrum could advocate for OVH to correct the routing issue? Are there any other diagnostic steps I could take to find a cause?

Best Answer

  • James_MJames_M Posts: 3,109 ADMIN
    Oct 27, 2021 Accepted Answer

    Hi -

    In the trace you provided, the Charter network was exited after hop 7. 142.44.208.227 is managed by OVH, as you pointed out. You would need to contact OVH to investigate or report an issue.

    Thanks!


Replies

  • StrandwellStrandwell Posts: 3 ✭✭
    Oct 26, 2021

    I'd meant to post this to connectivity but ended up in home networking. I don't see a way to move it.

  • StrandwellStrandwell Posts: 3 ✭✭
    Oct 29, 2021

    Thanks! It sounds as though there isn't some sort of reciprocity or more generic routing issue report mechanism I'm missing.

  • Paul_BPaul_B Posts: 419 MOD
    Oct 29, 2021

    It sounds like there is some sort of peering issue between hop 8 and the peer to the 142.44.208.227 server. Are you able to ping that Minecraft server at all?

    Paul_B

Sign In or Register to comment.