New Xbox One S drops network connection when in Instant On mode

Also Chiming in with the same issue. Had 3 original Xbox Ones with zero issues. Upgraded to the S a few months back and had this issue so I sent it back. Now I upgraded to 4k so I have the S and Scorpio on the way. The brand new S has the same issue. Destiny
2 will drop me out of the game and by the time I am back to the start screen, the connection is back up.

 

Do any of you guys with wireless network issues have an external USB 3.0 drive connected to the console? If so, unplug the drive and reboot the system. Now see if you're still experiencing network problems.

For more info, see here: Xbox One - hardware issues with Wifi and Kinect only with external USB 3.0 drive plugged in

FWIW, I'm using the same external drive (and Kinect via Kinect adapter) on my new Xbox One X Scorpio Edition with no problems. So the drive is ruled out for now.

 

I had exactly the same issue with an Xbox One S and my new One X, and I have done a lot of testing with this.

Soon after either console goes into standby mode, I can see a constant and consistent test ping from my PC to Googles DNS start to time out as you can see below.

Also, my 4K sport channel on my BT TV box stops working.

As soon as I pull the cable out of the back of the Xbox One S or X the ping fires back into life and the channel starts working again. Go figure.

There's definitely a problem with instant-on mode on the One S and the One X.Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=10ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=10ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Reply from 8.8.8.8: bytes=32 time=9ms TTL=57

Request timed out.

Reply from 8.8.8.8: bytes=32 time=23ms TTL=57

Request timed out.

Request timed out.

Reply from 8.8.8.8: bytes=32 time=25ms TTL=57

Request timed out.

Request timed out.

Reply from 8.8.8.8: bytes=32 time=24ms TTL=57

Reply from 8.8.8.8: bytes=32 time=22ms TTL=57

Request timed out.

Reply from 8.8.8.8: bytes=32 time=26ms TTL=57

Reply from 8.8.8.8: bytes=32 time=26ms TTL=57

Request timed out.

Reply from 8.8.8.8: bytes=32 time=23ms TTL=57

Reply from 8.8.8.8: bytes=32 time=27ms TTL=57

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 8.8.8.8: bytes=32 time=20ms TTL=57

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 8.8.8.8: bytes=32 time=31ms TTL=57

Reply from 8.8.8.8: bytes=32 time=25ms TTL=57

Request timed out.

Request timed out.

Request timed out.

Reply from 8.8.8.8: bytes=32 time=31ms TTL=57

Reply from 8.8.8.8: bytes=32 time=27ms TTL=57

Request timed out.

 

I have been having the same issue ever since upgrading to the XBOX One S over two years ago. Whenever the console is connected via Ethernet, it disconnects and reconnects rapidly. Changing cables and ports made no difference.

The constant changes on that port actually cause the DHCP server on my modem/router to lock up, requiring a reboot. I don't have a hardware model for the modem/router, but it says "Bell Home Hub 2000" in the web interface.

I have had no problems when using Wi-Fi, so I have just opted to that route because I can't have my console tanking my internet connection every few days, especially with my phone service being VOIP. I would prefer to have it connected via ethernet for
performance reasons, and because the console is only a few feet away from the modem/router.

 

I too am having this problem and have been for some time. It did it with my Xbox One S and now both of my One X’s. As soon as I turn my Xbox off, my router log blows up with these messages:

Jan 5 16:22:38 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.

Jan 5 16:22:41 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex

Jan 5 16:23:21 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.

Jan 5 16:23:24 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex

Jan 5 16:23:26 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.

Jan 5 16:23:30 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex

Jan 5 16:23:32 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.

Jan 5 16:23:35 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 10 mbps full duplex

Jan 5 16:30:16 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.

Jan 5 16:30:19 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex

And it doesn’t stop until I turn my Xbox back on. So frustrating.

 

I'm curious. Has anyone found a fix for this yet? Just picked up an xbox one x and I've never had this issue before. Looks like it has been 2 years and microsoft still hasn't resolved the issue.

 

Yes, I have this same general problem. Basically the XBOX ONE is a piece of Junk. I never had this issue with my Xbox 360 on the SAME wire, the SAME LAN port, the SAME Router for THREE years. I have the problem every single day with the Xbox One S and
it takes my hours and hours of restarting the Xbox One S before it will keep the NIC card awake. I can see the port LED's and the Xbox One S is not responding to polling pings from the Router. The stupid thing is asleep even after restarts, hard restarts,
full power restarts. WTH is going on with this piece of Junk. You thinking Microsoft was developing their first Windows 3.1 OS networking device that had the EXACT same problems 25 years ago before the Internet.

When I eventually get the boat anchor connected, it works great until I turn it off for the night and then the next day the whole thing starts over again. I have to think it is a hard ware problem. I'm returning this one to Walmart and getting a replacement.
However, if someone could give me a heads up in case the next one is also another Microsoft boat anchor.

 

I have Spectrum, one of the largest Cable Internet providers in the United States. They distribute the Technicolor router/gateway device with just about every install which I am guessing is probably 5-6 out of every 10 households
in the United States. Have you tried testing it with them instead of just Microsoft's garbage network?

 

2 Years later I still have this issue with a recently purchased brand new xbox one S. All I get from microsoft is blatant disregard, repeating the same “router” excuse. Sad to see a company as big as microsoft show no care of faulty products. After 10 years
of xbox I can finally say this will be my last purchase.

 

I'm having this issue with a wired connection where it drops connection for a split second for no reason glad to know i'm not the only one. I have tried every troubleshooting step you can think of to fix this. Been thinking of exchanging it but someone
said that will do no good. called Microsoft up and told them to read this forum it's not just me. Very frustrating

 

I have the same issue here.

Xbox One X connected to 3560-CG Cisco switch. My Xbox is in "instant on" mode but still seems to lose internet connectivity when its 'sleeping'. When I turn my Xbox on it shows no internet connection and takes a few seconds to get connected. An overnight
ping stream showed roughly 2 successful pings every half hour or so.

Connected my Xbox directly into my ASUS RT3100 wifi router and experienced the same issue. Cable is 100% good but tried multiple cables just to be sure.

Has anyone found a solution to this yet?

 

Hi Stowski!

Thanks for bring this to our attention!

Please consider taking the time to create your own thread on this issue since this is a 2 year old thread.

We will be more than happy to help!