Xbox 360 sees Serviio, but cannot connect
Posted: Sun Sep 29, 2013 9:05 pmServiio (via Windows 8 PC) shows up in the 360 video player list, but when I try to connect, I get a long timeout and the standard 'firewall may be blocking' message.
I've studied all the information on the forum and wiki, but I'm stumped.
All firewalls are off. All other potential DLNA servers on my network are disabled.
I used the Intel UPnP tools succesfully to test Serviio functions on another PC on the network.
I turned on log debugging, this is the relevant slice (*.216 is the Xbox, *.78 is the PC running Serviio):
2013-09-29 13:47:20,191 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,191 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,191 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,192 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,192 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,192 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,507 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,508 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,508 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,508 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,508 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,508 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,808 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,808 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,808 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,808 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,808 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,808 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:48:55,001 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 05003153-0543-2000-0000-6045bd522399 from address /192.168.1.216:27178
2013-09-29 13:48:55,001 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 05003153-0543-2000-0000-6045bd522399 from address /192.168.1.216:27178
2013-09-29 13:48:55,802 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 05003153-0543-2000-0000-6045bd522399 from address /192.168.1.216:27178
2013-09-29 13:48:55,802 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 05003153-0543-2000-0000-6045bd522399 from address /192.168.1.216:27178
2013-09-29 13:49:13,973 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface eth5 (Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller #2) and address 192.168.1.78, timeout = 0
2013-09-29 13:49:13,974 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device 42efa278-d9e8-31c8-befe-17486002f9c3
2013-09-29 13:49:15,356 DEBUG [ServiioHttpService] Incoming request from /192.168.1.216:6972: GET /deviceDescription/42efa278-d9e8-31c8-befe-17486002f9c3 HTTP/1.1, headers = [User-Agent: Xbox/2.0.16537.0 UPnP/1.0 Xbox/2.0.16537.0,Connection: Keep-alive,Host: 192.168.1.78:8895]]
2013-09-29 13:49:15,357 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.216
2013-09-29 13:49:15,357 DEBUG [DeviceDescriptionRequestHandler] DeviceDescription request received for device 42efa278-d9e8-31c8-befe-17486002f9c3 from 192.168.1.216 (headers = [User-Agent: Xbox/2.0.16537.0 UPnP/1.0 Xbox/2.0.16537.0,Connection: Keep-alive,Host: 192.168.1.78:8895])
2013-09-29 13:49:15,357 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.216
2013-09-29 13:49:15,357 DEBUG [RendererManager] Looking for a renderer profile for Http headers: [User-Agent: Xbox/2.0.16537.0 UPnP/1.0 Xbox/2.0.16537.0,Connection: Keep-alive,Host: 192.168.1.78:8895]
2013-09-29 13:49:15,358 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.216
2013-09-29 13:49:15,366 DEBUG [DeviceDescriptionRequestHandler] Sending DeviceDescription XML back using profile 'Xbox 360'
2013-09-29 13:49:15,775 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:03:11 (advertisement duration is 1800 sec.)
2013-09-29 13:49:28,702 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:28,702 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:28,702 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:28,702 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:28,952 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:28,952 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:28,952 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:28,952 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:29,202 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:29,202 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:29,202 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:29,202 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
I've studied all the information on the forum and wiki, but I'm stumped.
All firewalls are off. All other potential DLNA servers on my network are disabled.
I used the Intel UPnP tools succesfully to test Serviio functions on another PC on the network.
I turned on log debugging, this is the relevant slice (*.216 is the Xbox, *.78 is the PC running Serviio):
2013-09-29 13:47:20,191 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,191 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,191 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,192 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,192 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,192 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,507 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,508 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,508 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,508 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,508 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,508 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,808 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,808 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,808 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-microsoft-com:service:MSContentDirectory:1 from address /192.168.1.216:22423s
2013-09-29 13:47:20,808 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:47:20,808 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:service:ContentDirectory:1 from address /192.168.1.216:30398s
2013-09-29 13:47:20,808 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:30398
2013-09-29 13:48:55,001 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 05003153-0543-2000-0000-6045bd522399 from address /192.168.1.216:27178
2013-09-29 13:48:55,001 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 05003153-0543-2000-0000-6045bd522399 from address /192.168.1.216:27178
2013-09-29 13:48:55,802 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 05003153-0543-2000-0000-6045bd522399 from address /192.168.1.216:27178
2013-09-29 13:48:55,802 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 05003153-0543-2000-0000-6045bd522399 from address /192.168.1.216:27178
2013-09-29 13:49:13,973 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface eth5 (Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller #2) and address 192.168.1.78, timeout = 0
2013-09-29 13:49:13,974 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device 42efa278-d9e8-31c8-befe-17486002f9c3
2013-09-29 13:49:15,356 DEBUG [ServiioHttpService] Incoming request from /192.168.1.216:6972: GET /deviceDescription/42efa278-d9e8-31c8-befe-17486002f9c3 HTTP/1.1, headers = [User-Agent: Xbox/2.0.16537.0 UPnP/1.0 Xbox/2.0.16537.0,Connection: Keep-alive,Host: 192.168.1.78:8895]]
2013-09-29 13:49:15,357 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.216
2013-09-29 13:49:15,357 DEBUG [DeviceDescriptionRequestHandler] DeviceDescription request received for device 42efa278-d9e8-31c8-befe-17486002f9c3 from 192.168.1.216 (headers = [User-Agent: Xbox/2.0.16537.0 UPnP/1.0 Xbox/2.0.16537.0,Connection: Keep-alive,Host: 192.168.1.78:8895])
2013-09-29 13:49:15,357 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.216
2013-09-29 13:49:15,357 DEBUG [RendererManager] Looking for a renderer profile for Http headers: [User-Agent: Xbox/2.0.16537.0 UPnP/1.0 Xbox/2.0.16537.0,Connection: Keep-alive,Host: 192.168.1.78:8895]
2013-09-29 13:49:15,358 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.216
2013-09-29 13:49:15,366 DEBUG [DeviceDescriptionRequestHandler] Sending DeviceDescription XML back using profile 'Xbox 360'
2013-09-29 13:49:15,775 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:03:11 (advertisement duration is 1800 sec.)
2013-09-29 13:49:28,702 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:28,702 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:28,702 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:28,702 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:28,952 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:28,952 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:28,952 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:28,952 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:29,202 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:29,202 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target uuid:42efa278-d9e8-31c8-befe-17486002f9c3 from address /192.168.1.216:20078s
2013-09-29 13:49:29,202 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078
2013-09-29 13:49:29,202 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.216:20078