Hi,
Did someone face issues like below:
I am able to login to app server from other machines with DNS name but not from application server. If I use localhost.suite I can login to the server.
Thanks & Regards,
FL
Feb 19, 2020 06:04 AM
Hi Fawad,
I have seen such behaviour at several customer systems repeatedly, but I cannot tell what's the reason. What do you get if you run nslookup from the server? Do you use SSL?
Best regards,
Markward
Feb 19, 2020 09:34 AM
Feb 19, 2020 11:53 AM
@fawad_laiq - What would be the requirement to log into FlexNet Manager directly from the Application Server? As long as you are able to do so using the "localhost" as the URL, is that causing any problems?
Feb 19, 2020 12:05 PM
Feb 19, 2020 01:03 PM
Hi @fawad_laiq ,
Try browsing the Web application server using the IP address and check.
Not sure if there is some DNS issue if the Beacon is unable to connect App server and see if the NSLookup using fqdn and IP address is getting resolved and telnet is working using the required ports. Also make sure the TLS settings were as it should.
Regards,
Vinay.
Feb 20, 2020 03:17 AM
Please try adding the IP's of app server and beacon respectively to their host files in c\windows, and check.
I know its weird but it worked for few connectivity issues (not the same exact issue what you facing).
Also, please be sure TLS settings are properly configured on beacon and app server.
Feb 20, 2020 06:33 AM
Hi Fawad,
Which Windows user account do you use for logging into your FNMS application server (into the Windows OS)?
As the default setting, FNMS configures "Integrated Windows Authentication" for the /Suite folder in IIS. With this setting, the system will try using the same user that is logged into Windows for logging into FNMS.
You can reconfigure the /Suite IIS folder in IIS Configuration Manager to use "Basic Authentication" instead of "Integrated Windows Authentication". With "Basic Authentication", FNMS will prompt you for a user and password.
You should document these manual configuration changes. In case you re-run the FNMS PowerShell configuration scripts, these scripts will revert settings to "Integrated Windows Authentication" though.
Feb 19, 2020 12:54 PM - edited Feb 19, 2020 12:55 PM
Feb 19, 2020 01:00 PM
Feb 20, 2020 01:23 AM
Hello All,
I got the same problem as fawad_laiq. But I cannot use https://localhost/Suite to login because I have to use a wildcard cert of different domain (a.example1) from the domain my server in (b.example2). It returns server error 401 - unauthorized: access is denied due to invalid credentials. But I can log in normally by same credentials from other servers with https://application.a.example1/Suite.
Is there any way to fix this problem? Waiting for your answers.
Dec 05, 2021 03:28 AM - edited Dec 05, 2021 03:31 AM