This maybe better serviced as an actual support ticket where we can help you a little better. I cannot actually raise a ticket for you from the forum but if you could do so we will assign an engineer to service your request promptly.

I believe what Carl was trying to say is that the port from the UMP to the primary server Distribution Server (distsrv) is blocked, not the UMP to Database. Licenses are kept by the Distribution Server. The port is randomly assigned at robot startup but I usually see the distsrv start up first so it snags TCP port 48005. You can look in Infrastructure Manager and see what port has been assigned to the probe and try to telnet to that port (from command prompt: telnet <server ip> 48005) and you should go to a black screen immediately. If it times out there is a firewall in place.

Even when I disable windows firewall, I still have to put in firewall rules allowing ports 48000-48050 open on the primary hub sometimes. Maybe try putting in an allow ports on the primary hub or allow all ports from the UMP?

I tried adding Port exceptions on both servers (2003 windows) and restarting them. Same error. The logs show unable to get license from distsrv but it should be able to reach it since the port is there and listening and open both ways. I dont have antivirus so thats not it. Any other suggestions?

Make sure the UMP server can connect to the TCP port of the distsrv... I know you have already checked the rules in the network and host firewalls, but you should also check with telnet from the UMP server if you have not done so already. Make sure to lookup the TCP port number currently assigned to the distsrv, which you can find in the Infrastructure Manager.

Make sure the nimaddress of the distsrv can be resolved... On the UMP server use the PU command to send a request to the nimaddress of the distsrv. You should be able to get a list of supported callbacks in the distsrv without logging in, but providing your username and password should let license_list callback work.

Make sure the dashboard_engine knows where to locate the distsrv... I am not sure how the dashboard_engine figures out the nimaddress of the distsrv. So if #2 works, maybe the dashboard_engine does not know the right nimaddress. I do not think this is a config option in the dashboard_engine by default, but there may be a way to force it to use the right nimaddress. At this point you may need Nimsoft to help you determine why the dashboard_engine cannot figure out the correct nimaddress for the distsrv.

I know some of this may be old news and/or things you have tried, but hopefully you can narrow down the issue by checking any of these possibilities that you might not have already.

I actually thought the UMP server was required to report to the "main hub" (or core/root/central/SLM hub if any of those terms make more sense). I am fairly certain that was the case at one time, but that might not be a requirement any longer. Have you verified that it is okay to have the UMP server report to a different hub? (Or you might not care as long as it works.)

Faisal in Support had me do that and he says it should be ok. I have had it there for almost a half a year and the only 2 things that were broken were the UR and Dash Designer everything else worked fine. I hadnt used the Designer until now, I used LUA and the API to build dashboards. And the UR I hadnt needed since the Report scheduler but now it works as well. All your steps checked out and i thought i was going crazy cause i could reach the main distsrv fine. I guess wherever the UMP is the HUB its under must contain the licenses as well. Thanks for all your help!