jaycasler
asked on
Unable to promote a DC in 2012r2 Hyper-V VM due to DNS failures
Please see attached text file for detailed description of process and failure(s)
I have rebuilt the VM from scratch twice and some of the promo failures vary but in the end the promo scripts just lose dns in one way or another. OTOH none of my physical machines are having any problems with this & I can create, promote and demote a dc on a physical machine with no problems of any kind.
Totally at a loss of how to get this to work.
dc-promo-fail.txt
I have rebuilt the VM from scratch twice and some of the promo failures vary but in the end the promo scripts just lose dns in one way or another. OTOH none of my physical machines are having any problems with this & I can create, promote and demote a dc on a physical machine with no problems of any kind.
Totally at a loss of how to get this to work.
dc-promo-fail.txt
Please post the results from the DC VM:
From the Hyper-V Host:
IPConfig /ALL
From the Hyper-V Host:
Get-NetAdapter | FL
Get-NetLbfoTeam | FL
Get-VMSwitch | FL
Please post the results in a CODE Snippet to make things easy to read.
ASKER
Diagnostics follow:
Performed 1st thing after re-boot of VM with local admin credentials
Host diagnostics (while VM running per above)
Performed 1st thing after re-boot of VM with local admin credentials
C:\Users\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : -redacted- & correct
Primary Dns Suffix . . . . . . . : -redacted- & correct
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : -redacted- & correct (matches primary)
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : -redacted- & correct (matched primary)
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
Physical Address. . . . . . . . . : 00-15-5D-01-04-F1
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::61:f731:f228:fb6e%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.10.1.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.1.254
DHCPv6 IAID . . . . . . . . . . . : 301995357
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-E5-D3-FA-00-15-5D-01-04-F1
DNS Servers . . . . . . . . . . . : 10.10.1.2
10.10.1.3
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.insideoutsports.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : -redacted- & correct
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\Administrator>ping -n 1 "dns-name"
Pinging -redacted- [10.10.1.2] with 32 bytes of data:
Reply from 10.10.1.2: bytes=32 time=1ms TTL=128
Ping statistics for 10.10.1.2:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
C:\Users\Administrator>nslookup 10.10.1.2
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 10.10.1.2
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
NSLookup on name also failsHost diagnostics (while VM running per above)
Get-NetAdapter
Name : Ethernet-PDC
InterfaceDescription : Realtek PCIe GBE Family Controller
InterfaceIndex : 12
MacAddress : 04-D9-F5-1D-B7-12
MediaType : 802.3
PhysicalMediaType : 802.3
InterfaceOperationalStatus : Up
AdminStatus : Up
LinkSpeed(Gbps) : 1
MediaConnectionState : Connected
ConnectorPresent : True
DriverInformation : Driver Date 2013-05-10 Version 8.1.510.2013 NDIS 6.30
Name : Ethernet-Host
InterfaceDescription : Intel(R) Gigabit CT Desktop Adapter
InterfaceIndex : 15
MacAddress : 68-05-CA-B2-4D-9D
MediaType : 802.3
PhysicalMediaType : 802.3
InterfaceOperationalStatus : Up
AdminStatus : Up
LinkSpeed(Gbps) : 1
MediaConnectionState : Connected
ConnectorPresent : True
DriverInformation : Driver Date 2013-04-17 Version 12.7.27.0 NDIS 6.30
Get-NetLbfoTeam produced no output (nics not teamed)
Get-VMSwitch
ComputerName : -redacted-
Name : vSwitch-DC
Id : 40547733-6cdd-47bc-8603-14f81b279652
Notes :
SwitchType : External
AllowManagementOS : False
NetAdapterInterfaceDescription : Realtek PCIe GBE Family Controller
AvailableVMQueues : 0
NumberVmqAllocated : 0
IovEnabled : False
IovVirtualFunctionCount : 0
IovVirtualFunctionsInUse : 0
IovQueuePairCount : 0
IovQueuePairsInUse : 0
AvailableIPSecSA : 0
NumberIPSecSAAllocated : 0
BandwidthPercentage : 10
BandwidthReservationMode : Absolute
DefaultFlowMinimumBandwidthAbsolute : 100000000
DefaultFlowMinimumBandwidthWeight : 0
Extensions : {Microsoft NDIS Capture, Microsoft Windows Filtering Platform}
IovSupport : False
IovSupportReasons : {To use SR-IOV on this system, the system BIOS must be updated to allow Windows
to control PCI Express. Contact your system manufacturer for an update., SR-IOV
cannot be used on this system as the PCI Express hardware does not support
Access Control Services (ACS) at any root port. Contact your system vendor for
further information., This network adapter does not support SR-IOV.}
IsDeleted : False
Key :
ASKER
Also note that NSlookup (forward & revers) from any physical machine in the network works fine. No LDAP or GPO problems during logins.
Is the VM running on server grade hardware? It does not look like it?
Is there a DC at 10.10.1.2 and 10.10.1.3?
Is there a DC at 10.10.1.2 and 10.10.1.3?
ASKER
The hardware is a 4 core/8 thread AMD with 8 GB ram. Granted it’s not a Xeon, but has more than enough resources for our small shop (< 30 clients) This is a replacement mobo for a 2008r2 system that ran for years on a 2 core/4 thread AMD with 8 G memory and an Intel nic.
The PDC is on .2 and the sencondary dc on .3 The .3 dc is the one I raised up to try and diagnose this but it installed, promoted, and runs just fine. Full dcdiag on both these machines passes with no problems. It’s just the VM that fails.
Any other diags I can do that might be helpful? While I didn’t want to do this would it help to disable the mobo nic and attach the vswitch to the Intel nic with host acces enabled?
The PDC is on .2 and the sencondary dc on .3 The .3 dc is the one I raised up to try and diagnose this but it installed, promoted, and runs just fine. Full dcdiag on both these machines passes with no problems. It’s just the VM that fails.
Any other diags I can do that might be helpful? While I didn’t want to do this would it help to disable the mobo nic and attach the vswitch to the Intel nic with host acces enabled?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What errors can you see in Event Viewer?
ASKER
I swapped the adapters, letting the VM use the Intel adapter and everything worked like a charm
What errors can you see in Event Viewer?