Plantronics + Polycom. Now together as Poly Logo

QDX 6000 Logon Failure

SOLVED
Highlighted
Occasional Advisor

QDX 6000 Logon Failure

На экране QDX 6000 появляется сообщение: "Сбой входа в систему. Повторите попытку". При нажатии кнопки "Ок" сообщение проподает, затем случайным образом появляется вновь. Может появиться спустя долгое время, а может появиться сразу. Сообщение появляется как во время вызова, так и без него.

Пожалуйста помогите избавиться от ошибки.

 

Google Translate (from russian to english):

A message appears on the screen QDX 6000: "Logon Failure. Please try again". When you click "OK" message closes, then randomly reappears. It may appear after a long time, and can appear immediately.

The message appears during a call, and without it.

Please help to get rid of bugs

Message 1 of 11
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Honored Contributor

Re: QDX 6000 Logon Failure

There are some another places where the login may be required. Check the tabs in the Global Services menu.

WBR,
Mike
--------------------------------------------
“Reports that say that something hasn't happened are always interesting to me, because as we know, there are known knowns; there are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns- the ones we don't know we don't know.”
― Donald Rumsfeld

View solution in original post

Message 4 of 11
10 REPLIES 10
Highlighted
Honored Contributor

Re: QDX 6000 Logon Failure

Having near a zero information we can assume that your system is configured to use a gatekeeper while in fact there is no GK in your environment. Please check: System > Admin Settings > Network > IP > H.323 Settings > Use Gatekeeper.

 

Please note that the screen warnings localizations sometimes may be not authentic. The original (English) text could be more useful.

WBR,
Mike
--------------------------------------------
“Reports that say that something hasn't happened are always interesting to me, because as we know, there are known knowns; there are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns- the ones we don't know we don't know.”
― Donald Rumsfeld
Message 2 of 11
Highlighted
Occasional Advisor

Re: QDX 6000 Logon Failure

Thanks for the tip, but the gatekeeper is not used.
 
When I changed the Location - Language - "American English", the мessagе on screen: "Login Failed. Please try again"
Settings and version in the attachment.
 
Video conferencing is used RMX1505, which is installed in the main office. But message appears and not during a videoconference.
 
Maybe the error appears because of incorrect settings "H. 323 Extension (E. 164)"?
Highlighted
Honored Contributor

Re: QDX 6000 Logon Failure

There are some another places where the login may be required. Check the tabs in the Global Services menu.

WBR,
Mike
--------------------------------------------
“Reports that say that something hasn't happened are always interesting to me, because as we know, there are known knowns; there are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns- the ones we don't know we don't know.”
― Donald Rumsfeld

View solution in original post

Message 4 of 11
Highlighted
Occasional Advisor

Re: QDX 6000 Logon Failure

My Global Services menu:

 

Directory Servers

Polycom GDS: off

LDAP: off

SNMP: on

Management Servers:

1: --- 2: --- 3: --- 4: --- 5: --- 6: --- 7: --- 8: --- 9: --- 10: ---

Account Validation

Require Account Number to Dial: off

Message 5 of 11
Highlighted
Occasional Advisor

Re: QDX 6000 Logon Failure

From system log:

2016-03-09 11:29:05 INFO jvm: pc[0]: UI: asyn: SECURITY: LOGIN_FAILED Type: telnet_23 ID: admin ID: user

 

and:

2016-03-09 11:45:22 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager lastloginsuccessdatetimeadmin.dat = {09-03-201614:45} ID: user
2016-03-09 11:45:22 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedpostlockoutadmin.dat = {0} ID: user
2016-03-09 11:45:22 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedlogincountadmin.dat = {0} ID: user
2016-03-09 11:45:22 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedlogincountremoteadmin.dat = {0} ID: user
2016-03-09 11:45:22 INFO jvm: pc[0]: UI: asyn: SECURITY: Admin failed login attempts reset to 0 ID: user
2016-03-09 11:45:22 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedlogincountuserunknown.dat = {0} ID: user
2016-03-09 11:45:22 INFO jvm: pc[0]: UI: asyn: SECURITY: Unknown user failed login attempts reset to 0 ID: user
2016-03-09 11:45:22 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedlogincount.dat = {0} ID: user
2016-03-09 11:45:22 INFO jvm: pc[0]: UI: fcgi/1: SECURITY: ConfigurationManager web_client.dat = {82.116.51.147} ID: user
2016-03-09 11:45:26 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager lastloginsuccessdatetimeadmin.dat = {09-03-201614:45} ID: user
2016-03-09 11:45:26 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedpostlockoutadmin.dat = {0} ID: user
2016-03-09 11:45:26 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedlogincountadmin.dat = {0} ID: user
2016-03-09 11:45:26 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedlogincountremoteadmin.dat = {0} ID: user
2016-03-09 11:45:26 INFO jvm: pc[0]: UI: asyn: SECURITY: Admin failed login attempts reset to 0 ID: user
2016-03-09 11:45:26 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedlogincountuserunknown.dat = {0} ID: user
2016-03-09 11:45:26 INFO jvm: pc[0]: UI: asyn: SECURITY: Unknown user failed login attempts reset to 0 ID: user
2016-03-09 11:45:26 INFO jvm: pc[0]: UI: asyn: SECURITY: ConfigurationManager failedlogincount.dat = {0} ID: user

Message 6 of 11
Honored Contributor

Re: QDX 6000 Logon Failure

Sounds like someone from Saratov (82.116.51.147) wants to take control of your system. 

 

------------

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '82.116.51.0 - 82.116.51.255'

% Abuse contact for '82.116.51.0 - 82.116.51.255' is 'tech@renet.ru'

inetnum:        82.116.51.0 - 82.116.51.255
netname:        SARATOV-REGION-RENET-NET
descr:          Network for Balakovo
country:        RU
admin-c:        DOK10-RIPE
tech-c:         DOK10-RIPE
status:         ASSIGNED PA
mnt-by:         RENET-MNT
mnt-lower:      RENET-MNT
mnt-routes:     RENET-MNT
created:        2006-05-30T07:05:51Z
last-modified:  2006-05-30T07:05:51Z
source:         RIPE

% Information related to '82.116.51.0/24AS30936'

route:          82.116.51.0/24
descr:          Route for 82.116.51.0/24
origin:         AS30936
mnt-by:         RENET-MNT
created:        2006-05-29T09:21:11Z
last-modified:  2006-05-29T09:21:11Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.85.1 (DB-3)

-----------

WBR,
Mike
--------------------------------------------
“Reports that say that something hasn't happened are always interesting to me, because as we know, there are known knowns; there are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns- the ones we don't know we don't know.”
― Donald Rumsfeld
Message 7 of 11
Highlighted
Occasional Advisor

Re: QDX 6000 Logon Failure

On Thursday, I've disabled telnet on QDX6000.  During the video-conference (1.5 hours) no errors appear. On Wednesday I will check in during another video conference (2 hours).

 

(2016-03-09 11:29:05 INFO jvm: pc[0]: UI: asyn: SECURITY: LOGIN_FAILED Type: telnet_23 ID: admin ID: user)

Message 8 of 11
Highlighted
Occasional Advisor

Re: QDX 6000 Logon Failure

Messages no longer appear. Thanks for the help!

Message 9 of 11
Highlighted
Occasional Visitor

Re: QDX 6000 Logon Failure

pls help me our polycom also has that kind of problem and i dont know how to disable telnet pls help me

Message 10 of 11