Quantcast
Channel: THWACK: All Content - Network Performance Monitor
Viewing all articles
Browse latest Browse all 21870

Console logon failing after timeout, following upgrade NPM 11.0.1

$
0
0

After upgrading to NPM 11.0.1 and moving to a new Server 2012, we are experiencing login issues from the Orion console.

 

Scenario:  When initially opening the Orion website (while already logged on to a PC using a domain\account), the website authentication / credentials pass-through and the websites opens as expected.  After logging out and/or timing out, when attempting to log in using the same credential, we receive "Login failure.  User name and/or password incorrect."

 

Workaround:  Close all IE sessions and re-open the website so the pass-through reoccurs OR login with a local Orion account. [When logging in with the local Orion account, the audit trail shows this user logged in, but the user id shown in the upper right of the page is the domain\account.  When you log out, the audit trail shows the domain\account as being the one logging out.]

 

The security log on the server has an error.  Event id 4625, Source: Microsoft-Windows-Security-Auditing.  "An account failed to log on."  Account that failed is the domain\account, failure reason:  The user has not been granted the requested logon type at this machine.  [This account is not allowed to log onto the server and needs to remain that way.]  Logon type:  2 [2=interactive].  Process Information:  Caller Process Name:     C:\Windows\SysWOW64\inetsrv\w3wp.exe; Loon Process:  Advapi.


After working with a SolarWinds tech last week, he mentioned that the logon screen is a known bug.  Please notify me of the SolarWinds internal reference number and when a patch is available.


Thank you!

 

Using IE 11 on the PC, IE 10 on the server.

Orion Platform 2014.2.1, SAM 6.1.1, QoE 1.0, IPAM 4.2, NCM 7.3.2, NPM 11.0.1, NTA 4.0.3, IVIM 1.10.0


Viewing all articles
Browse latest Browse all 21870

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>