Many problems on Samsung UE40D5720 TV

Hey! I'm encountering many problems, after serviio just working fine for s short while.

The first few days everything worked as it supposed to be, but then I get one problem after another

First from one day to another the TV just doesnt seem te recognize Serviio, the solutions in the FAQ dont work! I tried setting the bound IP to the tv's and opening the correct ports also dont work.

Then I reinstalled, it finally recognized Serviio, but this time when I tried to open a file it says: Does not support file format (I tried opening a file that a day ago was supported....)

If I try to restart Serviio, I get an error message saying "cannot connect to serviio server - it does not appear to be running"

Again I reinstalled and now I cant even install it, this time at 10% during installation it says "Error opening file for writing" log4j.xml


What can I do?? And howcome in the beginning it was working just fine....

[Cerberus]

Hey! I'm encountering many problems, after serviio just working fine for s short while.

The first few days everything worked as it supposed to be, but then I get one problem after another

First from one day to another the TV just doesnt seem te recognize Serviio, the solutions in the FAQ dont work! I tried setting the bound IP to the tv's and opening the correct ports also dont work. ( set to IP of PC running serviio not the tvs IP)

Then I reinstalled, it finally recognized Serviio, but this time when I tried to open a file it says: Does not support file format (I tried opening a file that a day ago was supported....) (make sure you have correct profile for your device selected in the console)

If I try to restart Serviio, I get an error message saying "cannot connect to serviio server - it does not appear to be running" (caused by serviio console starting before pc has started the network adaptor http://wiki.serviio.org/doku.php?id=net_reboot )

Again I reinstalled and now I cant even install it, this time at 10% during installation it says "Error opening file for writing" log4j.xml


What can I do?? And howcome in the beginning it was working just fine....
(uninstall serviio COMPLETELY then reistall it)

all of these issue are common and could of been solved by searching these forums or by consulting the Wiki pages linked ( wiki under construction still so some thing maybe missing)

So I did, I think I struggled 5 hours in total before I opened a topic...

The solutions you provide I already tried

Where can I find my computers ip address if i may ask?

[Cerberus]

run command IPconfig from CMD prompt.

OK, im at the point again the tv fails to recognize Seviio.

I used the correct bound IP address and I forwarded the correct ports... Now what?

Restarting the computer or the television doesnt work

[Cerberus]

viewtopic.php?f=5&t=1289

[Mugwump]

Hey! I'm encountering many problems, after serviio just working fine for s short while.

The first few days everything worked as it supposed to be, but then I get one problem after another

First from one day to another the TV just doesnt seem te recognize Serviio, the solutions in the FAQ dont work! I tried setting the bound IP to the tv's and opening the correct ports also dont work.

Then I reinstalled, it finally recognized Serviio, but this time when I tried to open a file it says: Does not support file format (I tried opening a file that a day ago was supported....)

If I try to restart Serviio, I get an error message saying "cannot connect to serviio server - it does not appear to be running"

Again I reinstalled and now I cant even install it, this time at 10% during installation it says "Error opening file for writing" log4j.xml


What can I do?? And howcome in the beginning it was working just fine....

I don't want to raise too much of an alarm but by any chance did you just update the D series firmware on the TV?
I just encountered the same problem with a different D series device and had to do some very serious mucking around to get it to work again...I set everything to dhcp in my router ...no bound addresses and then tracked down which device was really the Samsung D series. After I did that then I reset to the correct profile every time the router re-assigns to a different local network address in the 192.168 series of dhcp addresses that routers use for common network address translation routing.

I hope that a Samsung Series D update did not just mess things up for UPNP servers like Serviio and others.... but this might just be the case. As they have been aggressively changing their firmware for the D series devices recently. Including possibly the device broadcast identity method. Guess it all depends on with model and if they changed the core identification methods for your firmware.

If you did not do an update then I would suggest that you go back to straight dhcp protocol on the tv and the router and see if it shows up as a generic profile device in the console that you can then set to the correct Samsung profile....this is what happened to me.
But I have the device working again.

[zip]

I hope that a Samsung Series D update did not just mess things up for UPNP servers like Serviio and others.... but this might just be the case. As they have been aggressively changing their firmware for the D series devices recently. Including possibly the device broadcast identity method. Guess it all depends on with model and if they changed the core identification methods for your firmware.

There is no such a thing as a device identification in the spec, really. Serviio uses different methods to identify devices and they should be enough. If they changed model name, for example, that would be a simple change in profiles.xml so no need to panick.

[Mugwump]

There is no such a thing as a device identification in the spec, really. Serviio uses different methods to identify devices and they should be enough. If they changed model name, for example, that would be a simple change in profiles.xml so no need to panick.

That's what I hoped was happening...Just the device "friendly name" does not even show up in my case but the fact that it is a dlna generic does??? Here is what shows up in the tools set.

  Code:

Location http://192.168.1.102:52236/rcr/RemoteControlReceiver.xml
UDN uuid:6155014c-7fbd-4dc2-9a20-0d5f4b63631d
Type urn:samsung.com:device:RemoteControlReceiver:1
Base URL http://192.168.1.102:52236/rcr/RemoteControlReceiver.xml
Friendly Name x\Uffffffff,x\Uffffffff,
Manufacturer Samsung Electronics
Manufacturer URL http://www.samsung.com/sec
Model Description Samsung BD RCR
Model Name BD-D5300
Model Number 1.0
Model URL http://www.samsung.com/sec
Serial Number 20090804RCR

And looking at what it sends out now as a "friendly name" is different than the C series devices.... it is in binary form not text. So my control point interface does not pick it up and I cannot remotely control it at all or push files, the way I can with the our older C series tv....Even though I set the security settings in the D series device to allow this functionality.

So perhaps not showing up as a named device is what is happening to quite a few Samsung D owners.

[zip]

this is not the correct UPnP device, it's remote control receiver, not renderer.

[jhb50]

jorickdd: See my PM

Thanks for your help. But I was being told to enter the IP address of the machine Serviio was running on, instead of the device I wanted to play the video files on?

[zip]

that is correct, IP of the Serviio machine

[jhb50]

My bad..not enough sleep I guess.
Can you post your log after setting DEBUG on?
I assume you have other PC's at 11 and 15.
Is your Serviio PC set with a Static IP to 10?

[Mugwump]

this is not the correct UPnP device, it's remote control receiver, not renderer.

UPDATE rest of post removed I have the taste of black coloured feathers in my mouth again and I apologise to both Zip and ghb50 as I see you both have jumped through the renderer difficulties for devices that show up as a Samsung BD RCR viewtopic.php?f=5&t=2712 so not showing up as a renderer is already a known problem.

I will try to help by doing some serious internet snake work and find out a little more about the D series methods...finding things that are hidden or if not hidden, at best being obscured by design is something which I am really good at.
If I find something that is might be useful I will pm you guys to see if it will help make these ubiquitous Samsung D Series devices work better.

Till then setting a designated device address set to the C/D profile for these puppies might be the best answer available for those who have similar problems.