yocker 1247 Posted May 13, 2025 Posted May 13, 2025 5 hours ago, mattl1979 said: That's interesting. Not sure why Emby would be different than any other DLNA server I've tried. I've tried a multitude of installations for Emby as well, including native to Synology, through a Docker container on Synology, directly on my Windows PC, and on a Docker container on my Windows PC. No installation method made a difference. I don't know how I'd assign a specific private IP to just Emby. Docker containers can be assigned their own IP depending on what network type/mode you assign them, fx. Bridge, Host, Br0 and so on. If you have the option try setting it to using Br0, then you should be able to give it it's own IP. Other wise i suggest looking up how to make a docker container compose. It should be there some where.
mattl1979 3 Posted May 15, 2025 Posted May 15, 2025 FINALLY got the DLNA server to work in my environment. The key information which helped was in https://lookanotherblog.com/resolve-port-1900-conflict-between-plex-and-synology/. For whatever reason, the Synology Windows network discovery service (minissdpd) was utilizing port 1900. So while EVERY OTHER application like Jellyfin, Plex, and the like seemed to not care and still worked, Emby had trouble grabbing control of the port. Once I disabled that service, the DLNA server showed up in a few minutes on my Windows PC and my other client devices. The separate IP address made no difference in my case. I tried with a host network and a bridge network. 1
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