Can't connect to Serviio

After running Serviio for about two years, I've got the problem that no device can connect to Serviio any more.

Serviio is up and running (hat a look into the services) and can be seen by any of the devices (Win7 MediaPlayer, Samsung Galaxy S3, Sony Bravia TV). But no device an connet to Serviio. In the console (status) "Enable access for new devices" is enabled with "No restriction" and I can see the three devices with there IP-Address and "Windows Media Player" or "unrecognized device" and "Generic DLNA profile.

I am running Serviio on a Windows XP machine. After having this problem I've updated Java to the newest release (Version 7 Update 45) and Serviio to the newest release (1.3.1.) and turned off the firewall. I reinstalled Serviio (because in an other thread this solved the problem) and I completely uninstalled Serviio and did install it again. I didn’t install any new software in the last time.

But nothing helped. Can anybody give me a hint what to do next?

[zip]

post detailed log

Here comes the log. To get it somewhat smaller (it had over 5 GB) I've deleted the filenames of the media items. To get it ready for the upload I compressed and splitted it with 7zip (http://7-zip.org/). Please remove the ending .7z before unpacking it (file extensions .001 etc. were not allowed to upload).

[zip]

From a quick look, your Serviio is on 192.168.123.100

I can see a local WMP connects to it. What are the IPs of your players? Are they on the same subnet? Do you have a firewall / antivirus?

The IPs of the clients are:
192.168.123.101
192.168.123.104
192.168.123.106

It's the same Subnet, connected via LAN/WLAN using DHCP. All Clients are connectet and can access Webserver, Internet, fileservices ....

As I mentioned in my first post there is no difference when turning off the firewall. Turning off Microsoft Security Essentials has no effect too.

[zip]

The log doesn't show any connection from these IPs, so the only explanation is something is blocking the incoming TCP (8895) or UDP (1900) traffic

Well, what's about the following lines in the log (not sure if I got everything):

2013-11-23 08:54:16,125 INFO [RendererManager] Stored a new renderer: uuid='a315365c-5cf5-43cb-8cea-7aabc1535e87', name = 'Unrecognized device', ipAddress='192.168.123.101', profile = '1'
2013-11-23 08:58:54,625 INFO [RendererManager] Stored a new renderer: uuid='00f1bf04-d705-4e8c-93ba-5b4147185f0a', name = 'Windows Media Player', ipAddress='192.168.123.101', profile = '1'
2013-11-23 11:45:35,578 DEBUG [ServiioHttpService] Incoming request from /192.168.123.101:50599: GET /deviceDescription/013d3fd4-1087-3998-a0dc-4960bd27e68a HTTP/1.1, headers = [Cache-Control: no-cache,Connection: Close,Pragma: no-cache,Accept: text/xml, application/xml,Host: 192.168.123.100:8895,User-Agent: Microsoft-Windows/6.1 UPnP/1.0 Windows-Media-Player-DMS/12.0.7601.17514 DLNADOC/1.50]]
2013-11-23 11:45:35,578 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.123.101
2013-11-23 11:45:35,578 DEBUG [DeviceDescriptionRequestHandler] DeviceDescription request received for device 013d3fd4-1087-3998-a0dc-4960bd27e68a from 192.168.123.101 (headers = [Cache-Control: no-cache,Connection: Close,Pragma: no-cache,Accept: text/xml, application/xml,Host: 192.168.123.100:8895,User-Agent: Microsoft-Windows/6.1 UPnP/1.0 Windows-Media-Player-DMS/12.0.7601.17514 DLNADOC/1.50])
2013-11-23 11:45:35,578 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.123.101
2013-11-23 11:45:35,625 DEBUG [ServiioHttpService] Incoming request from /192.168.123.101:50600: GET /icon/smallPNG HTTP/1.1, headers = [Connection: Keep-Alive,User-Agent: Windows-Media-Player-DMS/12.0.7601.17514,Host: 192.168.123.100:8895]]
2013-11-23 11:45:35,625 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.123.101
2013-11-23 11:53:28,343 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.123.101:59991s
2013-11-23 11:53:28,343 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.123.101:59991s
2013-11-23 11:53:28,343 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.123.101:59991
2013-11-23 11:53:28,343 DEBUG [ServiioHttpService] Incoming request from /192.168.123.101:50706: GET /deviceDescription/013d3fd4-1087-3998-a0dc-4960bd27e68a HTTP/1.1, headers = [Cache-Control: no-cache,Connection: Close,Pragma: no-cache,Accept: text/xml, application/xml,Host: 192.168.123.100:8895,User-Agent: Microsoft-Windows/6.1 UPnP/1.0 Windows-Media-Player-DMS/12.0.7601.17514 DLNADOC/1.50]]
2013-11-23 11:53:28,343 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.123.101
2013-11-23 11:53:28,343 DEBUG [DeviceDescriptionRequestHandler] DeviceDescription request received for device 013d3fd4-1087-3998-a0dc-4960bd27e68a from 192.168.123.101 (headers = [Cache-Control: no-cache,Connection: Close,Pragma: no-cache,Accept: text/xml, application/xml,Host: 192.168.123.100:8895,User-Agent: Microsoft-Windows/6.1 UPnP/1.0 Windows-Media-Player-DMS/12.0.7601.17514 DLNADOC/1.50])
2013-11-23 11:53:28,343 DEBUG [DeviceDescriptionRequestHandler] DeviceDescription request received for device 013d3fd4-1087-3998-a0dc-4960bd27e68a from 192.168.123.101 (headers = [Cache-Control: no-cache,Connection: Close,Pragma: no-cache,Accept: text/xml, application/xml,Host: 192.168.123.100:8895,User-Agent: Microsoft-Windows/6.1 UPnP/1.0 Windows-Media-Player-DMS/12.0.7601.17514 DLNADOC/1.50])
2013-11-23 11:53:28,343 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.123.101
2013-11-23 11:53:28,343 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.123.101
2013-11-23 11:53:28,421 DEBUG [ServiioHttpService] Incoming request from /192.168.123.101:50708: GET /icon/smallPNG HTTP/1.1, headers = [Connection: Keep-Alive,User-Agent: Windows-Media-Player-DMS/12.0.7601.17514,Host: 192.168.123.100:8895]]
2013-11-23 11:53:28,421 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.123.101
2013-11-23 11:53:31,359 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.123.101:59991s
2013-11-23 11:53:31,359 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.123.101:59991s
2013-11-23 11:53:31,359 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.123.101:59991
2013-11-23 11:53:34,359 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.123.101:59991s
2013-11-23 11:53:34,359 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.123.101:59991s
2013-11-23 11:53:34,359 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.123.101:59991

....

2013-11-23 11:06:52,062 INFO [RendererManager] Stored a new renderer: uuid='faa8a3cf-5ebd-4c6b-9965-286520a2199a', name = 'Unrecognized device', ipAddress='192.168.123.104', profile = '1'
2013-11-23 11:46:58,000 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.123.104:61106s
2013-11-23 11:47:01,000 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.123.104:61106s
2013-11-23 11:47:04,000 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.123.104:61106s
2013-11-23 11:47:07,000 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.123.104:61106s
2013-11-23 11:47:10,000 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.123.104:61106s
2013-11-23 11:47:13,000 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.123.104:61106s
2013-11-23 11:47:16,000 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.123.104:61106s
2013-11-23 11:47:19,000 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.123.104:61106s
2013-11-23 11:47:22,000 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.123.104:61106s
...

2013-11-23 08:56:40,265 INFO [RendererManager] Stored a new renderer: uuid='b4ae21ea-4040-4eab-8ed5-1b3352fecd4e', name = 'Unrecognized device', ipAddress='192.168.123.106', profile = '1'
2013-11-23 11:45:59,359 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.123.106:53532s
2013-11-23 11:45:59,375 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:CE:1 from address /192.168.123.106:53532s
2013-11-23 11:45:59,375 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.123.106:53532
2013-11-23 11:45:59,375 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.123.106:53532s
2013-11-23 11:45:59,375 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.123.106:53532
2013-11-23 11:45:59,375 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dmc-samsung-com:device:SyncServer:1 from address /192.168.123.106:53532s
...

[zip]

.106 looks like it's getting the response of search, but then doesn't make any further requests. That is UDP traffic. there is no TCP traffic (to port 8895), other than from the local .101 WMP. So I assume something is blocking TCP 8895.

Do you have any idea, what could cause this blocking? It is definitely not the firewall or the fire programme because switching them off both doesn't change anything. The machine Serviio is running on serves as a file server and a web server and there isn't much software installed: Just Office, some browsers, Net Syncronizer, WampServer, Adobe reader, cobian backup... Java Standard Edition Version is 7 Update 46 (Build 1.7.0_45-b18)

[zip]

Try this.

Look at the latest serviio.log and find this line:

  Code:

[Device] Created UPnP Device with UUID:

followed by UUID of the server instance.

Then try to open this URL on the same machine (using your UUID instead of the one below)

  Code:

http://localhost:8895/deviceDescription/90775982-25b4-38fa-940e-be80e85deb5a

It should open an XML document describing the Serviio UPnP server.

Then try to open the same URL from a different PC/IP address on your network, using the Serviio's PC IP address instead of localhost

Ifit open, the firewall is open, otherwise there is something blocking it.

Thank you very much for your detailed instructions.

I can see the xml-document on the server as well as on the client, using http://192.168.123.100:8895/deviceDescr ... 60bd27e68a

Do you have any hint, what I could try next?

[zip]

So to summarize:

- you can see your devices listed in the Serviio console
- the devices cannot see Serviio

Right?

Can you remove all the devices from the console, Save, restart the Serviio service and restart the console. Does it still show all your devices?

- Yes, I can see my devices in the Serviio console.
- And all the devices can see Serviio if the Serviio server is running.
- If I stop the Serviio service the devices can't see Serviio any more.

- If a device tries to connect to Serviio the device gets the message "data connection failed" (Samsung S3) or "There could not files be found in the remote library" (Win 7 MediaPlayer) or "Server-Connection could not be established (Sony Bravia) (All error messages translated from German, so the wording could be different in English)

- When I removed all the devices from the console, saved and restarted the Serviio service and restarted the console I could see the IP of the Win7 Windows Media Player at once.
- But the two other devices did not reappear, even after trying to connect to Serviio, which they both could see again.
. They did nit reappear even after pressing the refresh-Button and closing and reopening the Serviio-Console.

[zip]

Ok, so it confirms something changed on your setup, as before Serviio detected the devices, stored them in it DB and showed them in the console. Now they don't connect to the server anymore, so you cannot see them in the console.

Btw, when you said after stopping the service, you cannot connect to the server from the TV - that is of course expected behaviour, you cannot play any files if the service is not running.

I did a lot of testing in the last days. To get closer to the reasons I set up a Windows Media Server on the XP Machine.

Here is what I found out:
- Sony Bravia TV: This TV was connected yia a PowerLan Adapter v1.0, which worked well for almost 2 years. But now it was not possible to get a connection to the Serviio-Server and the internet any more (but it had a correct IP-Adress from the DHCP-Server. Stange! I replaced it with a PowerLan Adapter AV and now I can connect to the Serviio Server as well as to the Windows Media Server.

- Windows Media Player: The Win7 Windows Media Player (v. 12.0.7601.18150) can see the Serviio-Server but can't connect to it. But it can connect to the Windows Media Server. Might there be some incompatibility between Serviio and Windows Media Player? The connection of Nero Show Time to both ServIIo and Windows Media Server and works great

- Samsung Galaxy S3: The included MP3 Player as well as the included Video Player both can see the Serviio-Server as well as the Windows Media Server but are not able to connect to any of them. I installed the BubbleUPnP-App, which has no problem with both of the servers. Incompatibilities?

[zip]

WMP will not play anything from Serviio.

Samsung galaxy - I think people complained it does't work with their built in DLNA player, not sure what the problem is.