Frequent Repeated XBox Live Connection Interruptions

For the past month or so I have been getting disconnected from Xbox Live repeatedly. Once disconnected I cannot reconnect without quitting the game I am playing and either mucking about in the System's Network settings or restarting the Xbox. If I try 'Connect
to Xbox Live' from the Xbox menu, it returns an error. The specific error code varies, but 80151904 is the most common.

Coincidentally (or not?), my connectivity issues started around the same time Xbox Live started consistently reporting issues with their systems. Since I started troubleshooting this, I do not believe there has been a single day that I have visited Xbox.com
and there has not been a service alert in place. The list of affected services have never been clearly related to my issue but it seems interesting that it apparently started around the same time.

I have tried:

1. Power cycling the modem/router (no effect).
2. Power cycling the wireless bridge (no effect).
3. Power cycling the Xbox (usually temporarily resolves the issue).
4. Switching between Manual and Automatic networking configuration (usually temporarily resolves the issue).
   
5. Clearing the system cache from both storage devices (no effect).
6. Removing and re-instaling the latest system update (no effect).
7. Deleting and re-downloading my profile (I had to use another console to do this because the profile download always failed on this one) (no effect).
   
8. Disabling UPnP (no effect).

From the forum sticky, here are my answers to the listed questions:

What Country/State/Province do you live in? Ontario, Canada

Modem brand & model number: Unknown; my ISP provides a rebranded device of unknown origin

Router brand & model number: As above

How many consoles do you have connected to this router?
2 360s, an Xbox One and a PS3

Wired or wireless (for each console): The PS3 is wireless, 1 360 is cabled directly to the router/modem, the problem 360 and the Xbox One are cabled to a wireless bridge that is connected to the router/modem.

Things you have tried: See above

Is UPnP Enabled? It was until a little while ago, now it is not.

Do you have a NAT error? If so, what is your NAT type? No NAT errors shown by the 360

Any Error Codes you encounter: See above

Who is your ISP(Internet Service Provider)? Bell Canada

After you run "Test Xbox LIVE connection" press "Y" for "More Info". In the pop-up that appears, what are the following values, if shown?

As part of my latest troubleshooting effort, I ran the connectivity test 4 times in the past hour or so. Between tests, I changed nothing, but some values returned in the Error Status Report changed anyway. Here are the results (values that never changed
are omitted from all but the first set):

First test (failed):

W: 0000 - 000B

X: 0000 - F001

Y: 30A8 - 4840

Z: 0000 - 0000

ID FFFF - FFFF

L: 0015 - 10F1

Q: 8007 - 0435

T: Wired

D: 192.168.13.1/0.0.0.0

Second test (passed):

Y: 20A8 - 4840

Z: 0000 - 0000

L: 8015 - 190E

Q: 8007 - 0435

Third test (failed):

Y: 0C8C - 00E0

Z: 0000 - 274C

L: 8015 - 190E

Q: 8007 - 0435

Forth test (passed):

Y: 20A8 - 48E0

Z: 0000 - 0000

L: 8015 - 1904

Q: 0015 - 10F1

I realize that my network setup is somewhat unusual, but it was working normally for over a year. Additionally, the Xbox One that is using the same network setup does not appear to be having any issues. I am working on simplifying the networking, but that
involves running cables through walls and I am not sure when I will get it completed. I'm also not convinced it will have any impact on the disconnection issue since the existing network configuration had no issues until about a month ago.

Any thoughts on what else I can try to resolve this?

What Country/State/Province do you live in?

Modem brand & model number:

Router brand & model number:

How many consoles do you have connected to this router?

Wired or wireless (for each console):

If Wireless, are you using a white or black external adapter, or an internal (Xbox 360S) adapter?

Things you have tried:

Is UPnP Enabled? Yes/no/Unknown

Do you have a NAT error? If so, what is your NAT type?

Any Error Codes you encounter:

Who is your ISP(Internet Service Provider)?

:)

 

Repeated connection interruptions

What Country/State/Province do you live in? Milwaukee, Wisconsin

Modem brand & model number: Scientic Atlanta Cable Modem

Router brand & model number: CIsco/Linksys WRT310N

Network Connection Type: Wireless/Wired WIreless (White)

If Wireless, what type of encryption are you using? WPA2 Personal

Things you have tried: Restarting modem, router and xbox....Port forwarding.

Is UPnP Enabled? Yes/no/Unknown Yes

Is NAT Type Open? Yes

Any Error Codes you encounter:

What type of internet do you have? Cable/DSL/T1/3G? Cable

Who is your ISP(Internet Service Provider)? Time Warner Cable

When you run "Test Xbox LIVE connection" what is the exact message shown on screen? No error messages when running test

Speedtest.net results: 21.6Mb/s DL, .97Mb/s UL, Ping 27ms

I've NEVER had any issue like this until Friday, and I've been running my wireless modem for well over 2 years.

 

Repeated connection interruptions

Please try some of the tips to improve your wireless connection here:-
www.unofficialguidetolive.co.uk/.../114-troubleshooting-and-improving-wireless

 

Bell Canada gives you a 2wire Router/Modem combo. At least they did when I was with them years ago (lol you're getting robbed).

Anyway, keep UPnP enabled. Set a static IP address. 192.168.x.x, x being whatever your modem/router combo gives your Xbox 360. If you don't know, you could check your computer's, and then just add 10 to the end to be safe.

For example: My router gives my PC a static IP of, 192.168.1.123. That means, set your Xbox to ask for the static IP address of, 192.168.1.133.

Netmask should (almost) always be 255.255.255.0. Set your DNS servers to Google's. 8.8.8.8 and 8.8.4.4. Bell's servers suck. Bell also throttles you whenever they feel like it, slowing you down even though you're paying for 10, you're not going to get 10
just because they can do whatever they want, because it's Bell and they own everything. DNS servers won't fix that (leaving their expensive and unreliable service will though ). But anyway yeah, use Google's DNS.

Your gateway should be set to the same as the same one as your computer's. Basically your router's IP. Can be anything from 192.168.2.1, 192.168.1.1, 192.168.0.1. This is important.

If you don't know how to find any of this information out, on a Windows machine, hit the Windows Key and the R button, type in cmd, press enter. type in ipconfig. It will list all your connections. Some with numbers like I listed above. Look and copy.

It's 4 AM and I'm pretty sure I covered everything. I'm going to bed so if you need answers from me, then you probably won't get them until waaay later. But yeah. Set a static IP and try the test again. The first test just looks...weird. That's a weird IP
address the modem/router gave you...and the fact the second is just 0.0.0.0.

tl;dr,

Static IP, DNS and Gateway.

 

Hi there,

Thank you for the reply.

The Xbox already has a 'static' IP address that is set via a DHCP reservation that is configured in the router/modem. The troubleshooting step of flipping the configuration between Manual and Automatic was something that I found while trawling the internet
for suggestions. It effectively forces the Xbox to drop its dynamically assigned IP and get a new one from the DHCP server. In my case, however, because of the reservation, it always receives the same IP. As noted in my original post, taking this step will
usually allow me to reconnect temporarily.

Port forwarding is also already manually configured in the router/modem, so UPnP should not be necessary for that. The ports I have forwarded are TCP 3074 and UDP 3074 and 88. UPnP was enabled in the router/modem until last night, when I shut it off as yet
another troubleshooting step. With these ports manually forwarded, is there any additional functionality or value to be added by re-enabling UPnP?

This type of setup (DHCP reservation, statically forwarded ports, UPnP disabled) has served me well for years, though multiple network configurations, including different modems and routers. I used a statically assigned IP for a while but I occasionally
travel with my Xbox and redoing the networking settings became a pain so I switched to the DHCP reservation.

The IPs in my original post (the Error Status Report [ESR] D value) are my DNS servers. I think you may have mistaken it for the Xbox's local IP (the ESR
A value). I will try using Google's servers instead, though I am not sure why that would make a difference. With the exception of the DHCP reservation, every device on the network (including the other Xbox 360) use the same network configuration
and this one Xbox 360 is the only thing that appears to have any issues.

I will post back if changing DNS servers resolves the issue but my expectation is that it will not.

TL;DR:

I will try using Google's DNS; everything else is already set up correctly.

Any other thoughts or suggestions?

 

With regards to port forwarding and UPnP, only one should be enabled at a time. Having both enabled can cause conflicts.

 

Thanks for the feedback, HomegrownSilky.

I typically keep UPnP disabled but I must have forgotten to turn it off the last time I had to reconfigure my router/modem combo unit. When I realized last night that it was enabled I immediately disabled it and have no plans to turn it back on.

I tried using Google's DNS servers but it does not appear to have had any effect.

Process:

1. Launch 360 console; profile is automatically logged in and connected to Live.
   
2. Update DNS settings from Automatic to Manual and specify Google's servers; disconnected from Live as network connection is restarted.
   
3. Restart 360 console; profile is automatically logged in and connected to Live.
   
4. Launch game; disconnected from Live almost as soon as the game launched.
5. Press Xbox Guide button and attempt to 'Connect to Live'; console returns 8015190B error.
   
6. Test Xbox Live Connection; Network Connected, Internet Failed, Xbox Live Blocked (DNS error, ESR below).
   
7. Rerun Test Xbox Live Connection; passed (ESR below).
8. Sign in with my profile; successfully connected to Live.
9. Launch game; disconnected from Live as soon as the game launched.
10. Restart 360 console; profile is automatically logged in and connected to Live.
    
11. Launch game; Live connectivity persists.
12. Quit to Dashboard; receive error code 80072741 (some Xbox Live content is unavailable)
    

ESR Step 6

W: 0000 - 000B

X: 0000 - F009

Y: 0000 - 0000

Z: 8015 - 1904

ID 0002 - 0005

L: 0015 - 10F1

Q: 8007 - 0435

ESR Step 7

W: 0000 - 000B

X: 0000 - F009

Y: 20A8 - 48E0

Z: 0000 - 0000

ID FFFF - FFFF

L: 0015 - 10F1

Q: 8007 - 0435

The rest of the ESR (T, A, G and D fields) looks the same as before, except Google's DNS IPs have replaced my local IPs in D.

The error code lookup pages for both error codes I receive indicate that the cause may be issues with the Live service itself. This seems to fit with the fact that the Xbox Live Status pages have consistently reported issues ever since my issues began.

Possibly related, another user posted reporting issues that began at roughly the same time. (forums.xbox.com/.../1983395.aspx)

I am going to revert my DNS settings since that change hasn't resolved anything.

I think for my next test I will try using my fiancee's profile to see if it has the same issues.

Any other thoughts or suggestions?

 

I can't edit my post so I guess I have to double-post.

I tried my fiancee's profile on my console and it is having the same issues. She spent most of the afternoon playing on her console and didn't complain about anything, though, so presumably the issue is specific to my console.

The forums are filled with users filing similar complaints with little-to-no feedback beyond "try basic troubleshooting." It seems unlikely that this many people would all be affected by localized issues that have the same symptoms at the same time but hey,
I suppose it's possible.

One of the threads mentioned the beta program; does anyone know how I can determine whether or not my console is registered with the program? If my console is but my fiancee's is not (or vice versa) that might explain the differing behaviour between systems.

Any other thoughts or suggestions?

 

Greetings Cartoonite!

If you have configured static NAT for any of your consoles, I would then suggest that you clear these entries and revert back to UPnP. UPnP, or IGD (Internet Gateway Device) are the only sub protocol capable of handle multiple mapped connections which in
return can be multiplexed by any remote host on any remote port address. This behaviour is also known as a Full-cone NAT, Endpoint independent, or Open NAT in conjunction with the Xbox 360.

I suggest UPnP as the automatic port forwarding method, since you connect more then one Xbox to the same router Internet Connection.

Let's leave UPnP for a bit and let's try found out the make and model of your networking Equipment, such as your gateway, and wireless bridge.

If it's possible, can you connect the "problem Xbox 360" directly wired to the router and let us now if you can connect properly.

Keep us posted!

 

If you're registered it should have the pre-release tab visible, like home, games and settings etc.

The latest Xbox 360 system update would be the Public version, 2.0.17349.0

 

Hello taidara,

Thank you for the feedback.

The more time I spend on these forums the more I believe there is an issue on Microsoft's side that is affecting many people in many different ways but I am willing to continue troubleshooting my own issue nonetheless.

There are no static NATs configured on my network, only static local IPs with static port forward rules. This means that one of our 360s will always have a NAT limitation as it pertains to Xbox Live. This limitation has never had any practical impact for
us, though, so we are willing to live with it.

I don't see a pre-release tab anywhere on my console so presumably I am not part of the beta program. It sounds like MS does not have a firmware released to the beta testers, though, so it's a moot point anyway.

The wireless bridge is a Linksys E1200 v2 running DD-WRT v24-sp2 build 21676. My desktop PC, Xbox 360 and my Xbox One are the only devices behind it. There is a Linksys E1200 v1 (same DD-WRT build) in another room serving as a wireless bridge for another
desktop PC.

A previous poster says that the modem/router my ISP (Bell Canada) provides is a 2wire device. The name seems familiar but I can't say for sure. The MAC address pattern is F0:82:61 but
www.coffer.com/mac_find is unable to find a match.

Connecting the problem Xbox directly is non-trivial but I will give it a shot if I can figure out a way of doing it that does not, as they say, exceed my pain threshold.

Meantime, any additional thoughts on troubleshooting are appreciated.

 

[quote user="Cartoonite"]The wireless bridge is a Linksys E1200 v2 running DD-WRT v24-sp2 build 21676. My desktop PC, Xbox 360 and my Xbox One are the only devices behind it.[/quote]Just to clarify, is the Linksys E1200 configured in such way that its decisions
are based on the hardware addresses, or MAC addresses? Meaning, it's not operating with IP routing.

[quote user="Cartoonite"]Connecting the problem Xbox directly is non-trivial but I will give it a shot if I can figure out a way of doing it that does not, as they say, exceed my pain threshold.[/quote]Please do and let us know how that goes and we'll work
from there.

 

[quote user="taidara"]Just to clarify, is the Linksys E1200 configured in such way that its decisions are based on the hardware addresses, or MAC addresses? Meaning, it's not operating with IP routing.[/quote]

I made a few changes since the last post so if you're only interested in the current state of affairs you may want to skip to below the next quote.

In retrospect, perhaps my choice of words in a previous post was poor; the 3 mentioned devices are "behind" the E1200 only in the sense that one must cross the wireless link between the E1200 and the Bell-supplied device.

All devices are on the same private network. The Bell-supplied device is at .1 and the LAN IPs of the 2 E1200s are .2 and .3. Both E1200s are configured with the WAN IP disabled and "Assign WAN Port to Switch" enabled. Operatng Mode for both devices is "Router".

DHCP duties for the network are handled by the Bell-supplied device. The problem 360 has a reservation defined that is linked to its wired MAC address and it is receiving the correct IP when it connects.

With this in mind, I believe the answer to your question is "yes" but I am not sure how to determine whether it is operating at layer 3 or layer 2.

[quote user="taidara"][quote user=""]Connecting the problem Xbox directly is non-trivial but I will give it a shot if I can figure out a way of doing it that does not, as they say, exceed my pain threshold.[/quote]

Please do and let us know how that goes and we'll work from there.[/quote]

So we ran a couple cables through the wall but the one that comes into the room that hosts the 360 we're discussing isn't working. We do have a working cable that runs into the room on the other side of the wall, though, so I was able to get a cabled connection
set up.

The old connectivity path was 360 -> E1200 -> Bell device. The link between the 360 and the E1200 was wired and the link between the E1200 and the Bell device was wireless.

The connectivity path is now 360 -> E1200 -> D-Link 8-port switch -> Bell device. All links in this path are wired.

Once I resolved the routing loop that was created (turns out the Bell device
really doesn't like having 2 different paths to the E1200) network activity returned to normal and all the devices connected to the E1200 were able to connect to the internet again.

However, this change in connectivity path did not resolve the 360's Live connectivity issues.

Sadly, I must conclude that the result of this latest troubleshooting step has been "no change."

Any other thoughts while I work on fixing the cable that is supposed to connect this room directly to the Bell device?

 

If I may ask, why do you have an E1200 if the Bell device is a modem/router combo? Do you have the 2wire Modem/Router set to just modem? It can cause issues if the E1200 acts like a router and then your Bell Modem/Router acts like a router... I'd contact
Bell and make sure that it's configured properly. Good luck getting redirected to India with their sub-par customer service though.

 

[quote user="Irixion"]If I may ask, why do you have an E1200 if the Bell device is a modem/router combo? Do you have the 2wire Modem/Router set to just modem?[/quote]

The 2wire device is operating as a modem/router. The E1200 is (was) operating as a wireless bridge. That is, the E1200 provided a wireless link to the 2wire device for several devices that only support wired connections. It was the only way to get wired devices
upstairs connected to the 2wire without running cables through the house or walls.

The connectivity path at that time was:

360 -> RJ45 cable -> E1200 -> wireless link -> 2wire -> RJ11 cable -> Internet

Now that I have a cable running up from downstairs to a switch in the next room, the E1200 is operating as a switch. The 360 is connected to one of the LAN ports and there is a cable running from a different LAN port to the switch in the next room.

The desired connectivity path is 360 -> E1200 -> 2wire using all wired links but the cable that was supposed to make that possible isn't working so for now the extra hop is required.

I am reasonably certain that the 2wire device is configured properly since all devices on the network are able to access the internet as expected. Even when the problem 360 is disconnected from Live, connectivity to the internet is maintained. Also, this
networking setup worked flawlessly for a year or so and there were no changes when my issues first started.