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

Question

Question

Webtools Agent Scanning Packet Type

asked on November 14, 2023

Hello, 

I have a client who is setting up their Web Client to be used by the public.  They are attempting to allow scanning but are having some issues identifying how the Webtools / Scanning client used with Laserfiche Web Client communicates with the server.  They are reporting seeing SMB when viewing traffic with Wireshark and are hoping that it is using some sort of web service to send that data instead.

0 0

Replies

replied on November 14, 2023

It does use a web service to send the scanned data. None of our client-server data is sent using SMB.

1 0
replied on November 14, 2023

Is there a whitepaper or article detailing the specific ports or protocols required to send the data using the Scanning Tool? When using the Web Client outside of our network, it doesn't recognize that its there and requests that it be installed again.

An example of the error we see in the Web Client is attached as well.

error.png
error.png (25.93 KB)
0 0
replied on November 15, 2023 Show version history

Web Tools Agent only uses https/443 to communicate with the remote web client server. What you see there is the html page running in the browser attempting to communicate with the Web Tools Agent running on the local machine. This is the mechanism it uses to e.g. launch the scanning application. Those are the 3 ports that it will attempt to use. It sounds like your machines are set to use different firewall rules when attached to different networks, and you'll need to update those. But note that this is kind of an unusual connection as it's between processes on the same machine - you don't need to allow remote requests on those ports, just local ones.

1 0
replied on November 16, 2023

Brian, the Debug Information for Port 18345 "ErrorValidatingSecurityToken: Invalid JSON primitive: ..." jumped out as odd to me. That doesn't sound like a network error.

Brent, are you by any chance using a load balancer/reverse proxy with cookie-based session affinity in front of multiple Web Client instances?

0 0
replied on November 16, 2023

I think you're right. Probably the page was able to successfully connect to the agent, but the agent was not able to connect to the web client machine.

0 0
replied on November 20, 2023

Samuel, yes, you are correct about the following: 

Brent, are you by any chance using a load balancer/reverse proxy with cookie-based session affinity in front of multiple Web Client instances?y

 

We feel this is probably a problem we will need to resolve on our end, but any possible solutions or helpful advice would be appreciated.

0 0
replied on November 15, 2023

Thank you for the information - this really helps. We are going to do a little more testing on our end and will let you know if we have any more questions.

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

Sign in to reply to this post.