Can't Ping domain VM after convert from Physical to Virtual.

[Hawary1]

Hi All,

I have an issue that i used VMWare converter standalone which i installed on a virtual machine (hyper-v) to convert this machine to vsphere 6.0 but after conversion, I'm able to ping the IP normally but when i ping the name i got no reply although the entry is there in the DNS. any one faced same issue before and what was the solution?

Thanks all

[DanielOprea]

Good morning,

After migration, you did a cleanup of obsolete drivers?
The current network card are vmxnet3 model? You have the vmware tools in the latest version?
You have reviewed the events N.A. ?? You appear?
You have connectivity with the gateway?
VM is configured in the corresponding VLAN ??

Regards

Daniel

[Dan_Johnson]

What happens when you do a ping -a of the IP address?

EG ping -a 192.168.1.1

What about a tracert of the IP?

EG tracert 192.168.1.1

Are you able to ping out from the Virtual Machine to other devices on your network?

How many NICs does the VM have?

[Hawary1]

Hi Daniel,

thank you for your reply.

After migration, you did a cleanup of obsolete drivers? actually i didn't cleanup the obsolete drivers, how can i do that?.

The current network card are vmxnet3 model? You have the vmware tools in the latest version? yes the network card is vmxnet3 and also yes i installed the latest vmware coming with vsphere 6.0

You have reviewed the events N.A. ?? You appear? i didn't get what you mean.

You have connectivity with the gateway? yes and i'm able to ping this vm from any PC in the network by IP but not the name.

VM is configured in the corresponding VLAN ?? yes, i selected the correct port group represents the required VLAN during the conversion.

i believe that there is DNS cache issue since the only time I'm able to ping this virtual machine by name is from the DNS server. is it make any difference if during the conversion i selected to convert the powered on machine instead of hyper-v?

[Hawary1]

Hi Dan,

Thank you for your reply.

- when i ping with -a , i get the reply and it resolves the name, i means it gives the correct name of the vm but without the domain name( VMname instead of VMname.domain.local), i believe because i'm pinging from another domain machine.

- actually i didn't try to tracert but i believe it will work since i'm able to ping in both direction from and to the vm but only IP.

- I have only one NIC.

[DanielOprea]

Hi,

To cleanup, use the attached script.

For the resolution DNS client, look to this KB: https://technet.microsoft.com/en-us/library/cc755882(v=ws.10).aspx and from check the DNS server look to this KB: https://technet.microsoft.com/en-us/library/cc787724(v=ws.10).aspx

Regards

Daniel