Hello All,
Been searching but not able to find my answer(s).... So I do really appreciate the help. I'm seeing info for workstation, but not for ESX/vCenter....
I have VirtualCenter 2.5 installed on Windows 2003. I have 6 production ESX 3.5 servers that I manage with vCenter.
Recently we updated DNS servers throughout the company, so I was forced to update. ESX servers /etc/resolv.conf was updated a day later to reflect updated DNS servers.
On my Win2k3 server I have multiple NIC's..
-1 NIC is dedicated for Corporate Network, set as metric 10
-1 NIC is dedicated for backup, set as metric 20
How should I setup my VMnet1 and VMnet8 adapters? Currently they are disabled as my server starting pointing to the 192.168.x.x IP's causing another service to fail. The server wanted to resolve to the 192.168.x.x IP.
I've been trying to use converter on the same machine vCenter is installed on, and getting the following error: FAILED: Unable to connect to the virtual disk.
I'm assuming that because the VMnet1 and VMnet8 adapters are not setup correctly.
Previous weeks I was able to clone with no issues, and my server was not trying to resolve to the wrong IP.
PLEASE help!
Here's part of the log file for a failed converter attempt:
fullMessage = "Failed to clone disk 0 on the virtual machine 'Ubuntu10_Gold'.",
vmName = "Ubuntu10_Gold",
sourceDisk = "0",
reason = (converter.agent.internal.fault.NfcConnectionFault) {
dynamicType = ,
faultCause = (vmodl.MethodFault) null,
faultMsg = "File transfer failed.
Src error: File error -- Failed to write to the target file: An error was detected",
msg = "Unable to connect to the virtual disk.",
Thanks!