Xbox live disconnects as soon as i search for a game, works perfectly after that?...

So ive had a problem a while now and no idea why it does it. This problem occurs on every single XBL game i play as soon as i try searching for a game. i do not get disconnected when using services such as Sky, or download from the market place.

So i turn my xbox on for the first time throughout the day. I connect to XBL fine, can access my friends list/message etc fine. I load up the game fine, but as soon as i go to search for an online match, i get disconnected from the games server (EA sports on
Fifa, Bungie on Destiny etc), chucked back to the games main menu, and then a few seconds later disconnected from xbox live.

I press the guide button and sign back into profile, search for a gameand it works perfectly for hours. Just seems to be after searching for that very first game.

I have tried connecting the xbox using wireless + ethernet and does the same on both.

Is it a router problem? A friend on the same street with the same internet service provider and router doesn't have this problem on his 360.

What Country/State/Province do you live in? UK

Modem brand & model number:

Router brand & model number: D-Link DSL-3680

How many consoles do you have connected to this router? 1

Wired or wireless (for each console): Wired, but problem occurs both wired and wireless.

Things you have tried: resetting router for factory settings

Is UPnP Enabled? Unknown

Do you have a NAT error? If so, what is your NAT type? NAT is usually OPEN. Previously had a MODERATE NAT but seems to have sorted itself out?

Any Error Codes you encounter: none

Who is your ISP(Internet Service Provider)? TalkTalk



:)

 

UPDATE FAIL

as soon as i log into a game it disconnects me from xbox live after the update very frustating

 

Halo 4 List of Issues

Well, whenever I start my halo 4 it works perfectly , but as soon as I search for a war games server, my Xbox freezes. Then soon afterwards I get a red ring. I leave my Xbox off for a couple of hours and start it up again, but yet the problem repeats. What
on earth is going on?

 

Unfortunately you're not the only one, I'm having the exact same problem as well as others. It's a problem on Microsoft's side.