Issue joining W7 Hyper-V guests to domain

A

Angry_Birds

Weaksauce
Joined
Aug 16, 2011
Messages
67
Hi all,

I am having an issue where I cannot join Windows 7 Hyper-V guests to the domain. I have tried joining both VM and physical XP boxes (both work), as well as a few physical Windows 7 boxes which work fine as well.

Whenever I try to join the domain via FQDN, it prompts me for credentials, hangs for a good 5-10 minutes, and then either tells me "network path cannot be found" or "RPC server is unavailable". I can ping the primary DC via FQDN and IP, and I've checked the forward lookup zones on the primary DC and they all point to the correct IP address. Just to test, I have turned off firewall on both host, guest, and DC to no avail.

Any guidance would be much appreciated..
 
This is the output from the log file (WS11 is the computer, va.rapyoke.com is the domain):

10/03/2011 23:25:27:662 -----------------------------------------------------------------
10/03/2011 23:25:27:662 NetpValidateName: checking to see if 'WS11' is valid as type 1 name
10/03/2011 23:25:27:662 NetpCheckNetBiosNameNotInUse for 'WS11' [MACHINE] returned 0x0
10/03/2011 23:25:27:662 NetpValidateName: name 'WS11' is valid for type 1
10/03/2011 23:25:27:662 -----------------------------------------------------------------
10/03/2011 23:25:27:662 NetpValidateName: checking to see if 'WS11' is valid as type 5 name
10/03/2011 23:25:27:662 NetpValidateName: name 'WS11' is valid for type 5
10/03/2011 23:25:27:662 -----------------------------------------------------------------
10/03/2011 23:25:27:662 NetpValidateName: checking to see if 'va.rapyoke.com' is valid as type 3 name
10/03/2011 23:25:28:193 NetpCheckDomainNameIsValid [ Exists ] for 'va.rapyoke.com' returned 0x0
10/03/2011 23:25:28:193 NetpValidateName: name 'va.rapyoke.com' is valid for type 3
10/03/2011 23:25:35:709 -----------------------------------------------------------------
10/03/2011 23:25:35:709 NetpDoDomainJoin
10/03/2011 23:25:35:709 NetpMachineValidToJoin: 'WS11'
10/03/2011 23:25:35:709 OS Version: 6.1
10/03/2011 23:25:35:709 Build number: 7601 (7601.win7sp1_rtm.101119-1850)
10/03/2011 23:25:35:709 ServicePack: Service Pack 1
10/03/2011 23:25:35:709 SKU: Windows 7 Enterprise
10/03/2011 23:25:35:709 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0
10/03/2011 23:25:35:709 NetpGetLsaPrimaryDomain: status: 0x0
10/03/2011 23:25:35:709 NetpMachineValidToJoin: status: 0x0
10/03/2011 23:25:35:709 NetpJoinDomain
10/03/2011 23:25:35:709 Machine: WS11
10/03/2011 23:25:35:709 Domain: va.rapyoke.com
10/03/2011 23:25:35:709 MachineAccountOU: (NULL)
10/03/2011 23:25:35:709 Account: va.rapyoke.com\Administrator
10/03/2011 23:25:35:709 Options: 0x25
10/03/2011 23:25:35:709 NetpLoadParameters: loading registry parameters...
10/03/2011 23:25:35:709 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
10/03/2011 23:25:35:709 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
10/03/2011 23:25:35:709 NetpLoadParameters: status: 0x2
10/03/2011 23:25:35:709 NetpValidateName: checking to see if 'va.rapyoke.com' is valid as type 3 name
10/03/2011 23:25:35:834 NetpCheckDomainNameIsValid [ Exists ] for 'va.rapyoke.com' returned 0x0
10/03/2011 23:25:35:834 NetpValidateName: name 'va.rapyoke.com' is valid for type 3
10/03/2011 23:25:35:834 NetpDsGetDcName: trying to find DC in domain 'va.rapyoke.com', flags: 0x40001010
10/03/2011 23:25:39:006 NetpDsGetDcName: failed to find a DC having account 'WS11$': 0x525, last error is 0x0
10/03/2011 23:25:39:006 NetpLoadParameters: loading registry parameters...
10/03/2011 23:25:39:006 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
10/03/2011 23:25:39:006 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
10/03/2011 23:25:39:006 NetpLoadParameters: status: 0x2
10/03/2011 23:25:39:006 NetpDsGetDcName: status of verifying DNS A record name resolution for 'DC02.va.rapyoke.com': 0x0
10/03/2011 23:25:39:006 NetpDsGetDcName: found DC '\\DC02.va.rapyoke.com' in the specified domain
10/03/2011 23:25:39:006 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
10/03/2011 23:26:29:506 NetUseAdd to \\DC02.va.rapyoke.com\IPC$ returned 64
10/03/2011 23:26:29:506 NetpJoinDomain: status of connecting to dc '\\DC02.va.rapyoke.com': 0x40
10/03/2011 23:26:29:506 NetpJoinDomainOnDs: Function exits with status of: 0x40
10/03/2011 23:26:29:506 NetpDoDomainJoin: status: 0x40
10/03/2011 23:26:29:506 -----------------------------------------------------------------
10/03/2011 23:26:29:506 NetpDoDomainJoin
10/03/2011 23:26:29:506 NetpMachineValidToJoin: 'WS11'
10/03/2011 23:26:29:506 OS Version: 6.1
10/03/2011 23:26:29:506 Build number: 7601 (7601.win7sp1_rtm.101119-1850)
10/03/2011 23:26:29:506 ServicePack: Service Pack 1
10/03/2011 23:26:29:506 SKU: Windows 7 Enterprise
10/03/2011 23:26:29:506 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0
10/03/2011 23:26:29:506 NetpGetLsaPrimaryDomain: status: 0x0
10/03/2011 23:26:29:506 NetpMachineValidToJoin: status: 0x0
10/03/2011 23:26:29:506 NetpJoinDomain
10/03/2011 23:26:29:506 Machine: WS11
10/03/2011 23:26:29:506 Domain: va.rapyoke.com
10/03/2011 23:26:29:506 MachineAccountOU: (NULL)
10/03/2011 23:26:29:506 Account: va.rapyoke.com\Administrator
10/03/2011 23:26:29:506 Options: 0x27
10/03/2011 23:26:29:506 NetpLoadParameters: loading registry parameters...
10/03/2011 23:26:29:506 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
10/03/2011 23:26:29:506 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
10/03/2011 23:26:29:506 NetpLoadParameters: status: 0x2
10/03/2011 23:26:29:506 NetpValidateName: checking to see if 'va.rapyoke.com' is valid as type 3 name
10/03/2011 23:26:29:631 NetpCheckDomainNameIsValid [ Exists ] for 'va.rapyoke.com' returned 0x0
10/03/2011 23:26:29:631 NetpValidateName: name 'va.rapyoke.com' is valid for type 3
10/03/2011 23:26:29:631 NetpDsGetDcName: trying to find DC in domain 'va.rapyoke.com', flags: 0x40001010
10/03/2011 23:26:44:631 NetpDsGetDcName: failed to find a DC having account 'WS11$': 0x525, last error is 0x0
10/03/2011 23:26:44:631 NetpLoadParameters: loading registry parameters...
10/03/2011 23:26:44:631 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
10/03/2011 23:26:44:631 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
10/03/2011 23:26:44:631 NetpLoadParameters: status: 0x2
10/03/2011 23:26:44:631 NetpDsGetDcName: status of verifying DNS A record name resolution for 'DC02.va.rapyoke.com': 0x0
10/03/2011 23:26:44:631 NetpDsGetDcName: found DC '\\DC02.va.rapyoke.com' in the specified domain
10/03/2011 23:26:44:631 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
10/03/2011 23:27:36:553 NetUseAdd to \\DC02.va.rapyoke.com\IPC$ returned 64
10/03/2011 23:27:36:553 NetpJoinDomain: status of connecting to dc '\\DC02.va.rapyoke.com': 0x40
10/03/2011 23:27:36:553 NetpJoinDomainOnDs: Function exits with status of: 0x40
10/03/2011 23:27:36:553 NetpDoDomainJoin: status: 0x40
 
Have you tried creating the computer account in AD before adding it and see if it will join that way?
 
Ok, can you try using a legacy network adapter instead of the Hyper-V one and see if it will work over that?
 
Eickst said:
Ok, can you try using a legacy network adapter instead of the Hyper-V one and see if it will work over that?
Click to expand...

THANK YOU!! That was the issue. The clients are connected at only 100 mbps, but that's better than nothing at all.

If I can paypal you money to buy a sixpack or something please let me know, me and the other administrator at work had been spending almost all day looking for a solution to this.
 
You can try narrowing this down more if you want or you can live with that work around. Make a new vm and on the ethernet adapter try disabling "receive side scaling" before you join the domain and see if that will work and let you stay with the full network adapter.

netsh interface tcp set global rss=disabled

And no paypal required!

BTW what are you running on the DC, 2k3? or 2k8?
 
Unfortunately that didn't work. The second gigabit adapter we're currently using for the VM host is a Trendnet (until the Intel stuff comes in :) ). It's obviously not an enterprise-level card, so do you think there's a possibility that it's just driver-related (Realtek chipset I'm pretty sure)?

The DC's are both 2k8 R2.
 
I would try again once you get a new NIC but I don't know enough about the inner workings of Hyper-v to offer any other solution.

Once you have them joined can you add a hyper-v network adapter to the VM and see if it still can connect to the domain? That may be a better workaround, use the legacy to add them to the domain and then go to the full blown adapter.
 
You must log in or register to reply here.
Back
Top