Windows 10: Xbox Networking 100% Packet Loss

Trying to run Forza Horizon 4 Multiplayer, shocker. I have an issue both ways. So if I turn firewall off, my latency is normal and i have 0% packet loss, but then my connectivity is blocked and I can't access multiplayer.

If I have firewall on defaults, this happens, -1 latency and 100% packet loss but my connectivity is connected, but the packet loss and weird latency I guess makes it so the multiplayer will not work either. I have no way of getting around this, I have tried a million different things and googled everywhere for the same issue and nothing I've done resolves the problem.

https://preview.redd.it/h0s2nbt72w8...bp&s=6fe4b0a559d5e387c977f7cb1e1b90df79353eb8

submitted by /u/itzvap0r
[link] [comments]

:)

 

packet loss 100%

I have packet loss and my network I tape cmd ping 50.100.121.91 I have 100% packet loss is my adresse ip extern

 

On Windows 10, the "Xbox Networking" settings page shows 100% packet loss

I was having some difficulty playing games from the windows store, namely, Sea of Thieves. After doing some investigation, I eventually found the Xbox Networking under Windows settings, which displayed the following information:

Connection Status

--------------------

Internet Connection Connected

Xbox Live Services Up and running

Performance

--------------------

Latency -1 ms

Packet loss 100%

Xbox Live Multiplayer

--------------------

NAT Type Open

Server Connectivity Connected

Every other internet-related thing on this computer is fine (can play other games, browse the internet, etc) - it's just this particular connection that seems affected. Additionally, the other computer behind this router has 0% packet loss, and can play
the same game without issue.

How can I diagnose/debug this situation?

Some extra info:

I thought Teredo might be to blame, so here's the output of "netsh interface Teredo show state" :

Teredo Parameters

---------------------------------------------

Type : natawareclient

Server Name : win1711.ipv6.microsoft.com.

Client Refresh Interval : 20 seconds

Client Port : unspecified

State : qualified

Client Type : teredo client

Network : unmanaged

NAT : cone

NAT Special Behaviour : UPNP: Yes, PortPreserving: Yes

Local Mapping : <my internal IP address from my router, removed by me>:56762

External NAT Mapping : <my external IP address, removed by me>:56762

 

100% Packet Loss

I've been experiencing this problem for a couple of days now. My wifi works but I either I can't connect to a game or I am getting massive ping spikes every couple of seconds.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Ping statistics for 8.8.8.8: Packets: Sent = 100, Received = 0, Lost = 100 (100% loss)

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

1 9 ms 3 ms 3 ms hitronhub.home
2 * * * Request timed out.
3 20 ms 15 ms 20 ms 64.59.134.209
4 * * * Request timed out.
5 36 ms 35 ms 52 ms 72.14.221.102
6 * * * Request timed out.
7 45 ms 38 ms 34 ms 108.170.233.153
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
---------------------------------------------------------------------------------------------------------------------------------------------------------
Additional Information:
I am using wireless and I have not called my internet service provider.

- - - Updated - - -

Haha, I feel so silly. All I had to do was reset my modem and that fixed the problem. *Biggrin

Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 57ms, Average = 31ms