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

Question

Question

Generating PDF (to print) from Weblink

asked on February 13, 2017

We have Weblink 9.0.0.259, and have installed a firewall (Meraki) for one remote site. 

 

Since then, no users for that sites can generate PDF to print from Weblink. 

 

Same user travels to other remote sites, she can open the same scanned file and generate PDF just fine. 

 

See below screenshots for an example, they don't get any issues at other sites. 

 

Does anyone have clue what ports need to be allowed on firewall to allow users generate PDF from WebLink?

 

Tried Firefox, Chrome, IE11 but the same result. Any help would be appreciated. thank you

 

 

 

 

0 0

Answer

SELECTED ANSWER
replied on February 15, 2017

If the ports are blocked by the firewall, Weblink inside the firewall will not work. 
1. Have you checked your firewall rules? 

2. Try disabling all the firewall rules temporarily and download one of the LF Sample files.  Does that work?  If it does, start enabling them one at a time and test each time until you are able to reproduce the issue.

3. Are users on the problem location using a web proxy? Does the download work when you don't use the proxy?

4. Get the network admin to run Wireshark from a computer inside the problem (site) network and from a computer inside the working network (site)  to monitor the packets. He'll have to read both traces and compare them.

0 0

Replies

replied on February 15, 2017

It's not a matter of ports, the pdf download goes over the same 80 or 443 that the rest of the data uses.  More likely, it's a file size limit being imposed by the firewall, or something like that.  A tool like Fiddler should show you the data that's returned, it's possible that the firewall is trying to show an error message but that it's instead being interpreted as the expected pdf file.

1 0
replied on February 14, 2017

What version of Acrobat is the problem user using?

As for ports, the default ports used by Weblink are port 80 for HTTP and 443 for HTTPS.  This applies to version 9 and 10.  Note that these are default ports which can be changed in IIS.

0 0
replied on February 14, 2017

We have 11.0.19 Adobe Reader installed on both computers in working site as well as non-working site.

 

Port 80 and 443 are already open. If these two ports are blocked, are we able to access WebLink itself to view the document itself on WebLink?

0 0
replied on February 14, 2017

How many Weblink installations do you have?  You noted that you "have Weblink 9.0.0.259, and have installed a firewall (Meraki) for one remote site."  Are the problem clients and working clients connecting to the same Weblink instance?

0 0
replied on February 14, 2017

yes we have one Weblink, and working and non-working sites/ clients connecting to the same weblink, same LF server. 

0 0
SELECTED ANSWER
replied on February 15, 2017

If the ports are blocked by the firewall, Weblink inside the firewall will not work. 
1. Have you checked your firewall rules? 

2. Try disabling all the firewall rules temporarily and download one of the LF Sample files.  Does that work?  If it does, start enabling them one at a time and test each time until you are able to reproduce the issue.

3. Are users on the problem location using a web proxy? Does the download work when you don't use the proxy?

4. Get the network admin to run Wireshark from a computer inside the problem (site) network and from a computer inside the working network (site)  to monitor the packets. He'll have to read both traces and compare them.

0 0
replied on February 15, 2017

Thank you Raymond, 

 

Meraki has AMP feature enabled (Adv. Malware Protection), that needs to add whitelist of Laserfiche URL, since then everything started working. Thank you for guiding me to the right direction. 

 

AMP file scanning: the “Malware detection” selector on the Security Filtering page in Dashboard now enables AMP.  When AMP is enabled, downloaded files will be checked against the global AMP database to ensure that they are not malicious before they are allowed to enter the network.

0 0
replied on February 15, 2017

Glad it works for you!

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

Sign in to reply to this post.