We have a cloud environment where Laserfich and our development (SDK) server live. We have DNS Doctoring turned on in our firewall to allow us to hit laserfiche from within the same network. It works fine from a browser. However the SDK fails to connect. If we try the same code from outside that cloud environment it works fine. SO I have validated the code is good and that the site is reachable within the network but the SDK still fails to connect to it. My question is this. Since DNS Doctoring inspects DNS packets as they come and go through the firewall....is it possible that the SDK is wrapping that request or somehow making it so that the firewall does not see a DNS request therefore DNS doctoring fails to work and the connection fails to be made? Does that make sense?
Question
Question
Replies
replied on April 20, 2017
Assuming you are talking about the .NET SDK (Laserfiche.RepositoryAccess.dll), there is no custom DNS handling going on. Are you getting a specific error message when it fails to connect?
0
0
replied on April 21, 2017
Hi Robert, I'm the solutions engineer who was assigned a ticket for the issue Matt Duncan is having and I recommended that he post his question here first, since other users may have encountered the issue, and the java SDK is outside of my training. Would you recommend a ticket be created to get this resolved?
0
0
replied on April 20, 2017
This is actually the Java SDK. We have pulled it apart and are going to debug it today. Will post back with the specific error we are seeing.
0
0
You are not allowed to follow up in this post.