Link to home
Start Free TrialLog in
Avatar of Glenn Thibeault
Glenn Thibeault

asked on

Missing Network adapter in DCDiag output

When I run DCdiag.exe I get the following error. I for the life of me can’t find this adapter that is listed in the errors.

Command: C:\Users\administrator>%windir%\system32\dcdiag.exe /c /test:DNS /DNSBasic

TEST: Basic (Basc)
    Warning: Adapter B0:83:FE:DD:EC:7F has dynamic IP address
    (can be a misconfiguration)
    Warning: adapter [00000019] Hyper-V Virtual Ethernet Adapter
    has invalid DNS server: 8.8.8.8 (<name unavailable>)

            DNS server: 8.8.8.8 (<name unavailable>)
               1 test failure on this DNS server
               Name resolution is not functional. _ldap._tcp.SK.LOCAL. failed on
 the DNS server 8.8.8.8

I am getting a lot of DCom error in my event log related to this.
I have tried NETSH, Get-VMNetworkAdapter in Powershell, Get-NetworkAdapter in Powershell and device manager. I can’t find the adapter to fix the settings. Thanks
Avatar of Alex
Alex
Flag of United Kingdom of Great Britain and Northern Ireland image

why are you using googles DNS servers, that'll only do internet translation which will be covered by your firewall, not your DC.


Ohhhhh I see now

Click Start>Run.
Type cmd.exe in the textbox and click OK.
Type set devmgr_show_nonpresent_devices=1 and hit ENTER.

Launch Devmgmt.msc

Click view, show hidden devices and uninstall it from there :-)
Avatar of Glenn Thibeault
Glenn Thibeault

ASKER

Been there many times. Not Listed. See attached.
2019-09-13-08_33_04-SKSRV---ConnectW.png
Did you show the hidden devices first, you actually need to run that command first otherwise it won't show you orphaned network cards.
Yes I did. Here is the Another screen shot.
2019-09-13-08_58_50-SKSRV---ConnectW.png
It's the hyper-V virtual ethernet adapter right, is that not in your network and sharing center?
Check the DNS settings on VEthernet.
Alex
Sorry got tied up this weekend. I did check the Hyper-V network settings. They are good. I thought I was on to something when I found a hidden network adapter in the Hyper-V  machine, but I deleted it and that didn't fix the issue. I always thought the that any network adapters and there settings with in a Hyper-V machine would be hidden from the host OS.
What I don't understand, you've clearly got a google DNS server in there.

When you run ipconfig /all on the VM, what network card does it say has the 8.8.8.8 address?
Here is the IP config /all of the VM. Looks OK. Maybe time to look in the registry but not even sure it is stored there/

Windows IP Configuration

   Host Name . . . . . . . . . . . . :
   Primary Dns Suffix  . . . . . . . : ???.LOCAL
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ???.LOCAL

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . : ???.LOCAL
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter #2
   Physical Address. . . . . . . . . : 00-15-5D-10-03-02
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.16.113(Preferred)
   Subnet Ma??? . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, September 14, 2019 3:36:21 AM
   Lease Expires . . . . . . . . . . : Sunday, September 22, 2019 7:16:52 AM
   Default Gateway . . . . . . . . . : 192.168.16.1
   DHCP Server . . . . . . . . . . . : 192.168.16.2
   DNS Servers . . . . . . . . . . . : 192.168.16.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.???.LOCAL:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : ???.LOCAL
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces

Go and take a look in there, clear out the incorrect interface.
There are a few interfaces with 8.8.8.8 in them. But that IP is good. It is just 1 interface that is the issue. I am not sure I feel comfortable deleting the interfaces via the registry. Either way I can't do anything until the weekend since this is a production server. I will keep poking around to then.
You're using google DNS on a domain controller, it's not really ideal to be fair. You're better off pointing the DNS IP to your other domain controllers.
Don't have any other domain controllers.So the theory here is if the Domain controller dies, the clients will fall over to Google and be able to reach the internet.
.... You're running a single domain controller and you're expecting people to still be able to access the internet when they won't even be able to log on. That's genius....

Build a second one, because when you lose your DC, you're screwed
Thanks for the insult. The can logon for a while if the domain controller is offline with cached credentials. But I am guessing you knew that. I have tested it many times.
That wasn't an insult, it was sarcasm, an insult would be saying that you're stupid, which I'm certainly not saying, misguided or a simple lack of experience would be more apt.

Your idea is a terrible plan, you are actually planning for doing a full active directory restore when it is simply not required. Please please build a second DC, if you want to set DNS servers to google, do it in GPO.

Regards,
Alex
Alex
Thanks for you input. I think I can handle the issue from here on out.
Ok Good luck....

Regards,
Alex
Anyone else out there have idea's?
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.