Question

Forms Configuration 404 Not Found Error when adding the Laserfiche Workflow Server

Workflow Forms

Updated December 2, 2016

asked on November 28, 2016

I used a real server name.

Occurs when I use IIS IP Address and Domain Restrictions with a Default Deny. I added a list of Allowed IP's which include the Forms Server (local to Workflow) but only works when the the below "Access for Unspecified Clients" is Allow

0 0

Replies

replied on November 28, 2016

Hi William, I cannot reproduce this.

I mimicked the described settings on one machine with Workflow Web Services installed, and provided the IP address was given an Allow Entry in the IP Security feature, Forms on both a remote machine and the local machine were able to authenticate correctly. If there is something different from your configuration, based on the attached screenshot, please let me know and I can try again.

What IP address did you use to allow traffic for the local machine? In particular, does the machine have both a public and an internal network IP address? Is the IP address being used the same one which shows when pinging the machine by SERVERNAME (i.e. what you had entered in the config field for Workflow server)?

ipsec.png (54.97 KB)

| Download

0 0

replied on December 2, 2016

Interesting thing is it does work using the IP.

This Server is not part of a domain and I had a known issue with Quick Fields Server due to that.

However I have the same policy on other Web Applications ie. LFDS, Audit Trail and connecting via the browser using the machine name works fine.

In fact connecting via the browser to Workflow and WF works fine as well. I do require SSL.

0 0

You are not allowed to follow up in this post.

Question

Question

Forms Configuration 404 Not Found Error when adding the Laserfiche Workflow Server

Replies

Sign in to reply to this post.