Hi, tx that's great

Hello guys,

one question:

Is the converter supported with destination Hyper-v 2019 Server?

regards

Ralf

Hi, 135 was open. I checked the connection with the security guys..... 902 was missing. Now it works

yep ... i will check 135 and sorry i mean all ports from 49152 to 65535 are open

Hi Boris,

it is ESX Version 5.5 commercial .
At the internal network it works without problems.
Now i try it from the DMZ (ESX) to the internal (Hyper-v).
I open the ports which you told me before.
TCP ports 443 and 80. For Hyper-V, it uses WMI to connect to the hosts.
WMI ports 49152 und 65535.

HI, on the FW the ports are open now but i get an error. I can select the VM on ESX host from my Hyper-v host. But if the convertion start the VM on hyper-v was created but the disk was not created. Any idea? regards Ralf The log file name: 'logs\V2V_Log-20191028-110652.log' (PID 13756) Delete log f...

tx

Hi all,

i have to convert a VM from the DMZ to the internal network.

The security guys asks me which ports they have to open?

Is anywhere a list of all ports which the converter needs?

regards

Ralf

Hi Oleg,

got no mail ... i send you a private message with my email adresse

Hi Oleg,

i opened i support case as you requested.

But i got no auto rely mail with the case number.. i hope it was working.

btw

I guess it is the same as..

https://forums.starwindsoftware.com/vie ... 773#p29214

Hi, there are some topics with this error with the answer ... I have passed information to our R&D team .... some news? i got this error now also. Migration from ESX to Hyper-v 2016 works but to Hyper-v 2012 not. Some solution for this problem avaiable? regards Ralf The log file name: 'C:\Progra...