Problem with network port !

[Pabxer]

Hi !

To start using network port, we changed IP address of network port with IONPC and then restarted NIU2 board with RFBOI.
Checking with IONPP showed that the change was accepted ( although IONPP showed it even before restarting ... but ok, who would know ... )

The problem is that we cannot establish connection over this network port using MDDT.
When we ping IP address of a network port , we have no reply.
If you have any idea what to check on this problem, please write !

Thanks

 

[cuneyt2020]

If no physical connection changed, then probably , subnet mask ,or gateway or IP adress is wrong or misconfigured on PBX side.. did you ask the network specialists that gateway or subnet mask is changed for the new IP adress?

 

[Pabxer]

We didn't use this network port before. It is the fourth port on NIU2 that is by default set as network port. It had some default IP address which we changed. We asked system administrator to give us IP address for this and also mask and gate parameters.It was these data that admin gave us that we set on network port ... so, that would mean that values of these parameters are ok ...

???????

 

[DUFQI]

Have you done a restart of the board (niu) after changing network parameters with ionpc?

 

[cuneyt2020]

Do you give the printout for IONCP?

 

[rfpui]

Hi Pabxer

How do you connect to MD?
Direct PC to MD or over LAN?
And cable is factory new?


----------------------------------
If anything can go wrong, it will.
(Murphy's Law)

 

[ETBOY]

Hi ,

check Gateway ip address.


Regards

 

[whosrdaddy]

Pabxer, did you program a network MML port on that NIU??

give us IODDP printout...

--------------------------------------
What You See Is What You Get

 

[Pabxer]

2DUFQI : Yes, we did a restart of a NIU2 board with RFBOI right after changing the parameters.

2cunneyt2020 : We didn't program any network connection, so the printout of IONCP is empty. We want to use this network port mostly for taking CIL files on HDU (we have programmed monthly CIL files) by using MDDT.To do this, is it also necessary to program network connection with IONCI ?

But, it's weird we can't ping MD at all ...

2rfpui : At the moment we connect to MD by using modem. PC is in the LAN and we dial a local extention number on which we connected modem... But, this network port which we are trying to start using,is connected on a switch in a LAN, as other PCs. Yes, the cable is factory new and the lamp on a switch turns on when we connect a port with this cable ...

2whosrdaddy : Here is a IODDP printout concerning this port :

NODE : SYSN
IODEV/SUBFS : NET
BPOS/EQU : 001-0-60-4
I/O-BUS : -
TYPE/USAGE : NETWORK/OUT
STATUS : IN SERVICE
AUTH : (empty)

This network port was already initiated as we received PABX. I think this fourth port was by default set as network port and it had default IP address, which we changed (unsuccessully it seems ... )

 

[whosrdaddy]

CNBIP:BPOS=1-0-60; ??

--------------------------------------
What You See Is What You Get

 

[cfrei]

Use niux and try ping NIU adress. If OK, NIU is alive and problem is in the LAN connection.

 

[Pabxer]

2whosrdaddy : Here is a a printout of CNBIP :

BPOS BOARD/BRDID PRODUCT NUMBER REVISION STATUS ADD
/IND
001-0-60 NIU ROF 137 5396/2 R2
CAA 1580021 R5A EXE
CAA 1580001 R13A OLD

2cfrei : We tried and we got the message :
"BAD SOCKET CALL"

I could't find in Alex what this message means ?!

????

 

[whosrdaddy]

to be sure that the NIU2 ethernet port works, try connecting with a cross cable. recommended firmware is R6A (R7A will be released shortly, R8 is in test phase) although R5A should work too...

we are seeing problems with the NIU when the PC is in a different subnet as the one from the NIU (will be solved in R8) so make sure they are in the same subnet

--------------------------------------
What You See Is What You Get