Cant connect to XBL

Here is my Trace info I gathered from my x box... I cant change my router so I figured maybe some one on the forums can help me...

Issue : cant connect to LIVE service and cant change router settings.

Tracer info

Hop Ping IP Host

1 <1ms 192.168.0.1 ------

2 7ms 10.101.64.1 --------

3 7ms 192.168.47.81 ---

4 22ms 10.224.252.106 ---

5 22ms 4.28.80.53 xe-5-0-1.bar1.pheonix1.level3.net

6 28ms 4.69.144.139 ae-3-80.edge5.LosAngeles1.level3

7 29ms 4.69.144.139 ae-3-80.edge5.LosAngeles1.level3

8 29ms 4.69.201.6 ae-16-16.car1.LosAngeles1.Level3.net

9 29ms 4.71.140.78 MICROSOFT -C.car1.LosAngeles1.Level3.Net

10 31ms 207.46.47.11 ae11-0.;ax-96cbe-1b.ntwk.msn.net

11 * Request timed out

12 * Request timed out

13 63 1.91.234.82.251 ae19-0.co2-96c.1b.ntwk.msn.net

I have no clue what any of this means and I was literally on last week so i have no idea whats causing this issue.

:)

 

80151904

I cant connect to xbl whenever I try it just say my consol cant connect to xbl. When i try to reinstal my profile it still just says i cant connect so i cant evan reinstal my profile.

 

XBL

I can connect to the internet, but i cant connect to XBL. It told me to reset my router for 30 seconds, but i still cant connect to XBL. What do i do?

 

Whatever evidence you provide, remember it's not Microsoft's fault. It's yours.

 

If this is for Xbox 360 please try to restore your settings to factory defaults and try connecting back to Live and if the same thing please try to turn off your router, unplug it from the outlet and wait for 5 minutes. Then retry. If the same thing please
try to contact your Internet Service Provider for them to check your router settings/Network settings. Consoles are dependent with your network settings.

 

RESET NETWORK SETTINGS:

Kindly go to Settings >> select System Settings > Select Network Settings >> Select the name of your wireless network/wired network > Select Configure Network > select Restore to Factory Defaults. When prompted, select Yes, Restore to Factory Defaults.

Note This resets the console's network settings only, and not other settings.

 

I'm sorry to inform you Sabo, but rehashing th same information that all of us have tried and tested long before we come here is not helpful in the least. Most, perhaps not all have been this route, we have web searched, we have read the forums, been to
the support page, done all of the things suggested a hundred times over again to no avail. Please stop attempting to tell us this is on our end. my system was off for three days, left untouched and unfettered, i loaded a new game in, booted my xbox and nothing.
rebooted and connected long enough to download the always unneeded game update and got dumped.... again. Tried a third time, was on for 15 minutes in multiplayer got dropped by XBL. Again, I rebooted and got back in, this time for 8 minutes, long enough to
just get into a match, dropped by XBL. I and most of those posting here in this forum are having the same issue, we have done all that is asked of us and more in some cases.

Error 8015190E the evil little genies of an error that is plaguing 99% of us right now is in laymens terms a nondescript error, a generic error of unknown origin that means in fact very little. It is generated when the system sees that it should be receiving
traffic from the server but for lack of a better term isn't. There is no connection error to speak of, the internet and network protocols are met and working, but its receiving no answer from home. so its generally stuck in a ping loop until the machine reaches
a set number of attempts and says "oh well, no one is answering, I'm hanging up."

Microsoft will not help us because, if the error is on the server end and they admit it, they open themselves to lawsuits for lost time and subscription fees for the time the problem occurred. With tens of thousands of customers, it'd get very costly if
even one person won. So they will attempt to cover it, at the current time XBL core services have been in maintenance twice in 15 hours, both times related to this little bugger. It's not and let me reiterate that again it is NOT a problem with the ISP, or
the Internet backbone or a goblin or fairies messing with our consoles, this is simply a hardware communication issue at the server farm where one of the data nodes that handles traffic needs to be replaced.

Thank you and again please take a second to not assume we are all idiots that have not looked into the possible fixes before we came here