Network Error- Failed to communicate with IP Office

[FreightTrain]

I have a customer who has 100 plus stations that all use hot desk (why I don't know), but when someone needs a password change he has to log in and he is getting the
[Network Error- Failed to communicate with IP Office]. Now I've upgraded the system to the latest release, I've change VMPRO machines, I've even use my lap top to log in and I even used the WAN port and I get this message. Now it only clears once the system has been rebooted but you know how big of an issue it is to reboot when all users are hot desk users.
In any case I thought that there was an IP address conflict and maybe it locked the cabinet up on that address so I had the IT guy there who is also my POC make sure that there was no more conflict and here is his reply:

"We’re still getting the network error issue. It is not an IP thing as we changed subnets and still having the same issue. It doesn’t make sense that you can ping the device, connect via status, it sees it in manager, but once you try to login it doesn’t work. Many forums talk about this issue without any real results. We need this resolved asap as I cannot modify or add any entries to our system and its holding me back. We have users that are not able to access their voice mails"

Does any one have any ideas as to what is going on. My only option now is to default the dang thing and reprogram it, but that as you know will take time and money that the customer will not pay, and of course they will want it after hours.



"When all else fails call for backup

 

[tlpeter]

Did you try rebooting the vmpro service?
Also try to chemurg change the preferences of manager.
There is an option called secure communication.
Don't turn it off but set it to none.

BAZINGA!

I'm not insane, my mother had me tested!

 

[TomMills]

+1 for vm pro service restart. Worked for me last week.

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[FreightTrain]

I will try those suggestions, but wanted to also let you know that I've tried connecting with my laptop through the WAN port and got the same problem.

"When all else fails call for backup

 

[amriddle01]

It's not the port that's the issue, it's like the system has blinkers on and it's totally focused on already connected devices/software, restarting the VM Pro service makes it look around and go ...."oh yeah"

 

[qtelcom]

I've had this issue rarely, (seemed to be the GA release of 9.0) but I've always just try to open the config a 2nd or 3rd time again and then it magically works. I haven't had the issue where you have to reboot.

 

[FreightTrain]

OK, I will give that shot, If that works I will do 6 flips.

"When all else fails call for backup

 

[FreightTrain]

OK, so update: I tried the restart idea and I get the same problem. Any other ideas, I really hate to have to default the entire system and program for scratch and even doing that there is no grantee that will fix it.

"When all else fails call for backup

 

[Telecomboy]

Silly question, but you say you upgraded the IPO. Did you give the client the new software or are they still trying to connect with a lower version of Manager?

 

[tlpeter]

Like i said before:

Also try to change the preferences of manager.
There is an option called secure communication.
Don't turn it off but set it to none.

BAZINGA!

I'm not insane, my mother had me tested!

 

[FreightTrain]

Yes I have upgraded all software to match at 9.0.5. Also tlpeter I did that as well and getting same result. Customer is wanting cabinet replaced but this is going to cost me a lot.

"When all else fails call for backup

 

[tlpeter]

To be honest it sounds to a network issue to me.
Can you post the IP address of the IPO and the PC running Manager?
If those are on a different subnet i need the IP route too.

BAZINGA!

I'm not insane, my mother had me tested!

 

[FreightTrain]

The IP address and the VMPRO are on the same network and have the same subnet. I thought the same thing that's why I took them both out of the network and directly connected to each other and still had the same problem. Even with the system out of the network I get not response on CMD when pinging the IPO.

"When all else fails call for backup

 

[Gunnaro]

Try defaulting the security settings with DTE, because this sounds like the same crap you get from downgrading R9.x to R8.1.
(even though you haven't done any downgrade, it might be the solution.)

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[tlpeter]

How is the secure communications set?

BAZINGA!

I'm not insane, my mother had me tested!

 

[FreightTrain]

Its set to none.

"When all else fails call for backup

 

[tlpeter]

Which version IPO and VMPro?

BAZINGA!

I'm not insane, my mother had me tested!

 

[snowman50]

Look again to your security settings.

I had a colleague set the configuration certificates to high and this give him the same error.
Once he changed it back he was then able to acces the system again.

 

[Westi]

Had this issue on Tuesday and it was the network port set to not allow a statically set IP address so it blocked traffic on TCP but the UDP discovery was working.
Reading again your post you have the same issue on the LAN2 port, did you set you IP address to the correct range when you tried that because again UDP discovery works even if you are not on the same network but then no communication happens.

I also second snowman50's suggestion to try and have a look at the security settings (if you can get in)

Joe W.

FHandw, ACSS (SME), expired ACIS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter