Media renderer was not recognized
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Media renderer was not recognized
Using
Windows 7
UMS 4.3.1
Problem description:
Configuration of UMS or network has not been changed.
Nevertheless UMS cannot find media renderers.
"Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18"
Ports in firewall are open.
Please help.
Windows 7
UMS 4.3.1
Problem description:
Configuration of UMS or network has not been changed.
Nevertheless UMS cannot find media renderers.
"Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18"
Ports in firewall are open.
Please help.
Re: Media renderer was not recognized
Which renderers are you using to try to connect to UMS?
-- UMS serving PS3, WDTV, Samsung H6400 + J5500 and Kalemsoft renderers! (no video transcoding but remuxing accepted 
)
)Re: Media renderer was not recognized
Samsung All Share
I can see it connected on Status.
I can see it connected on Status.
Re: Media renderer was not recognized
01-09 14:00:20 Using forced address 192.168.2.102
01-09 14:00:20 Created socket: /192.168.2.102:6001
01-09 14:00:20 Using the following UUID configured in UMS.conf: 82c5be6b-93e2-4911-bde6-906074d11118
01-09 14:00:20 No IP filter specified, access granted to /192.168.2.100
01-09 14:00:20 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:00:21 The server is now available for renderers to find
01-09 14:00:31 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:00:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:03:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:04:20 No IP filter specified, access granted to /192.168.2.168
01-09 14:05:30 No IP filter specified, access granted to /192.168.2.102
01-09 14:06:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:09:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:12:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:15:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:00:20 Created socket: /192.168.2.102:6001
01-09 14:00:20 Using the following UUID configured in UMS.conf: 82c5be6b-93e2-4911-bde6-906074d11118
01-09 14:00:20 No IP filter specified, access granted to /192.168.2.100
01-09 14:00:20 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:00:21 The server is now available for renderers to find
01-09 14:00:31 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:00:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:03:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:04:20 No IP filter specified, access granted to /192.168.2.168
01-09 14:05:30 No IP filter specified, access granted to /192.168.2.102
01-09 14:06:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:09:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:12:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
01-09 14:15:51 Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18
Re: Media renderer was not recognized
If you can see it connected on Status, what's the problem? That log message is probably about another renderer