Ask a new question

Randomly Disconnecting from Xbox Live

Hi Support,

I have a new XBox360S for christmas, my wife is a darling and has been an Xbox widow for 6 years of my gold membership now, loaded up the new dashboard and had dashboard only live disconnects whilst on the wired network.

My 8 year old "white" one updated to the new dashboard and has had no problems at all, the same with my sons XBox360Elite.

After much analysing and swapping consoles etc, it looks to me like it is not so much the update that is causing the problems now but the XBox360S network/wireless implementation.

In the end I had the 360S signed in to live and watched the Available network tile with the tick in the wired network block, when live dropped the tick moved to wireless tile and back again and is repeatable time after time.
This suggests that the 360S is possibly "detecting" the network cable being disconnected, which it isn't and trying to connect to the wireless, which it cann't because the ethernet cable is still plugged in.
And yes, I have changed the cables and all the other things that have been asked all the others to perform with this kind of problem.

It does look like it could be some kind of timeout problem as suggested earlier by PatrickPlan8 and maybe a new patch for the 360S network manager firmware could fix the problem.

What Country/State/Province do you live in? New Zealand
Modem brand & model number: NetgearDG834PN with DGteam firmware V1.03.39 -  DGTeam Rev.1018
Router brand & model number: 
If Wireless, are you using a white or black external adapter, or an internal (Xbox 360S) adapter?Xbox360S
Things you have tried: New network cable, resetting modem, clearing cache, reloading profile.
Is UPnP Enabled? Yes
Do you have a NAT error? If so, what is your NAT?Open
Any Error Codes you encounter: none
Who is your ISP(Internet Service Provider)? Xtra Broadband - Telecom NZ
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? (If a value below does not appear for you, just leave it blank.)
Normal connection test
W:0000 - 000B
X:0600 - F001
Y:20A8 - 4840
Z:0000 - 0000
ID:FFFF - FFFF
L:0015 - 10F1
Q:0015 - 10F1
T:Wired
A:192.168.0.220/255.255.255.0
G:192.168.0.1
D:202.27.156.072/202.27.158.40

After XBox Live disconnects
W:0000 - 000B
X:0600 - F001
Y:20A8 - 4840
Z:0000 - 0000
ID:FFFF - FFFF
L:8015 - 100D
Q:8015 - 100D
T:Wired
A:192.168.0.220/255.255.255.0
G:192.168.0.1
D:202.27.156.072/202.27.158.40

Since my post earlier to PatrickPlan8, I have been running on the wireless signed in to Live, played some Gears3 and later with it sitting in the dashboard for over 6hrs with the ads cycling, (glad I had my laptop to play on), have not had one single disconnect from live during that period.

Went back onto the wired network and within minutes was disconnected from Live.  
Tried it again, this time waiting in the Available Networks panel, nek minit, yep, same as before, the tick in the wired connection filcked over to the wireless tile and back as it disconnected.  I still think the problem is in the wired to wireless detection method.

When it last dropped live I didn't bother to reconnect and left it 'signed in' but still watching the Available Networks panel/wired network tile.  
Surprisingly, the tick in the wired connection filcked over to the wireless tile and back, this time it signed me out completely.
To get back on Live it was the same as starting from scratch and re-signing in.

I hope this helps with the data gathering.

SteveH.

 

 

 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Thank you for the very thorough post Aquil. I'm curious, when wired, are you connected directly to your modem? Please let us know, and we'll go from there. :-)

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Fitzler, yes only about 3ft and it doesn't matter which of the 4 ethernet ports are used.  It was using a short patch cable but now it is on a 1mtr new one.  I tested it on the other XBox just to make sure it was good.  

Same distance away for the wireless.  

The other 2 XBoxs are in different rooms and access the modem via wired 8 port switches and have no problems at all.  

Fault presents the same when the 360S is on its own or with the other 2 on as well.  But I have been doing all this testing with the 360S on its own for clarity.

After I get disconnected and switch to wireless to run the network test the error codes for "L" and "Q" are the same numbers as in the disconnect list above, just the wireless bits are different of course.  I can post them l8tr, at work just now ;)

Hows that?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hey there Steve! So I understand you have 3 or 4 total consoles connected to your network, is that correct? What if you disconnect all of them except the one you seem to be having issues with and then try a wired connection? Does the number of consoles seem to have any effect?

One other thing we can do to test is try connecting your console to a completely different network, like at a friend or family member's house. Do you notice any issues using a wired connection there? If you do, there may be an issue with this console and you could set up a hardware repair to get it fixed. Please let us know what you find out, thanks!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Mr Gwyther,

Yes, 3.  Mine is the new 360S 250Gig and the one dropping Live on a wired connection, but only when in the dashboard.

On line gaming works without and problems, all 3 have open NATs and can thrash the network 'til it bleeds and doesn't drop both on wired or on the wireless.

All of the testing for dropping Live has been done on the network on its own for clarity.

Each time I try a fresh test I go to, Configure Network>Additional Settings> and select Restore to factory defaults, just to make sure the network controller is cleaned out.  UpNp gets flushed as well in the modem.

UpNp is on and port forwarding is turned off.

I have also reserved an ip address of xxx.xxx.xxx.220 in the router based on the MAC address and set the xbox to automatic network address.  This makes sure the xbox gets the same ip address on the network all the time.

The 3 xboxs on my network all have open NAT using this method. the others are on ip addresses xxx.xxx.xxx.190 and xxx.xxx.xxx.200.

Since doing all this checking, I then went back on wired, but put an 8 port network switch in between the Xbox and the router and that seems to work as well as the wireless!!!@#, it helps to keep the ethernet port open.  We use this method when we test some of our ethernet based products at work.

It was left on in the dashboard last evening and overnight, approx 10Hrs and did not drop.

I will definately try it on another network and will be able to get a 360S 4Gig to try on my network and post up the results.

Thanks for the input.  Let us try all avenues before committing to the repair loop. ;)

Best regards,

SteveH.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Steve! I agree, we should pursue all opportunities available! The switch is an interesting development for sure. Please keep us updated on the status of your console on another network, as well as that other console on your network! And, I hope you are having a wonderful day! :)

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Miss Portia, I have now been running the 8 year old white 360 for 6hrs sat in the dashboard in place of the 360S on wired in the same port without the network switch and it has not dropped live at all.

I am absolutly certain now that it is not any of my network equipment, it has been tuned, honed, re-flashed and loved to get the best possible performance out of it, otherewise the same or similar faults would be apparent with the other 2 consoles.

This is now looking more likely to be pointing to a common problem with the firmware or physical network implementation in the 360S consoles in general.
There is now too much evidence with respect to all the other very similar posts in this forum.

I doubt very much it is just my 360S that has a problem. 

Has any of your technicians back at at Xbox base set up any testing similar to the above descriptions in this and other posts to simulate any of the fault scenarios many, many Xbox faithfuls have been describing?

An example; one of my companies network products had a wired network problem where the unit would load files from TFTP but would not load from FTP at 100M.
It turned out to be a timing issue caused by a 33R resistor in the ethernet clock signal to the main CPU.  Changed the offending resistor to 0R and the problem has completely been cleared.
I'm not saying it is the same but it could even be something in the code that needs patching that could fix it etc.

To continue the testing, I will be trying a different 360S soon in the same spot the white one is now in.

L8trs,  SteveH.


Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hey Steve - thank you for the extensive follow up. We are not seeing a widespread issue with ethernet connectivity and Xbox 360 S consoles, so unfortunately it is hard to speculate that there could be a design fault. If there were a significant number of consoles affected in the exact same way, that would certainly make sense. However, that is not what we are seeing.

The switch development was interesting, but can I ask how your network is configured in it's entirely? Switches are not typically supported with Xbox LIVE as they are a dumb networking device, as I am sure you're aware. We tend to recommend against those types of devices. The thing you mention initially, the wired check mark moving to wireless then back again, indicates an issue with the connection between your console and whatever device you have plugged it into. If you were to unplug the cable from the other device, that is what would happen - the console would then look for wireless networks. I would be very curious to see what behavior the console exhibits when you have it directly connected to your modem, bypassing your network completely. Do you still observe this type of behavior? Or does it stay solidly connected?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Again, been busy testing several scenarios.

The only way to hook up everything in the house is to use network switches if wireless is not an option.
Hubs are dumb, switches are not.

The wired check mark moves to the wireless and back and the annuciator sounds bink/bonk as well.
The cable is new, 2 others have also been tried.

Three other XBoxs work in the position my new one normally occupies.  All updated to Dash 2.0.14719.0.
1) 8 year old white one updated no problem and works flawlessly.
2) 2 year old Elite updated no problem and works flawlessly.

This is the significant information regarding the coparison to my new XBox 360S.  Which has a manufacture date of 22/Sept/2011 Serial #127095413909.  Production ID-04073501127095413909.

3) 360S 250G 4Gig upgraded to 250Gig, manufacture date 24/Aug/2010 Serial #042817603508, Production ID-024101673992, had no problem sitting in the dashboard for 15Hrs without dropping Live.
All cables, connections and ethernet ip address were exactly the same.  (Actually does not matter what the IP Add is).
The tests have all been carried out with only one XBox connected directly to the Netgear DG834PN ADSL Modem/Router.  It is not possible to separate the modem from the router.
After all the testing the and new XBox returned to it's place for confirmation, it still drops several times an hour at any time of the day.

I have attached a copy of my network configuration which should help explain the situation.
Note the heartbeat only seems active when on the wired network tile with the tick.  not present on the dashboard.

Best regards,

SteveH.


Here is a short Wireshark capture of the drop and recover event from heartbeat to heartbeat.  Goes off wire to back on wire.


No.     Time                       Source                Destination           Protocol Length Info
     54 2012-03-18 17:35:54.996764 192.168.0.210         Broadcast             MS NLB   60     MS NLB heartbeat

Frame 54: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
MS Network Load Balancing

Drops network/live here.

No.     Time                       Source                Destination           Protocol Length Info
     55 2012-03-18 17:35:55.012080 0.0.0.0               igmp.mcast.net        IGMPv3   60     Membership Report / Leave group
239.255.255.250

Frame 55: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: igmp.mcast.net (224.0.0.22)
Internet Group Management Protocol
    [IGMP Version: 3]
    Type: Membership Report (0x22)
    Header checksum: 0xeafe [correct]
    Num Group Records: 1
    Group Record : 239.255.255.250  Change To Include Mode

No.     Time                       Source                Destination           Protocol Length Info
     56 2012-03-18 17:35:55.041780 0.0.0.0               255.255.255.255       DHCP     342    DHCP Discover - Transaction ID 0x8b7ab642

Frame 56: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
    Message type: Boot Request (1)
    Hardware type: Ethernet
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x8b7ab642
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: 192.168.0.210 (7c:ed:8d:e0:d6:87)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type
    Option: (61) Client identifier
    Option: (60) Vendor class identifier
    Option: (55) Parameter Request List
    Option: (255) End
    Padding

No.     Time                       Source                Destination           Protocol Length Info
     57 2012-03-18 17:35:55.056686 0.0.0.0               255.255.255.255       DHCP     342    DHCP Request  - Transaction ID 0x8b7ab642

Frame 57: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
    Message type: Boot Request (1)
    Hardware type: Ethernet
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x8b7ab642
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: 192.168.0.210 (7c:ed:8d:e0:d6:87)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type
    Option: (61) Client identifier
    Option: (60) Vendor class identifier
    Option: (55) Parameter Request List
    Option: (50) Requested IP Address
    Option: (54) DHCP Server Identifier
    Option: (255) End
    Padding

No.     Time                       Source                Destination           Protocol Length Info
     58 2012-03-18 17:35:55.086646 192.168.0.210         Broadcast             ARP      60     Gratuitous ARP for 192.168.0.210

(Request)

Frame 58: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request/gratuitous ARP)

No.     Time                       Source                Destination           Protocol Length Info
     59 2012-03-18 17:35:56.046745 192.168.0.210         Broadcast             ARP      60     Gratuitous ARP for 192.168.0.210 (Reply)

Frame 59: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (reply/gratuitous ARP)
.
Reconnects to network here
.
No.     Time                       Source                Destination           Protocol Length Info
     60 2012-03-18 17:35:56.246736 192.168.0.210         igmp.mcast.net        IGMPv3   60     Membership Report / Join group

239.255.255.250 for any sources

Frame 60: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: igmp.mcast.net (224.0.0.22)
Internet Group Management Protocol
    [IGMP Version: 3]
    Type: Membership Report (0x22)
    Header checksum: 0xea03 [correct]
    Num Group Records: 1
    Group Record : 239.255.255.250  Change To Exclude Mode

No.     Time                       Source                Destination           Protocol Length Info
     61 2012-03-18 17:35:56.246826 192.168.0.210         239.255.255.250       SSDP     313    NOTIFY * HTTP/1.1

Frame 61: 313 bytes on wire (2504 bits), 313 bytes captured (2504 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: upnp:rootdevice\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687::upnp:rootdevice\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     62 2012-03-18 17:35:56.446930 192.168.0.210         239.255.255.250       SSDP     313    NOTIFY * HTTP/1.1

Frame 62: 313 bytes on wire (2504 bits), 313 bytes captured (2504 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: upnp:rootdevice\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687::upnp:rootdevice\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     63 2012-03-18 17:35:56.447081 192.168.0.210         239.255.255.250       SSDP     322    NOTIFY * HTTP/1.1

Frame 63: 322 bytes on wire (2576 bits), 322 bytes captured (2576 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: uuid:12709541-3909-2000-0000-7ced8de0d687\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     64 2012-03-18 17:35:56.447141 192.168.0.210         239.255.255.250       SSDP     322    NOTIFY * HTTP/1.1

Frame 64: 322 bytes on wire (2576 bits), 322 bytes captured (2576 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: uuid:12709541-3909-2000-0000-7ced8de0d687\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     65 2012-03-18 17:35:56.447196 192.168.0.210         239.255.255.250       SSDP     369    NOTIFY * HTTP/1.1

Frame 65: 369 bytes on wire (2952 bits), 369 bytes captured (2952 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: urn:schemas-upnp-org:device:MediaRenderer:1\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687::urn:schemas-upnp-org:device:MediaRenderer:1\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     66 2012-03-18 17:35:56.447252 192.168.0.210         239.255.255.250       SSDP     369    NOTIFY * HTTP/1.1

Frame 66: 369 bytes on wire (2952 bits), 369 bytes captured (2952 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: urn:schemas-upnp-org:device:MediaRenderer:1\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687::urn:schemas-upnp-org:device:MediaRenderer:1\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     67 2012-03-18 17:35:56.447314 192.168.0.210         239.255.255.250       SSDP     379    NOTIFY * HTTP/1.1

Frame 67: 379 bytes on wire (3032 bits), 379 bytes captured (3032 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: urn:schemas-upnp-org:service:ConnectionManager:1\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687::urn:schemas-upnp-org:service:ConnectionManager:1\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     68 2012-03-18 17:35:56.447371 192.168.0.210         239.255.255.250       SSDP     379    NOTIFY * HTTP/1.1

Frame 68: 379 bytes on wire (3032 bits), 379 bytes captured (3032 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: urn:schemas-upnp-org:service:ConnectionManager:1\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687::urn:schemas-upnp-org:service:ConnectionManager:1\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     69 2012-03-18 17:35:56.447428 192.168.0.210         239.255.255.250       SSDP     377    NOTIFY * HTTP/1.1

Frame 69: 377 bytes on wire (3016 bits), 377 bytes captured (3016 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: urn:schemas-upnp-org:service:RenderingControl:1\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687::urn:schemas-upnp-org:service:RenderingControl:1\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     70 2012-03-18 17:35:56.447485 192.168.0.210         239.255.255.250       SSDP     377    NOTIFY * HTTP/1.1

Frame 70: 377 bytes on wire (3016 bits), 377 bytes captured (3016 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol Version 4, Src: 192.168.0.210 (192.168.0.210), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 7232 (7232), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
    NOTIFY * HTTP/1.1\r\n
    HOST: 239.255.255.250:1900\r\n
    NT: urn:schemas-upnp-org:service:RenderingControl:1\r\n
    NTS: ssdp:alive\r\n
    LOCATION: http://192.168.0.210:1054/\r\n
    USN: uuid:12709541-3909-2000-0000-7ced8de0d687::urn:schemas-upnp-org:service:RenderingControl:1\r\n
    CACHE-CONTROL: max-age=1800\r\n
    SERVER: Xbox/2.0.21076.0 UPnP/1.0 Xbox/2.0.21076.0\r\n
    \r\n
    [Full request URI: http://239.255.255.250:1900*]

No.     Time                       Source                Destination           Protocol Length Info
     71 2012-03-18 17:35:56.998774 192.168.0.210         Broadcast             MS NLB   60     MS NLB heartbeat

Frame 71: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
MS Network Load Balancing

No.     Time                       Source                Destination           Protocol Length Info
     72 2012-03-18 17:35:59.017545 192.168.0.210         Broadcast             MS NLB   60     MS NLB heartbeat

Frame 72: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Ethernet II, Src: 192.168.0.210 (7c:ed:8d:e0:d6:87), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
MS Network Load Balancing

 

 

 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,  I have some more info to see if it can help identify the reason for randomly dropping Live.

Not forgetting all this is only happening on my new 360S made in Oct 2011.  None of the other consoles behave this way.

When it drops it is clear from what wireshark is capturing, that there is nothing wrong with the network, cable or any of the connections.
The XBox issues a network command, [Protocols in frame: eth:ip:udp:bootp], that is identical to the unit being turned on or using the "reset network to default" on the test screen and entering the network for the first time.
Something is causing the XBox to issue this command randomly.

Another interesting development on the use of the network switch between the XBox and the modem/router, is, when connected to Live through it, it still doesn't drop Live. 
If the cable connection between the switch and the modem/router is removed now isolating the switch and the XBox from the modem/router , the dashboard stays functonal with everything running as if it is still connected, wireshark still sees heartbeat when on the wired network tile.
It stays like this for 2min, then drops.
This is the reason why, when the XBox is behind the switch it never drops Live, the switch is supplying all the control until the ARP cache refreshes.  (It cann't because the wire is still out so it drops).
If I plug the wire back in before the cache times out the XBox never even knows the wire was disconnected ;) and carries on as if nothing has happened. Mmmm.  But this is what switches are meant to do.

Best regards,  SteveH.

Below is part of the capture of the XBox issuing the beginning of its network boot, (hello I'm here), sequence, even though it was running 'normally' in the dashboard when it gave it.

User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
    Source port: bootpc (68)
    Destination port: bootps (67)
    Length: 308
    Checksum: 0x662d [validation disabled]
        [Good Checksum: False]
        [Bad Checksum: False]
Bootstrap Protocol
    Message type: Boot Request (1)
    Hardware type: Ethernet
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x8b7ab628
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: 192.168.0.210 (7c:ed:8d:e0:d6:87)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type
        Length: 1
        DHCP: Discover (1)
    Option: (61) Client identifier
        Length: 7
        Hardware type: Ethernet
        Client MAC address: 192.168.0.210 (7c:ed:8d:e0:d6:87)
    Option: (60) Vendor class identifier
        Length: 8
        Vendor class identifier: Xbox 360
    Option: (55) Parameter Request List
        Length: 4
        Parameter Request List Item: (1) Subnet Mask
        Parameter Request List Item: (3) Router
        Parameter Request List Item: (6) Domain Name Server
        Parameter Request List Item: (15) Domain Name
    Option: (255) End
        Option End: 255
    Padding

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Just a thought. Have you consider sending it in for repair?

The impossible just takes a little longer

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info

Last updated August 18, 2021 Views 171 Applies to: