docs(kb): VMware import scans succeed but file downloads fail#484
Open
CarlRodabaugh wants to merge 1 commit into
Open
docs(kb): VMware import scans succeed but file downloads fail#484CarlRodabaugh wants to merge 1 commit into
CarlRodabaugh wants to merge 1 commit into
Conversation
The VMware Service uses vCenter only to enumerate/locate files; the actual transfer goes directly to the ESXi host by FQDN. When the service can't resolve or reach that host (DNS, or ports 443/902 blocked), the scan succeeds while every download fails with 'server refused connection'. Covers diagnosis and fix. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New KB article for a common VMware import/backup failure: the VMware Service connects to vCenter and scans VMs fine, but jobs fail with
The server refused connectionthe moment they start pulling files — and the failure hits every file, including the tiny.vmx/.vmxf/.nvramconfigs.Root cause: vCenter is used only to enumerate and locate files; the actual transfer goes directly to the ESXi host by the FQDN vCenter returns. If the service VM can't resolve or reach that host, vCenter looks healthy while downloads fail. Two causes: DNS resolution of ESXi host FQDNs, or TCP 443/902 (NFC) not open to each ESXi host directly. Includes diagnosis via the VMware Service Diagnostics panel and the fix.
Type
Troubleshooting
Source
Recurring support pattern — two customer cases. Promoted from internal support KB.
Checks
validate_frontmatter.pypasses locallyvmware-service-vm-nic-ipv4-configuration,vmwarebackupdrguide)🤖 Generated with Claude Code