Page 1 of 1

XBox 360 ip woes after reboot

PostPosted: Sat May 11, 2013 8:58 pm
by ac_carshop
Hello,

I'm running Serviio v1.2.1 on a Win 7 x64 (current service packs) and use an XBOX 360 set a static ip (via dhcp). The PC also has a Ceton tuner card in it with a bridged adapter setup. Serviio is set up for delayed start and set to bind to the bridged address (static via dhcp).

The problem I run into is that if I reboot my PC I have to go through a song and dance getting my XBOX 360 to see the Serviio server. Media Center sees the Xbox and vice versa with no problems but the XBOX will either not see the Serviio server at all or will see it but when you try to select it it never connects. What I find odd is that when I have trouble I can look at the list of devices in the Renderer Profile section of the status tab and I will see Serviio listing the XBOX with the proper address (status red) BUT it will also list the IP bound to Serviio as an XBOX profile and status green. I have to go through multiple iterations of shutting down the XBOX and Serviio, removing the profiles, restarting Serviio to get it going. Sometimes I have to change the IP address on the XBOX.

LOG EXCERPT WHEN FAILING (bound ip is .133 and xbox is .140):
2013-05-11 14:49:20,630 INFO [RendererSearchSender] Searching for Renderer devices
2013-05-11 14:49:20,630 INFO [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth5 (MAC Bridge Miniport) and address 192.168.203.133, timeout = 0
2013-05-11 14:49:21,186 INFO [RendererManager] Stored a new renderer: uuid='82b11606-3ee3-453b-86f5-3c9fd222d685', name = 'Windows Media Player', ipAddress='192.168.203.100', profile = '1'
2013-05-11 14:49:42,238 INFO [DiscoveryAdvertisementNotifier] Leaving DiscoveryAdvertisementNotifier
2013-05-11 14:50:00,810 INFO [RendererManager] Stored a new renderer: uuid='10588331-4209-2000-0000-7c1e523c8e0d', name = 'Xbox 360', ipAddress='x.x.x.140', profile = '3'
2013-05-11 14:50:36,878 INFO [RendererManager] Stored a new renderer: uuid='659515a6-1d4f-4e5f-961f-059e9b6c0b72', name = 'Windows Media Player', ipAddress='x.x.x.133', profile = '1'
2013-05-11 14:50:44,764 INFO [RendererManager] Stored a new renderer: uuid='f8f1f540-bd33-4de7-9bf2-7aaf5c771cd6', name = 'Xbox 360', ipAddress='x.x.x.133', profile = '3'

LOG EXCERPT WHEN WORKING (bound ip is .133 and xbox is .139):
2013-05-11 15:15:31,662 INFO [RendererSearchSender] Searching for Renderer devices
2013-05-11 15:15:31,849 INFO [RendererManager] Stored a new renderer: uuid='10588331-4209-2000-0000-7c1e523c8e0d', name = 'Xbox 360', ipAddress='x.x.x.139', profile = '3'
2013-05-11 15:27:19,512 INFO [RendererManager] Stored a new renderer: uuid='659515a6-1d4f-4e5f-961f-059e9b6c0b72', name = 'Windows Media Player', ipAddress='x.x.x.133', profile = '1'
2013-05-11 15:34:33,531 INFO [LibraryAdditionsCheckerThread] Finished looking for newly added files

I realize these are short cuts from an info only log. Can turn debugging on and try again if you like but wanted start here in hopes this might be simple.

Sincerely,
Allen

Re: XBox 360 ip woes after reboot

PostPosted: Mon May 13, 2013 5:25 pm
by slyguy42o
do you have more than one xbox on your network?

also why static? were you having issues with dhcp?

Re: XBox 360 ip woes after reboot

PostPosted: Wed May 15, 2013 2:25 pm
by ac_carshop
Only 1 xbox on my network. Primary reason I went with static via dhcp was trying to get around this issue.

Thanks much. Look forward to your response.

Re: XBox 360 ip woes after reboot

PostPosted: Wed May 15, 2013 4:58 pm
by zip
It receives responses from 2 xboxes:

  Code:
2013-05-11 14:50:00,810 INFO [RendererManager] Stored a new renderer: uuid='10588331-4209-2000-0000-7c1e523c8e0d', name = 'Xbox 360', ipAddress='x.x.x.140', profile = '3'
2013-05-11 14:50:44,764 INFO [RendererManager] Stored a new renderer: uuid='f8f1f540-bd33-4de7-9bf2-7aaf5c771cd6', name = 'Xbox 360', ipAddress='x.x.x.133', profile = '3'


Different IPs, different UUIDs. Not sure if the bridge network config might be causing this.

Re: XBox 360 ip woes after reboot

PostPosted: Thu May 16, 2013 12:46 am
by ac_carshop
The bridged adapter is definitely a variable in this problem. Sadly it is one that is a real PITA to remove. The .133 address is the bridged network adapter on the Serviio/Ceton PC and with the new "Bound IP Address" feature Serviio is set to bind to that .133 address. But how can Serviio think that .133 is an XBox responding?

A curiosity, the PC just went through Microsoft's Patch Tuesday cycle. After the patches the PC rebooted as normal. At that point every time in the past I would have to go through a painful process of removing the profiles in Serviio and restarting services, rebooting the PC, cycling power on the XBOX, etc to get the XBOX to work with Serviio. This time Serviio was available on the XBOX. I've power cycled twice and Serviio has been available both times. Microsoft installed the following updates:

* KB2310138 - Security Essentials definition update
* KB2830290 - Win 7 Security update
* KB2820331 - Win 7 Update
* KB2798162 - Win 7 Update
* KB2813956 - Win 7 Update
* KB2829361 - Win 7 Security update
* KB890830 - Win Malicious Software Removal
* KB2804576 - Security Update for MS .NET Framework 4
* KB2804579 - Security Update for MS .NET Framework 3.5.1
* KB2829530 - Cumulative Security Update for IE 10
* KB2820197 - Cumulative Security Update for ActiveX Killbits for Windows 7

I have turned on debugging and will continue to monitor the problem. Unless you have any interim recommendations I'll post the debug logs the next time it occurs.

Thanks much