i've tried all kinds to try and get the server to work, apparently something to do with NLM being stuck on local intranet.
co pilot has given me this for you
Message body
Hello MediaMonkey Support Team,
I’m having an issue activating MediaMonkey Gold on a Windows Server system, and I believe the problem relates to how the application determines internet connectivity rather than actual network access.
Environment
MediaMonkey for Windows (current version)
Windows Server (Domain Controller + RDS)
Static IPv4 configuration
Full internet access confirmed (browsing, DNS, outbound HTTP/HTTPS)
The problem
MediaMonkey activation fails with the message:
“There is a problem with your internet connection.”
However, the server does have verified internet connectivity.
Technical details
MediaMonkey’s debug log shows the following during activation attempts:
MyInternetGetConnectedState (using NLM) result: false
Windows itself is reporting:
Get-NetConnectionProfile → IPv4Connectivity = LocalNetwork
This occurs even though all Microsoft Network Connectivity Status Indicator (NCSI) probes succeed:
http://www.msftncsi.com/ncsi.txt → Microsoft NCSI
http://www.msftconnecttest.com/connecttest.txt → Microsoft Connect Test
So the machine can reach the internet, but Windows Network Location Awareness (NLM) does not mark the connection as “Internet,” and MediaMonkey appears to rely on that status.
What I’m asking
Could you advise on one of the following:
A supported workaround or configuration so MediaMonkey can activate on Windows Server / RDS environments
An alternative activation method that does not depend on InternetGetConnectedState() / NLM
Confirmation whether MediaMonkey Gold activation is supported on Windows Server systems
Is there a way of manually registering without connecting to the internet?