please attach logs - do not paste them - its almost impossible to read this way
post the boot.ini please
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
I changed my posting.
Howto solve this problem now?
please post boot.ini as already requested
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
that may be to complicated for stupid converter
try
[d-12537] timeout=5 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Server Version 4.00"
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
I changed the boot.ini, but it doesn't help.
I'm getting the following error:
09:25:10 PM Step 1 : Connecting to VMware Converter Agent on 10.10.1.24
09:25:11 PM Step 2 : Creating target virtual machine and converting data
09:25:16 PM Configuring parameters for the target virtual machine...
09:25:20 PM WARNING: Dropping extra floppies
09:25:20 PM WARNING: Dropping extra parallel ports
09:25:20 PM Creating target virtual machine...
09:25:56 PM ERROR: Unable to open file %s
BTW ports 443 and 902 are open directly between the source server and the ESX host.
did you configure a target that already exists ?
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
NO, I don't have this target name on my ESX 3.5 Update2
Any idea to solve this problem?
Check the speed and duplex of the switch port. I set mine to Auto/Auto and the converter to Auto. Works for me.
Good Luck,
Scott
All switches are set to AUTO, but howto set the converter to AUTO?
BTW I have the following port open at the ESX firewall:
Opened ports:
SSH : port 22 tcp.out
esXpressLicenseClient: port 64420 udp.in
SNMPRequest : port 161 udp.in
FTP : port 21 tcp.out
HTTPS : port 443 tcp.in tcp.out
OpenManagement : port 1311 tcp.in
Backupexec : port 10000 tcp.in tcp.out
Do I need to open additional ports for the Converter?
I've solved this problem!
I've added the IP address and the host name of ESX and vCenter server to the hosts file from the NT machine and it works now.