unable to connect to Mitel 5000

[eia]

out of the blue, we are unable to connect to the Mitel 5000 from session manager or the web browser.
The session manager hangs waiting for socket. We are using the default listening port of 44000 and Web listening port of 443. We did verify that we can connect from a PC directly connected to the unit. The PC we are connecting with is onsite, not a remote connection. Anyone have any thoughts? We turned off the firewall on the pc which didn't help.

[dwayneg]

Can you ping the address of PBX?

[eia]

Thanks for the reply, I should have mentioned that. I am able to ping the PBX. What's weird is that I was able to connect to this fine a week or so ago. I installed the session manager software on a local pc in the lan just in case we could not access the PBX from the wan.

We may have to drive up to the site and direct connect to debug further.  We also rebooted the PBX but that did not help.

[acejavelin]

Going through a customer router? Probably changed something, seen it many times... You call and they say "no, we haven't changed anything" and you go there and find a whole new IP address range and new router or something crazy.

I am betting once you get onsite it will work fine.

[eia]

I know what you mean. Actually, our Vendor suggested we install the session manager on PC's in the local LAN.
In this location I have the session manager software on a local PC to eliminate WAN connection issues.
I have having the connection problem from the local lan PC. Let me know if you have any other ideas?
Thanks!

[pexecutone]

I have seen this happen a couple of times. Each time I have completely uninstalled the Session Manager from the PC and reinstalled the program and it would still hang. I ended up installing Session Manager on a different local PC and it worked. My guess is something in the PC is preventing it from going all the way.

[eia]

Thanks for the reply, indeed we were able to connect to it from another PC.
Not sure why the install on the local PC isn't working. We tried a reboot but no luck. We'll try a re-install and see if that works