Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PCADMIN connection problem

Status
Not open for further replies.

jongemcf

Technical User
Feb 25, 2010
16
GB
Hi,

I am having an ongoing problem with connecting to our LDK100 (UK90P-C.9Bc, 1 rack). I have for some time been able to connect using LAN from my PC using LDK PCADMIN.

The IP address is set outside of our normal DHCP scope but I receive the following error:
[MESSAGE] MAIN WINDOW, SYSTEM CONNECT FAIL
Additionally in the status window, it says. "CAN'T OPEN CONNECTION, CHECK CONNECTION TYPE"

I have of course checked connection. I have previously had it working when programming or adjusting aspects of the system. However I have discovered that i can work around this if I reset (Power cycle) the system and then connect. IT then works! After some indeterminate time it then stops working.

There must be some fault since when I ping it (at say 192.168.0.80) the ping returns but from the local (DHCP assigned) address of my PC. (Note, the same happens if I manually set and out of scope IP address on my PC!)

Can you offer any advice?

Thanks
Jon.
 
In PGM 108 you set the IP address of your ipLDK system. Try to check by keyset admin : [Trans/pgm]+*+#+code+[Hold/save]. Enter 108 in the PGM list and go through the entered values. Each flex key (button) represent the IP address, the subnet mask and the default gateway. The default gateway must be programmed.

///doktor
 
Thanks doctor:

I should have been clearer:
jongemcf said:
I have previously had it working when programming or adjusting aspects of the system.

The IP, subnet mask and gateway are all set correctly as I should have made clear in my post. As I mentioned, I can get it working by power cycling the system but that is not a satisfactory work around.

Any further thoughts?

Jon
 
Nice to know. Did you ground the system correctly? and add ferrite cores to all in/outgoing cables to the ipLDK?
What happened since it worked allright? Did you upgrade from an earlier version? or ?

///doktor
 
Also: Check that the LANU sits tight on the MPB.
What type of MPB and LANU do you use?
Or use a cross-over cable to work-around as cpozdena writes.

///doktor
 
You don't have an IP address confilct do you?, unplug the IPECS from the LAN and ping the IP address and see if you get a reply. 2 things on the same IP address casue odd things to occur.
 
I have had this before , what i did was default kit then downgrade to 3.8 then test your connection via lan it hopefully will connect each time ,then back up to the latest version. Try connecting again in default state on 3.9 you will find it works(hopefully)

Obviously take a back up prior to downgrade , then when you upload the config if you cant connect again im afraid you have corruption in the database(dont ask where or how i dont have a clue), if this is the case its button bashing time.

keep us posted


APSS (SME)
ACSS (SME)
 
Or you can got PGM450 and initialize ONLY PGM 108, which is the IP settings.
Then re-enter by keyset admin the data for IP/LAN.

If you see problems like this it is often because the database was not initialized from the beginning - i.e. before the installation. Do not do this on a live installation!!!
The correct way (or if you have periodical faults on e.g. handsets, DECT or IP) is from the very beginning to initialize all database fields in PGM 450+452. This will delete the whole database.
From here all data is to manually tampered in. Re-using the database will NOT help since the database (often) was not initialized correctly.

///doktor
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top