How to repair IP403 IP settings

[NickRyan]

We have an IP403 system, however for whatever reason the IP settings appear to have been corrupted and we can no longer communicate with the system using IP. The system has been restarted in case it's a transitory fault but this hasn't fixed it's problems.

(Can't say what version of the SW it's running, as we can't connect...)

Is there a way to connect to the system and fix the IP settings? We can make up a suitable DTE cable if required.

 

[jamie77]

You could try using Ethereal to see what IP address it is throwing out.

If you connect a serial cable to the DTE and reboot the unit it it will output the IP address in HEX with all the rest of the rubbish it thows out.

If this doesn't work you will have to default the system by the DTE port.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[NickRyan]

We can see the IP address of the system (various scanning tools find it), however we can't communicate with it.

I had a custom serial cable made up (thanks to Avaya for needing a custom connector) and we managed to access the Avaya box itself using the legacy serial port mode. Turns out it had corrupted some of it's settings, one of which was the routing table, resulting in it being unable to route outgoing packets using IP.

 

[ProviderReborn]

Do you have a working .cfg config back up. If yes it may be worth running through removing the config and re-entering. You can do this Via the DTE port and using AT commands to wipe the unit.

 

[Gibsonic]

check out the FAQ section of this forum for more information about the DTE commands.

Is the IP address the default 192.168.42.1 ? Do you have your Manager PC plugged directly into the front of the 403?

 

[NickRyan]

Using a serial cable I just connected directly to the IP403 unit. The manager software that we still have here (v3.3), has a "legacy serial connection" option (File > Preferences > Edit) which I just set to the appropriate serial port.

Once connected I managed to fix the corrupted routing record which was routing IP packets towards a non-existent router, causing the loss of 2-way communication (the IP403 should have been able to receive TCP data, but not respond).

All of the other configuration seems to be fine.