KX-NCP Maintenance Console cannot connect due to lock

[Coenradie]

PROBLEM DESCRIPTION:
We have a Panasonic KX-NCP1000 phone system. We use the Panasonic PBX Unified Maintenance Console (MC) via LAN to programm it in interactive mode. Recently the user session which was connected to the KX-NCP1000 was broken due to a problem with the client computer. Now we are not able to reconnect to the KX-NCP system anymore. It seems there is some kind of lock which we cannot reset.

SYMPTOM ERROR:
E030103 Invalid Password or Model Type Error

WHAT DID WE TRY:
1. We have double checked the LAN connection settings (which was documented), so PBX model, IP, port and password are 100% correct. We even tried to connect via serial port, but no connection was possible.
2. We have tried to reset the KX-NCP (normal reset via button, power off, etc, NO initial reset to prevent loss of programm data). Result: MC connection still not working
3. We have tried to backup the system programm data from the SD card, change the DBSYS file offline in Maintenance Console batch mode and restart the KX-NCP again with the changed data. Result: Restart of KX-NCP was successfull with the changed data, but MC connection still not working

QUESTION:
How to reset the lock on the Maintenance console connection at the KX-NCP?

Help would be appreciated.

Best regards,
System installer @ Coenradie

 

[bigglesnz11]

Can you ping the lan interface on the NCP?
Have you selected the correct device type on MC?

 

[Coenradie]

Thanks for trying to help.
Yes I can ping the LAN interface on the NCP.
Yes I have selected the correct device type on MC.
We believe a broken connection between the MC and NCP is causing all the trouble. What can we do?

 

[Rhiuz]

if pbx turned on, whether the extension and co can be used?

 

[Coenradie]

> if pbx turned on, whether the extension and co can be used?
@Rhiuz: Not sure what your you mean with extension and co.
But the KX-NCP phone system is running okay, even after restart as described in my WHAT DID WE TRY section.

 

[Rhiuz]

What version of MPR NCP1000 ?
What version of pbx Unified Maintenance Console ?

 

[Coenradie]

Version info: KX-NCP1000 (according to DBSYS file Version 003-000/Region 006-015 loaded @ MC in batch mode)
PBX Unified Maintenance Console V6.2.1.1

 

[Rhiuz]

Open DBSYS -> maintenance -> main -> password

can you see system password - PC programming

 

[Coenradie]

In MC you cannot see the PC programming system password from DBSYS when you are in batch mode. We can see only the PT Programming passwords.
Luckily we know the PC programming system password, since we documented it.

 

[Rhiuz]

cau u send backup NC1000 DBSYS to me

 

[Coenradie]

I prefer not to send the file just to someone or attach in this forum, it has all our programming data in it. Maybe you can point me to which part I should look?

 

[bigglesnz11]

Just tried one of our systems and the only way I can get the E030103 error is by having the wrong model type of by deliberately entering the wrong password.
wrong IP address or port number gives an EA04301 error (cannot open LAN port)
What happens if you try and access system thru Mtce Port?

 

[Coenradie]

What do you exactly mean with Mtce Port? Do you mean the MNT Port on the IPCMPR Card? We didn't try that one yet. Could be an option!
We tried to connect in interactive mode through the serial RS-232C interface of the PBX. Unfortunately we got an EA03201 error via this approach.

 

[Turbonet]

Seems like you are focusing all of your attention on the PBX and assuming that the problem must originate there. Have you uninstalled the MC console software, deleted any folders or files remaining after the uninstallation, and then done a clean re-install? After all, you said the fault occurred after a problem with the client COMPUTER. Nobody has a laptop handy with MC software that you can try?

 

[Coenradie]

Thanks for your reply. The problem with the client computer was that the user who had the MC open was logged out remotely by the administrator. We have tried other computers, unfortunately without success. We will try once more with laptop on MNT port, but we need to plan this maintenance.