Voice mail pro not connecting running on a virtual windows server 2016

[Bailly34]

Hello all,

I'm moving a voice mail pro release 11 from an old Windows server 2008 to a virtual windows server 2016. When I switch the IP address on the IPO voice mail tab from one server to the other, everything seems to work on the vmpro client. The VMPRO client shows connected to the correct IP address of IPO. When I check System status it shows "NONE". Any thoughts? Thank you in advance.

Oscar
Business Linxs
Miami, Florida

 

[TouchToneTommy]

Set the VM Pro password in IPO Security Settings, and put it in VM Pro Client under Administration ? Preferences > General

 

[Bailly34]

Yes I have VM password in both spots.

Oscar
Business Linxs
Miami, Florida

 

[SamIPOfficeSupport]

Are you showing any licensing alarms in system status?

 

[Bailly34]

No alarms.

Oscar
Business Linxs
Miami, Florida

 

[SamIPOfficeSupport]

I'm sure you've done this, but please make sure to restart voicemail pro service a few times, reboot the machine, and confirm that the service is running with administration privileges.

Then.. What about a cmd tracert from the network to the voicemail service? And also, from the voicemail machine to the IP Office. It may be a good test to connect the IP Office directly to the interface, if possible. Might be a good idea to do an IP scan to see if there may be duplicate IPs. You can connect monitor, and turn on TCP port 8 to watch a ping go from the IP Office to the voicemail server... (do the ping from system status). This will tell you what is responding at that location.. you can see the mac address in the ping response of the monitor log.. but just doing advanced IP scanner may be faster

 

[teletechman]

check firewall and if you are looking immediately at SSA for it to show you need to wait about 3-5 minutes for SSA to update the status.
Mike

 

[IPGuru]

from an old Windows server 2008 to a virtual windows server 2016

i moving to a virtual server why not simply use application server
that way to know all applications are correctly installed & configured without any firewall/ Antivirus issues. any issues will therefore be with the network configuration of the VM hypervisor (actually that is also probably your problem with the windows server)


Do things on the cheap & it will cost you dear

 

[intrigrant]

Make sure the DNS server service is turned off, firewall turned off and no real-time virus detection turned on, enable all services as TFTP read/write etc until VMPro is checked
Default IP Office security and reprogram it
Run the VMPro server initially with the local service account to test connection
inspect the file debug.txt on the server in the root of drive c:, better is to use debugview and disable all except VMPro in the filtes and set the filter to high

 

[Bailly34]

Here is what I see different on the debugger.

16/02 16:39:32.917 vmprov5s (09,5) 894, 678: TFTPWebSocket::CreateSocket: Receive buffer size is 0x10000 bytes (64K)
16/02 16:39:42.939 vmprov5s (11,5) 894, 678: TFTPWebSocket Error - 10060 [0x274c] (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) calling connect from TFTPWebSocket::ConnectSocket
16/02 16:39:42.939 vmprov5s (11,5) 894, 678: TFTPWebSocket - Failed to connect to 172.19.105.35:443
16/02 16:39:43.194 vmprov5s (11,5) 894, 678: Failed to upgrade to web socket
16/02 16:39:43.200 vmprov5s (11,5) 894, 678: TFTPMergeThread::~TFTPMergeThread
16/02 16:39:43.231 vmprov5s (09,2) 894, 678: SOCKSTask::~SOCKSTask: Failed to close the socket, error=2736 (An operation was attempted on something that is not a socket.)

Any thoughts.

Oscar
Business Linxs
Miami, Florida

 

[teletechman]

did you disable the firewall as suggested? reset passwords on VM service?
Mike

 

[Bailly34]

Mike, yes I tried both. One thing I noticed is when I change the VM password on the IPO while the IP office shows connected to VMPRO on the virtual 2016 server, SSA does not show a service alarm stating voice mail password incorrect. When I switch back to the old 2008 server, after changing the VM password on the IPO I get the an alarm on SSA stating voice mail password incorrect. After changing the password on the VMPRO on the 2008 sever I get the Voicemail Type: Voicemail Pro. On the 2016 server still "None" even though it seems to be connected. any thoughts?

Oscar
Business Linxs
Miami, Florida

 

[Bucky101]

Proxy off?
Have you reset ipo security settings?
In settings on vmpro, are the directories set to program files x86?

 

[Okkie26]

Or try to run the firewall batch file on the W2016 server.