You are viewing limited content. For full access, please sign in.

Question

Question

Laserfiche forms portal ports 5048 and 5049

asked on October 24, 2022

Hi friends.,

We are using Laserfiche 11. We have 2 servers for forms, one for our internal use and one that will be the public one. For now, we don't have a DMZ, so, the Public server for Forms is basically in the same Network. We know that is not recommended and is not safe, but for now, we just need to finish the configuration of that server. The consultant helping us with the installation is requesting that ports 5048 and 5049 should be open and listening on the forms server. We can see those ports listening and working on the LFDS server, but not on the Forms Public server. We are trying to find documentation that supports that configuration because we haven't managed to have the Laserfiche Forms server listen on those ports unless a service is installed on that server and the service is actively listening on those ports. Any clue? should we have the second Forms servers actually listening on those 2 ports even when the documentation we find says is the LFDS server that should be listening on those ports?

0 0

Answer

APPROVED ANSWER
replied on October 24, 2022 Show version history

Hi Maria,

The LFDS Windows Service is the only Laserfiche component that listens on TCP ports 5048/5049. As such, inbound firewall rules need only be open for those ports on the server hosting LFDS.

I suspect there was misinterpretation of documentation/guidance somewhere mentioning that servers hosting other Laserfiche components must have outbound connectivity allowed to reach LFDS on those ports. We've seen network communication issues from firewalls in both directions.

Run these two commands in PowerShell from the Forms server after updating the LFDS server placeholder value. If they both return "true" for TCP connection test success, you're good for Forms -> LFDS network connectivity.

Test-NetConnection 'lfdsServerFQDN.example.com' -Port 5048
Test-NetConnection 'lfdsServerFQDN.example.com' -Port 5049

Since this server is public facing, you should restrict access to the /FormsConfig IIS application endpoint to only localhost (127.0.0.1) or intranet IPs for added security as described in the link below. You don't want outside parties to be able to attempt to access the config page over the internet.

https://answers.laserfiche.com/questions/199591/Hide-httpsservernameformsconfig-page#199593

0 0
replied on October 25, 2022

Thanks Samuel for the clarification

1 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.