Make sure that the Windows Firewall is configured to allow incoming connections to MMW.Try updating to the latest version of MMW–it will reinstalling the firewall rules, possibly solving the problem. If the problem started after installing a Windows Update, the issue may be that firewall settings were reset.Ensure that firewalls aren’t blocking the connection.If it isn’t listed, then try connecting with MMA to the MMW UPnP/DLNA server, and MMW will prompt you to enable access to the client (alternatively, you can enable ‘Share automatically with all new devices’ though this may not be desireable if you want to limit access to the library). Double click the server (it’ll be named something like ‘MediaMonkey Library’), and make sure that the IP address/MAC address of the client is checked off in the ‘Enabled’ column.In MMW, click Tools > Options > Media Sharing, and verify that a server is enabled and running.Verify that the server is running and configured correctly:.

If your DLNA client can’t access content on the server or MediaMonkey can’t cast, please try each of the following:

When no Media Server is enabled in MediaMonkey casting will use a temporary server with a random port to be able to cast media. When you Cast/Stream from MediaMonkey to a Chromecast/DLNA client MediaMonkey also requires access from your Firewall. DLNA/UPnP clients or Wi-Fi Sync clients such as MediaMonkey for Android (MMA) may fail to access content shared by the MediaMonkey for Windows (MMW) DLNA server due to a variety of networking, security/access control issues, or configuration issues that prevent the server from announcing it’s availability and/or sharing content.

Windows upnp player