As of File Director 4.1U1 we disable TLS 1.0 by default for PCI compliance. If your browser (or proxy server) is not configured to allow TLS 1.1 or 1.2 this could be the cause.
The admin console can only be served over SSL (port 8443) - If you are getting a login box over HTTP, this will be the web client, to which the 'appliance' account has no relevance.
Can you try connecting directly to the appliance from an endpoint with TLS 1.1 or 1.2 enabled in the browser and see if this allows you to connect (the web admin url is https://<appliance>:8443)
Once you're in the admin console, you can re-enable TLS 1.0 if required via the 'advanced' tab, although the recommended approach (for best security) is to ensure any connected devices support, and are configured to use TLS 1.1+ - https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1.1-and-tls-1.2-as-a-default-secure-protocols-in-w…
We checked the DNS and reverse zones, all are OK.
even more, from de app store it works, IE, Firefox, ... or other doesn't !!
Even for the sam user on different PC's it does not work, appl store is OK other (IE, ...) not !!!
We tried differend browsers: Firefox, chrome all the same!!
For some users it works other it doesn't, we even create a new user same case, it does not work on the same PC. We cleared cache on the PC, same, ...
=> can we have more logging in one or the other way? And were can we verify? Web interface, putty, ...
without syslog if possible!
Are the problems you're seeing now related to the greyed out DFS map points, or clients connecting to the appliance?
Windows client logging can be gathered as per https://community.ivanti.com/docs/DOC-43532
There is a utility attached to the article which can be used to decode the ETL logs
Appliance logs can be collected as per Collecting Appliance logs