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

Question

Question

How to set your source IP on the workflow server so that Forms can connect?

asked on November 2, 2020

I am trying to google how to choose which source IP the system should refer to itself as when making network communications since we found the requirement from Laserfiche to do so.

Every blog post and stack post I read says that starting with Windows 2008 Microsoft revoked this capability. It now selects as it pleases based on a number of factors, when you have multiple NICs and IPs assigned.

But Laserfiche is requiring we use a specific source IP for all network communications from Workflow to Forms, so how can I use the newer Windows operating systems to connect Forms and Workflow together if I can not explicitly define this?

0 0

Replies

replied on November 2, 2020

Chad, please open a support case for these issues. Laserfiche does not have any specific or custom requirements and it relies on the underlying OS/domain's name resolution.

0 0
replied on November 2, 2020

But only when connecting Forms to Workflow to we receive this error and associated requirement, [LFF5206-WFAPIAccessDenied].

Forms connects to the repository just fine of any IP address, Chrome connects to the workflow web service just fine over any IP address.

Windows connections like UNC allow connection on any IP address as well.

In general Windows doesn't care how many addresses you want to have or what address you want to use

0 0
replied on November 2, 2020

The error you're getting is likely indicating that name resolution already happened and it was fine.  That is why I think this will be better investigated through a support case. We're talking about a non-standard configuration, so I'd like to make sure we're getting the full picture rather than guessing at what the issue might be in an incomplete picture.

0 0
replied on November 2, 2020

Ok I will give it a try

0 0
replied on July 20, 2022

What was the resolution for this scenario?

 

0 0
replied on July 20, 2022

I can't remember the very specifics but I do remember finding a Microsoft article which explained that you can not have direct control of this, Windows determines it by default based on the order in which you installed your network card drivers or something.

The customer had to keep sending the traffic through the network card they did not want to use so that the source IP would match up.

They had a network card that was being used for the SAN and they did not want general network traffic going through it, but in the end they had to so that Forms would function.

0 0
replied on July 20, 2022

So you used the hosts file to force it?

0 0
replied on July 20, 2022

Yes, exactly, sound right. We made sure Forms was hitting WF on the internal IP of the network card that would have the proper "Master Source" IP.

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

Sign in to reply to this post.