I requested this already. it takes a bit until that is implemented...
I'll let you know then.
Okay, the Port is not the problem.
The first line looks as if the target server reject the connection. Half a minute later no answer seems to pitch on the firewall.
Aug 17 09:31:09 10.25.15.22 framf02: NetScreen device_id=framf02 [Root]system-notification-00257(traffic): start_time="2015-08-17 09:31:05" duration=5 policy_id=1001 service=tcp/port:902 proto=6 src zone=bt-mgmt dst zone=bt-mgmt action=Permit sent=16576 rcvd=0 src=10.15.3.201 dst=10.15.5.219 src_port=50961 dst_port=902 session_id=171331 reason=Close - TCP RST
Aug 17 09:31:39 10.25.15.22 framf02: NetScreen device_id=framf02 [Root]system-notification-00257(traffic): start_time="2015-08-17 09:31:20" duration=19 policy_id=1001 service=tcp/port:902 proto=6 src zone=bt-mgmt dst zone=bt-mgmt action=Permit sent=279933 rcvd=0 src=10.15.3.201 dst=10.15.5.219 src_port=50980 dst_port=902 port=902 session_id=251722 reason=Close - AGE OUT
So other question. you did Installed the Converter as a Server and connecting to the Powered on Machine ? or you're installing the Converter directly to the Hyper-V VM as a Client?
as if you're not using the Converter inside the Hyper-V directly then you need additional Ports open from the Converter Server to the Hyper-V VM
Converter Standalone server to powered on source machine TCP - 445, 139, 9089 UDP - 137, 138 (Windows).
Most Problems in the Past i had with the Converter Server Config. if was most worst because of Firewalls etc,.... i installed Client on the VM and connected to the vCenter/Esxi (but i had not much vm's to migrate last time).
and you need to change the host file on the Windows VM
Please upload worker's log.
Seems you want to do conversion with powered-off machine (V2V), is this correct?
In this case if a virtual disk is expandable i.e. its total capacity is times bigger that used capacity - this could be a problem.
To avoid such situation try to convert VM as powered on machine, just ensure guest os to see ESX at port 902.
the used virtual disk is a static / Thick Provision disk with 50gb. Its a test vm. EDIT: The destination disk has 350GB free and i tried a second one with 1800gb free.
Yes im trying to convert a shutted down windows server 2008r2 vm to the ESXi (v2v).
I got the root credentials for the esx server, but the converter says: "The access to the host resource settings is restricted to the server 'xxx' that is managing the host. Use the management server as a destination.
Madmax01 wrote something about to change the hosts file. where can i find informations about this?
- 10.15.3.201 to 18.104.22.168 have to go over the Gateway 10.15.3.206
- reverse way is 22.214.171.124
So here you have the Infos .
To be honest - i didn't checked the 6.0 Converter. But with earlier versions i had the Problem that also with IP communication he blamed somewhere that Names not reachable. So i configued the vcenter + esxi inside the local hosts file of the Source Machine
For the Error above > just please try connecting to vCenter. as direct Esxi connect is avoided. need to "Disassociate host from vCenter Server" before able doing direct connect.
The probable problem could be with source disk, not with destination one... If disk is 50GB but it's not extended to max capacity but occupied something like 15GB - this is a problem - shrink the disk size, ex exend it to maximum size.
About "The access to the host resource is restricted..." you need to point as target the VC server which manage the ESX.
About hosts file - this helps when you access by name destination VC and/or ESX which are not visible in your source machine, to avoid this use the IP addresses.
The location of the file is c:\windows\system32\drivers\etc\hosts and adding the name-to-ip resolution is very simple, just edit it with notepad (running from elevated administrator).