DLNA setting issue with LG BD-570

[k10ck3r]

I have the LG BD-570 working well for the most part, but I noticed something strange.
When the device connects to the server, I get very different times depending on how the DLNA setting is configured.
(This is a DLNA 1.5 device)

Example:
When UPNP only, it takes about 4 seconds (this is what I currently use)
When DLNA 1.0 or DLNA 1.5, it usually takes 45 seconds to 1 minute.

My guess is that there is a error and perhaps timeout on the DLNA handshaking on connect.

Any ideas? Would an advanced or debug log be helpful in tracking down the problem?
(Note: I don't see this issue with my Dlink DSM-520 configured as DLNA 1.0)

Thanks.

[Eugene]

I have the LG BD-570 working well for the most part, but I noticed something strange.
When the device connects to the server, I get very different times depending on how the DLNA setting is configured.
(This is a DLNA 1.5 device)

Example:
When UPNP only, it takes about 4 seconds (this is what I currently use)
When DLNA 1.0 or DLNA 1.5, it usually takes 45 seconds to 1 minute.

My guess is that there is a error and perhaps timeout on the DLNA handshaking on connect.

Any ideas? Would an advanced or debug log be helpful in tracking down the problem?
(Note: I don't see this issue with my Dlink DSM-520 configured as DLNA 1.0)

Thanks.

Log file http://www.wildmediaserver.com/forum/vi ... p=833#p833

[k10ck3r]

While capturing the log files, I noticed that the first connect after a server restart works fine.
Once the device disconnects and then reconnects, the long connection times are seen.

Two log files are attached. The first one is the debug log file for the first connect after server restart (which worked fine). The second log file includes all information from the first log, but adds information for the next connect (which took over 30 seconds).

[Eugene]

While capturing the log files, I noticed that the first connect after a server restart works fine.
Once the device disconnects and then reconnects, the long connection times are seen.

Two log files are attached. The first one is the debug log file for the first connect after server restart (which worked fine). The second log file includes all information from the first log, but adds information for the next connect (which took over 30 seconds).

Delays in the 30 seconds is in the first and second log. Problems with the server in log not found. Try to apply to the server at the time of the delay by another device.

[k10ck3r]

A little clarification on the logs I submitted:

The first log ends at 15:09:09:834 (There was no delay on the connect to this point).

The second log continues from this point (I then did a disconnect and then reconnected). I see a couple of 30 second delays (15:09:38:050 to 15:10:09:096) and (15:10:09 to 15:10:33). I'm not sure which one is relevant, though the first one is for a subscribe event, so I think that it is probably it.

I did notice the following error later in the log:

15:10:33:682 Sender: SendResponse ba132a53-2ab4-4217-91b2-401a762f02f9
send response HTTP/1.0 403 Forbidden
Content-Length: 0
Date: Sat, 12 Jun 2010 15:10:33 -0700
Cache-Control: no-cache
Expires: 0
LAST-MODIFIED: Sat, 12 Jun 2010 15:10:33 -0700
EXT:
Server: Windows/6.17600 UPnP/1.0 Wild Media Server (UPnP, DLNA, HTTP)/1.02


Take a look at these time indices - hopefully that will help.

[Eugene]

A little clarification on the logs I submitted:

The first log ends at 15:09:09:834 (There was no delay on the connect to this point).

The second log continues from this point (I then did a disconnect and then reconnected). I see a couple of 30 second delays (15:09:38:050 to 15:10:09:096) and (15:10:09 to 15:10:33). I'm not sure which one is relevant, though the first one is for a subscribe event, so I think that it is probably it.

From the server side in log there is no problem, but maybe the device expects closing the connection or some other response. Working with subscriptions has been tested on Intel UPnP Tools - no problems. If there are no problems with Nero, then I can check his answers.

I did notice the following error later in the log:
15:10:33:682 Sender: SendResponse ba132a53-2ab4-4217-91b2-401a762f02f9
send response HTTP/1.0 403 Forbidden
Content-Length: 0
Date: Sat, 12 Jun 2010 15:10:33 -0700
Cache-Control: no-cache
Expires: 0
LAST-MODIFIED: Sat, 12 Jun 2010 15:10:33 -0700
EXT:
Server: Windows/6.17600 UPnP/1.0 Wild Media Server (UPnP, DLNA, HTTP)/1.02

This is normal, restriction of access devices

[k10ck3r]

Update:
With the latest LG firmware and the latest WMS configuration profile for LG BD, the 30 second delay no longer exists when DLNA is enabled.