What you’re seeing
- The VM boots and you can log in at the console, but it can't reach the network, the internet or the domain.
- Windows shows 'No network access', an unidentified network, or a 169.254 address.
- The guest's network adapter has a new name, such as Ethernet 2, with none of the old settings.
- In Hyper-V or vSphere, the VM's adapter shows as not connected, or attached to a switch that doesn't exist on this host.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The virtual switch or port group name on the new host differs from the original, so the adapter isn't connected to anything.
- The restored VM received a new virtual NIC with a different MAC address, and Windows treated it as a new adapter without the old static IP.
- VLAN tagging on the new host or port group doesn't match the network the VM belongs on.
- A cloned VM shares an IP address or MAC address with the original, causing a conflict.
- Hypervisor integration services or VMware Tools lack drivers for the new virtual network adapter type.
Why it matters
A restored or migrated server that can't talk to the network is effectively still down, even though it appears to be running. File shares, applications and authentication remain unavailable, so the business is still paying for the outage. If a cloned VM conflicts with the original, both may become unreachable, or the domain may see duplicate computers. Getting the networking right is often the last step that determines whether a recovery or migration counts as a success.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Did something go wrong with the restore itself?
Usually not. The data and operating system are typically fine; it's the connection between the VM and the host's networking that needs to be matched up.
Could this affect the original server if it's still running?
Yes, if the copy uses the same name, IP or MAC address. We look for conflicts before bringing the VM onto the network.