Question

Communication Ports between License Manager and AD

Laserfiche Administration Licensing License Manager

Updated September 10, 2014

asked on August 26, 2014

I would like to know if there is any specific port that License Manager uses to communicate with AD, other than the default 5048 port?

We have the following setup and running into communications issues:

We have 3 LF environments, PROD, QA and DEV. The DEV environment is closed off from the normal PROD network to avoid accidental communication to any of the other PROD systems running.

Our License Manager is installed on our PROD LF Server and communicates successfully with the LF Server in Dev and is able to communicate and inform the DEV server of licenses allocated to it. This was done when we had opened the relevant port to that server etc.

We are now trying to switch over to a Windows Accounts based architecture and need to test this in our DEV environment. The challenge is that the DEV environment contains its own AD that only broadcasts in that secluded environment. So by default when addig a new Named User on License Manager, it is the one from the PROD AD and when the user is allocated on the DEV LF Server, it does not pick up that it has a Named Licenses. in QA and PROD it registers the User correctly.

I then tried to add a location on License Manager to include the AD from the DEV environment, but get back a "Access Denied" error. The account being used does have sufficient rights on the DEV AD so it cannot be that. I also used telnet to establish that port 5048 is open between the Server hosting the LM instance and the DEV AD server.

therefore my assumption is that it must be using a different Port for communication, or is there something else that I am missing?

0 0

Answer

SELECTED ANSWER

replied on August 26, 2014

License Manager communicates over port 5048 (5049 for https). Are DEV and PROD on two different domains? If so, there must be trust between the two domains. If the License Manager service account has access to the DEV AD machine, ports are open, and the domains are trusted, consider opening up a case with Support to get to the bottom of the issue.

0 0

replied on September 5, 2014

Thanks for the Info Zachary.

Will update shortly.

0 0

replied on September 10, 2014

Just an update:

After a new Domain was created in our Dev environment and the trust relationship setup, then License Manager was able to correctly communicate with that Dev AD and I was able to allocate the users.

1 0

Replies

replied on September 2, 2014

Hi Vincent,

If your question has been answered, please let us know by clicking the "This answered my question" button on the appropriate response.

If you still need assistance with this matter, just update this thread. Thanks!

0 0

replied on September 5, 2014

Hi Kelsey,

I should know after today if the information provided helped. Our IT is in the processes of setting up a separate Domain in the Dev environment and will then be able to setup the Trust relationship. the original setup was that Dev was a image Copy of the Production but in a secluded segment of the network and could not communicate externally. So a Trust relationship could not be created as it would be seen as a duplicate domain.

I'll give another update to this once everything is up and running and I've had a chance to test.

0 0

replied on September 5, 2014

Great, thanks!

0 0

You are not allowed to follow up in this post.

Question

Question

Communication Ports between License Manager and AD

Answer

Replies

Sign in to reply to this post.