Unable to login to Siemens Hipath 3550 via IP

[Christowfurs]

Trying to login to the above phone system via IP using HP3000 Manager but having no joy trying to transfer config from system>PC

For some strange reason I am able to 'log in' to the system using a variety of random credentials for e.g. can log in with u/n 31994 p/w 31994 or just p/w 31994 with no u/n and vice versa. I can log in using u/n admin with no p/w and so on...

Anyway I am logging into the manager software using 31994 for both u/n and p/w and then hit the transfer icon and try to download config to make changes and get this error - 'attempt to connect timed out without'

I am new here in my job and the only info I have is that the username and password is 31994 but I then found another note to say the password is 1812... I naturally have tried a combination of all numbers with no joy, doesn't help though when the software will accept any old combination as described earlier.

The IP address I have been given for the HP3550 should still be the same, no reason why it would of changed but again don't have any real way of testing this as I'm not even sure if the LAN interface has been configured to respond to PING or ECHO.

Any ideas on this would be greatly appreciated!

 

[obtsystems]

you should be able to ping the ip address. no response is because it cannot talk to the system.
is your pc on the same subnet as the system. if you check the cable to the system is the network light on the switch

 

[Christowfurs]

Managed to get it working now simply by restarting the PBX itself...

However if I leave the network cable (from system NIC to LAN) plugged in for extensive periods of time the same issue happens again - any ideas?

I can't see why this would happen but the only fix so far is a full system reboot which isn't ideal as I have to do this out of hours.

 

[obtsystems]

yes I have one doing this as well. I changed the lim card and it still does it.

 

[Christowfurs]

It's rather annoying! It's kind of reassuring though that you've come across another system with the same issue...

Our system is due to be replaced 2015 year end anyway so I don't want to chuck any money or time at it trying to repair it unless it's a quick fix.