Killervette 5 Posted February 10, 2015 Share Posted February 10, 2015 I have a Samsung UN65HU8550 TV. I had MB3 server on a windows box. the DLNA would work fine except for any channels such as Trailers. I changed to Ubuntu 3.0.5518.0 today. DLNA will not work at all anymore. Attached is the log file. Anytime I try to play to the TV I get "The remote server returned an error: (500) Internal Server Error." This is for any video file or channel. Files that used to work no longer work. Please advise Log.txt Link to comment Share on other sites More sharing options...
Killervette 5 Posted February 11, 2015 Author Share Posted February 11, 2015 (edited) I did a clean Windows 7 64bit install. Full updates. Then i installed MB3 Server release version. In the settings admin side i see the Active Devices that have DLNA support and that used to work on my old install. When i click the Play To Remote button to choose my device, nothing is listed. I then installed MB Client Classic on the server and launched it. It would show up in the Play To options. Attached is full log from launch to viewing of the Play To menu. I have also tried the latest Beta and Dev builds with no change. Other PCs in my house can play to the DLNA devices just fine. Log.txt Edited February 11, 2015 by Killervette Link to comment Share on other sites More sharing options...
Killervette 5 Posted February 12, 2015 Author Share Posted February 12, 2015 anybody? Link to comment Share on other sites More sharing options...
Killervette 5 Posted February 12, 2015 Author Share Posted February 12, 2015 Forget it. Clean install with beta fixed it Link to comment Share on other sites More sharing options...
Luke 37128 Posted February 12, 2015 Share Posted February 12, 2015 Unfortunately the nature of dlna is that it requires individual testing on devices, so we don't always know the answers to these kinds of questions. It's a feature that is very much community driven and we rely on each other for knowledge sharing. When there's a problem such as this the best way for them to get resolved is for a knowledgeable community member who has your same device to help out. Link to comment Share on other sites More sharing options...
Killervette 5 Posted February 12, 2015 Author Share Posted February 12, 2015 Unfortunately the nature of dlna is that it requires individual testing on devices, so we don't always know the answers to these kinds of questions. It's a feature that is very much community driven and we rely on each other for knowledge sharing. When there's a problem such as this the best way for them to get resolved is for a knowledgeable community member who has your same device to help out. Understood. At least this part is fixed. Thanks Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now