Sudden Connection Issues

[Trenloe]

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 6 ms 10.117.217.1
3 16 ms 16 ms 16 ms 10.224.253.13
4 * * * Request timed out.
5 28 ms 33 ms 28 ms ae-2-3613.edge1.Seattle3.Level3.net [4.69.160.73]
6 37 ms 27 ms 29 ms 4.68.70.162
7 26 ms 26 ms 27 ms 108.170.245.97
8 26 ms 26 ms 27 ms 209.85.254.167
9 26 ms 29 ms 25 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Steps 2 and 3 are private IP addresses - this more than likely indicates that your Internet Service Provider (ISP) has started sharing the public IP address with others - which is becoming more and more common. Unfortunately, this means that the port forwarding required by FG won't work in this setup, without assistance from the ISP.

Give your ISP a call (I think they're CableOne?) and say that you need TCP port 1802 port forwarded to you for peer-to-peer gaming. See what they say. You may need to pay more for a static public IP address or they may be able to set you up. If they can't you can look into the alternatives mentioned here: https://www.fantasygrounds.com/forum...d-Alternatives

[SilverStud]

Thank you so much for the help! Restarting the whole setup worked immediately.

[Trenloe]

Thank you so much for the help! Restarting the whole setup worked immediately.

Glad you got working, but that’s weird based off the tracert you sent before. Can you do another one and post what is shows here? I’m concerned your ISP may be making dynamic changes and you may get this issue again...

[damned]

Glad you got working, but that’s weird based off the tracert you sent before. Can you do another one and post what is shows here? I’m concerned your ISP may be making dynamic changes and you may get this issue again...

The private IPs are a good indicator but not a guaranteed one.
One of the Qs I ask in the FG Connections Explained thread is whether the External IP shown in FG is the same as the one shown on the Routers WAN interface.
I see a lot of shared IP addresses but I also see a lot of connections where the ISP has used private addressing on all their internal equipment but have a Public IP on the customers device.

[SilverStud]

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 6 ms 10.117.217.1
3 16 ms 16 ms 15 ms 10.224.253.13
4 * * * Request timed out.
5 28 ms 28 ms 28 ms ae-2-3613.edge1.Seattle3.Level3.net [4.69.160.73]
6 28 ms 26 ms 26 ms 4.68.70.162
7 27 ms 28 ms 28 ms 108.170.245.97
8 25 ms 26 ms 25 ms 209.85.254.167
9 30 ms 27 ms 27 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Here's the new tracert, Trenloe