-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Poly Video Conferencing
- Meeting Room Solutions
- Re: QDX 6000 Logon Failure
Create an account on the HP Community to personalize your profile and ask a question
03-03-2016 04:51 AM
На экране 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
Solved! Go to Solution.
Accepted Solutions
03-04-2016 12:13 AM
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.
03-04-2016 03:19 AM
03-09-2016 01:47 AM
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
03-09-2016 05:30 AM
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
03-09-2016 05:52 AM
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)
-----------
03-13-2016 11:20 PM
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)
Didn't find what you were looking for? Ask the community