Xbox one literally cuts my net.

So this is the first time something like this has happened.

Basically everytime I connect my Xbox to my WAN, the net becomes incredibly slow if not dead.

I tested this by disconnecting all the devices except my pc from the modem by changing the wireless password. Used CMD to ping "www.google.co.za" and it gave me 4 solid 17ms packets.

I did this for 5 minutes and the net fluctuated between 15-17ms.

Connected my Xbox One and the packets start to become 1600ms and then says "request timed out" 4 times. All my updates are paused and there are no media files queued for uploading.

Think this can either be my modem or my Xbox One. The thing is though my net is perfectly fine when my Xbox One is not connected, at all times. So it can't be my modem nor my ISP.

There are moments when I disconnect the Xbox and reconnect it that the net seems okay for a while and then just gets leached again.

:)

 

hey just curious who is a mature and respectful player?

np man i didn't thinked the frist one worked my net cut out

 

We are the pioneers

@Mega, ill just cut to it. Dont bring up any other systems DRM. Period. Because what totally obliterates the comparison is that on either one of those, if the net is down, I can still play other games on my PC. YOU CANT ON XBOX ONE! End of story. Do not
pass go. Do not collect 100 dollar savings.

 

I have these ports forwarded to my Xbox's IP address:

1. TCP: 53, 80, 3074.
2. UDP: 53, 88, 500, 3074, 3544, 4500.

And work because before this problem my NAT was always open.

I also made sure that my Xbox's current IP address is still the address the ports are forwarded to.

 

Xbox One Disconnection Help | Xbox Live Disconnect | Xbox Live Problems

 

Okay, it seems to be fixed. Realised that whenever I open up Project Cars the issue starts. Changed the UDP setting in the game to be off. Immediately after I did the change and saved it, my ping dropped.

I also changed a port 5100 to be turned off which enabled me to connect to my wifi without any ping issues. Do know if these changes should have had any effect but apparently, it did....