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 ...
Search found 3 matches
- Sat Jan 10, 2015 1:06 am
- Forum: Help and Support
- Topic: Media renderer was not recognized
- Replies: 4
- Views: 6750
- Sat Jan 10, 2015 12:48 am
- Forum: Help and Support
- Topic: Media renderer was not recognized
- Replies: 4
- Views: 6750
Re: Media renderer was not recognized
Samsung All Share
I can see it connected on Status.
I can see it connected on Status.
- Fri Jan 09, 2015 8:42 pm
- Forum: Help and Support
- Topic: Media renderer was not recognized
- Replies: 4
- Views: 6750
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 ...
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 ...