Knowledgebase: UPnP / DLNA
MediaMonkey for Windows cannot access a UPnP Server
Updated by Russell Samuels on Oct 13, 2016

If you're on the same network as the server and receive an error that a UPnP server that you've configured cannot be reached,

  1. In the case of a server that has been discovered by MediaMonkey, it may be because:
    • the server has been turned off; verify the server config.
    • a firewall is blocking the connection; verify your firewall rules.
    • there may be a network connectivity problem; try resetting the router and/or UPnP server.
  2. In the case of a server that you've manually entered, verify that you're using the correct protocol (http or https), port number, and entered the incorrect path to the devicedescription.xml file (different UPnP servers use different paths and different filenames).


If you want to use MediaMonkey from a different network than the server, you'll need to first successfully configure a local connection (see above) and then either:

  1. 'Configure remote access' to automatically reconfigure MediaMonkey to connect to the server via your router's external IP address and to reconfigure your router to forward such connections to the UPnP media server.
    If this fails, it may be because your router doesn't have UPnP/NAT-PMP auto-configuration functionality enabled.

  2. 'Add Media Server Manually' and configure MediaMonkey to try to connect to the server via your router's public IP address (rather than the IP address of the server behind the router), and then manually set up port forwarding in order to be able to access the server from another network. If you receive an error after doing so, it can be because:
    • forwarding is configured incorrectly
    • a firewall is blocking one or more of the ports used by UPnP (e.g. port 5000/5001, TCP port 2869, UDP port 1900).
(8 vote(s))
Not helpful

Comments (0)