VM Pro fails to connect to the Control Unit PC IP Address: x.x.x.x

[GoApex]

Been researching this all weekend. New install of IPO 8.1 with VMPro on Win2k8R2 32-Bit install. Installed via VNC to server NOT RDP. Disabled Firewall, even created exemption rules just to make sure. IP address is set in IPO under Voicemail tab. When accessing VM Client is shows the IP address of the switch correctly but when accessing Users or Administrators is says downloading and comes back with nothing. System Status errors are growing with the above error. Took it to next step and uninstalled, reinstalled with same results. Stopped VMPro Service and reinstalled on a WinXP workstation also located on site via VNC with the same results. IPO seems to be performing normal (system is not live yet in production but softphone and T Series sets all coming up fine). Also checked managed switch remotely and nothing is programmed like port mirroring or vlan. Rebooted switch remotely also just to clear it.

T-6 hours to kickoff, please help !!

 

[intrigrant]

try this:
On the win2008 server stop the vmpro service, stop the dns service, start vmpro service and see if it works, then start dns service

A simple mind delivers great solutions

 

[GoApex]

Stopped the DNS Client and Disabled the service after stopping VMPro service. Restarted VMPro service and found same results. Ran Netstat with the following results:

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:4999 Win2k8:53630 ESTABLISHED
TCP 127.0.0.1:4999 Win2k8:53631 ESTABLISHED
TCP 127.0.0.1:4999 Win2k8:53632 ESTABLISHED
TCP 127.0.0.1:42001 Win2k8:53770 ESTABLISHED
TCP 127.0.0.1:53630 Win2k8:4999 ESTABLISHED
TCP 127.0.0.1:53631 Win2k8:4999 ESTABLISHED
TCP 127.0.0.1:53632 Win2k8:4999 ESTABLISHED
TCP 127.0.0.1:53735 Win2k8:42001 TIME_WAIT
TCP 127.0.0.1:53750 Win2k8:42001 TIME_WAIT
TCP 127.0.0.1:53759 Win2k8:42001 TIME_WAIT
TCP 127.0.0.1:53770 Win2k8:42001 ESTABLISHED
TCP 192.168.128.7:53719 a23-64-160-60:https ESTABLISHED
TCP 192.168.128.7:53733 192.168.128.5:50804 TIME_WAIT
TCP 192.168.128.7:53739 Win2k8:50791 TIME_WAIT
TCP 192.168.128.7:53740 Win2k8:50791 TIME_WAIT
TCP 192.168.128.7:53744 Win2k8:50791 TIME_WAIT
TCP 192.168.128.7:53747 Win2k8:50791 TIME_WAIT
TCP 192.168.128.7:53748 Win2k8:50791 TIME_WAIT

The IP address of the VMPro is 192.168.128.7

 

[intrigrant]

I have had the same issue once but it was the DNS server and not the client.
Does the service start with a user account or a service account?
Use debugview or open c:\debugout.txt and see what vmpro think about it.

A simple mind delivers great solutions

 

[GoApex]

Reviewed the log file and noticed TFTP failing authenication. Checked Preferences in the VMPRO and Voicemail Password field was blank (default=blank). In the IPO I checked the Security Settings, System and tried to verify the VMPro password by attempting to change it however it wouldn't let me continue by leaving the Current Password field blank. Not knowing what the password is/was because it's a new install I cleared the settings using the Option in Manager. Restated the VMPro service, checked the VMPro client and now all extensions appear!! The only thing I didn't see was the Administrator user and Password but system is now functioning, tested extension with message and saw it register with the system!

Thanks for your help for getting me in the right direction.

Dale

 

[IPGuru]

I had this one just last week
Avaya have changed something as VM Pro did not previously require a password

the ddefault VM Password in the Security settings of the IPO is password.



A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear