Question

LFDS-Unable to get information for the machine (LFDS1000)

Laserfiche Directory Server Version 10 Licensing

Updated July 26, 2021

asked on July 23, 2021

Hello,

Customer tried to register a workstation with a QF Instance in LFDS and received the message "Unable to get information for machine (Machine Name). (LFDS1000).

Machine is on the same domain as LFDS.

We tried renewing the Master License to see if that would help, but it did not.

We were able to ping the machine from LFDS as well as run a Trace Route to it.

We did go the route of running the showhwfp.exe on the workstation to get the HWFP to complete the QF install.

Of another note, when they tried selecting the LFDS server for licensing when initially installing QF, they received an error that LFDS could not be reached.

They could also ping the LFDS server from the workstation.

We could find nothing in the Directory Services->Server->Operational Trace logs to point to the issue.

Wanted to see if anyone else has encountered this issue and how to resolve it other then the manual running of showhwfp.exe to get the HWFP.

Appreciate the feedback,

Jeff Curtis

0 0

Replies

replied on July 26, 2021

We have a similar issue when getting a license from LFDS. We are using a proxy server and have to go into internet options and turn the proxy off then the software will get a license. We have the option set in internet options to Bypass proxy server for local addresses but evidently our proxy still doesn't pass LFDS traffic.

1 0

replied on July 26, 2021

Hi Jeff, is port 5048 open between the two machines?

0 0

replied on July 26, 2021

Hello Chase,

Good Point...I am checking with the customer

Jeff

0 0

replied on July 26, 2021 • Show version history

Hey Jeff,

Try in PowerShell from the client computer:

Test-NetConnection 'LFDSServerFQDN' -Port 5048

That will tell you if the client computer can open a TCP connection to the LFDS server on port 5048. The output will have a field like "TcpConnectTestSuccess: [True/False]" indicating the result.

If it fails, you know you the issue lies with a firewall (or possibly proxy, as Craig mentioned).

Ping tests aren't particularly useful for troubleshooting issues like this beyond validating DNS resolution. ICMP pings don't tell you if the port of interest is open and firewalls are often configured to categorically block ICMP traffic. The Test-NetConnection PowerShell command (alias "tnc") is much more helpful in this regard and should be your go-to for port connectivity checks.

Cheers,
Sam

1 0

You are not allowed to follow up in this post.

Question

Question

LFDS-Unable to get information for the machine (LFDS1000)

Replies

Sign in to reply to this post.