Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 15 replies
  • Answers 2 answers
  • Subscribers 29 subscribers
  • Views 11543 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

STAS doesn't working anymore after 2nd DC demote

VikenNajarian

Hello,

I have a problem on a XG210 (V17.1) of my custommer.

The STAS worked well for weeks but stopped working this week end after the old DC has been demoted.


The STAS was collecting the informations of the two DCs, it was working, and the custommer decided to demote the old DC (old server going to be thrown away), the STAS sofware suite was installed on the two DCs and has been uninstalled on the old DC after being demoted. We then deleted the old DC's IP from the collector list in the 2nd DC stas settings, and deleted the old DC's IP in the STAS settings on the XG aswell.

 

Then the problems happened. All the live users are now not being viewed online anymore in the XG's reports and logs are reporting problems with credentials for all users as shown in this screenshot: 

But in the STAS suite settings we can see the live users showing well: 

 

I thought that it was a problem with users who have been created by the old DC into the XG that they don't work anymore because the DC changed (even if the two DCs cohabited for weeks), so I created a new user in the new DC, and logged in onto a server, but the issue is still the same.

For information: the SSL VPN is configured with AD Auth and it works well, the issue is only in the STAS.

I have many custommers who have multiple DC's with XG and STAS working well, and now I'm afdraid if I will have to demote another DC and if it will break STAS...

 

Thank you for your help.

 

Viken NAJARIAN



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to sachingurung

    I did not try that yet but I will try it and will tell you the result.

     

    It's really weird that there are only the users connected through STAS that the XG refuses to authenticate, but those same users with the same users account under the XG (through AD) can successfully connect with SSL VPN...