Hi All, Hyper-V (Role) 2008R2 Server with 4 Nics 1 NIC Dedicated to the HOST 2nd NIC for Hyper-V Virtual Network (External) Hyper-V Host is not joined to our Domain I setup a W7 32BIT VM on this Hyper-V Host for testing purposes, Joined the VM to our domain (Fine) When I Check DNS (Forward Lookup zone) there is no record for this VM (as you would normally find for other domain joined machines) Can ping the machine with IP Address (IPV4) If I try to ping the machine with NAME w7vm , it responds on it's IPV6 default address (we don't use or have ipv6) If I try to manage the machine via AD Users & Computers, right click computer name > maange, it gives "network path not found" I did the following too (ON The Local Computer / Windows7 VM): Run gpedit.msc Browse Local Computer Policy Computer Configuration Administrative Templates Network DNS Client Enable "Allow DNS Suffix Appending to Unqualified Multi-Label Name Queries" unjoined from domain and then re-join still no dns record Computer account gets created in AD Users and Computers. At a loss here :-) can't seem to understand why ? we have several windows7 physical machines and they don't seem to have this problem. Will be grateful for your assistance Thanks and Regards PS : Also, I can't seem to login as a normal Domain user or as a Domain ADMIN when I RDP to this W7 VM, can only login as a local user via RDP - any thoughts?

Hi, Since this issue is related to the Hyper-V configurations, it is recommended to post in Hyper-V forum, they are the better resource to help you on this kind of issue: Hyper-V Forum Thanks for understanding and cooperation. Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

My suggestion is to create an (A) record manually in the DNS server. If it doesn't work try to unjoin again the machine from the domain, delete the DNS record manually created and delete the Computer Object in AD. Check again the network settings of the machine and from the command prompt type ipconfig /flushdns. At the end join again your machine to the domain

As Matteo pointed out, for the time being you can manually add an (A) record to the DNS server mapping w7vm to it's IP address. Also, please ensure that the check box in the DHCP scope properties > Dynamically update DNS A and PTR records only if requested by the DHCP clients is unchecked. Please post a screenshot to show what you see on the screen when you ping the client using it's name? Based on my knowledge, I'm guessing it replies back over IPv6 because of LLMNR (http://en.wikipedia.org/wiki/Link-local_Multicast_Name_Resolution).Kunal D Mehta - a Windows Server Enthusiast | My first TechNet Wiki Article