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

Question

Question

Understanding this DS error "remote server could not be resolved"

asked on August 19, 2021 Show version history

A user gets this error at the DS server landing page after logging in, but only 1 user. My user account works just fine.

We tried entering the server name, global DNS name, and many other things into the text field.

What does this error mean? What is it asking for? What does it mean by "forms"? I don't believe any server is named "forms".

Also what does it mean by remote server, I feel like when you visit a web page, the web host is the remote server and if the web page displays I have resolved the server. It is like going to Google.com and it says "The remote server can not be resolved" but that message is coming from Google.com

0 0

Replies

replied on August 20, 2021

Hi Chad,

This error is getting thrown by the web front-end, indicating that it cannot reach LFDS (the back-end server).

If this is only happening for one user, it might be a caching problem where an incorrect server alias is stored for a particular user. You may want to file a support case for this including:

  1. a full screenshot of the page (including URL bar)
  2. a copy of C:\ProgramData\Laserfiche\LFDS\UserSettings.config
  3. the problem user's AD SID
  4. a working user's AD SID
  5. a HAR trace of a login attempt in incognito mode
0 0
replied on August 20, 2021

It is saying that the IIS application LFDS can not see the Windows Service Laserfiche Directory Server?

And it thinks the host name of the Windows Operating system is "forms"? I am almost sure "forms" does not resolve to anything. Where is the configuration for the connection between the IIS site and the Windows Service?

0 0
replied on August 20, 2021

Yes, the website is being told to reach the service at the wrong location. The IIS site configuration is located here: C:\Program Files\Laserfiche\Directory Server\Web\LFDS\Web.config

But I don't think you will find the issue there, as only one user is affected. I think the issue will be seen in the places I mentioned above. Try checking for the string "forms" in C:\ProgramData\Laserfiche\LFDS\UserSettings.config

1 0
replied on August 20, 2021

I have seen this before and it was caused by an entry in the UserSetting.config file as Chase described. No actual backend server communication issues, just a bad location reference that was easy enough to fix.

2 0
replied on August 25, 2021

I am reviewing this file. It has a hostname, which is the local server hostname (not "forms") and an IP Address. Both are correct, not sure what to fix.

Also since there is only one UserSettings.config, wouldn't the same file be used when I login to the website compared with when the problem account logs in?

Why would it work for me and not for this one user?

0 0
replied on August 25, 2021

Please file a support case for this so we can take a closer look, and include:

  1. a full screenshot of the page (including URL bar)
  2. a copy of C:\ProgramData\Laserfiche\LFDS\UserSettings.config
  3. the problem user's AD SID
  4. a working user's AD SID
  5. a HAR trace of a login attempt in incognito mode
1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.