Donald Henderson
asked on
Exchange: No DNS servers could be retrieved from network adapter that doesn't exist.
On Exchange 2010 in Event Viewer I'm getting 205 errors: "No DNS servers could be retrieved from network adapter b6ec8a19-09c6-4450-b4f5-77 f54556e860 . Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results."
Running Get-NetworkConnectionInfo gives two NICS (which are the internal and external ones)
RunspaceId : d3fa1621-9146-432c-8d3a-69 fdd7b2766c
Name : XenServer PV Network Device #0
DnsServers : {10.10.0.1, 10.10.0.2}
IPAddresses : {10.10.0.35, fe80::d951:d5d:bd06:34d8}
AdapterGuid : 1c4cbe9d-487a-4605-be10-32 d47c073e9b
MacAddress : 1A:44:17:0B:A4:73
RunspaceId : d3fa1621-9146-432c-8d3a-69 fdd7b2766c
Name : XenServer PV Network Device #1
DnsServers : {}
IPAddresses : {62.254.230.194, 46.102.207.187, fe80::64ee:30f1:ee7:c89d}
AdapterGuid : 6a08318a-7634-4747-b830-37 21c907965d
MacAddress : CA:B1:0A:B7:24:3E
neither of which seem to be the one giving the error.
Checking HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > WindowsNT > CurrentVersion > NetworkCards gives two additional NICs, both Realteks, but with different GUIDs.
A search of the registry for the GUID finds nothing.
How can I stop this error I I can't find the device it is referring to? System seems to be working OK. We are running as VM on XenServer host. Guest is Win 2008R2 SP1, 24GB RAM, Exchange 2010
Running Get-NetworkConnectionInfo gives two NICS (which are the internal and external ones)
RunspaceId : d3fa1621-9146-432c-8d3a-69
Name : XenServer PV Network Device #0
DnsServers : {10.10.0.1, 10.10.0.2}
IPAddresses : {10.10.0.35, fe80::d951:d5d:bd06:34d8}
AdapterGuid : 1c4cbe9d-487a-4605-be10-32
MacAddress : 1A:44:17:0B:A4:73
RunspaceId : d3fa1621-9146-432c-8d3a-69
Name : XenServer PV Network Device #1
DnsServers : {}
IPAddresses : {62.254.230.194, 46.102.207.187, fe80::64ee:30f1:ee7:c89d}
AdapterGuid : 6a08318a-7634-4747-b830-37
MacAddress : CA:B1:0A:B7:24:3E
neither of which seem to be the one giving the error.
Checking HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > WindowsNT > CurrentVersion > NetworkCards gives two additional NICs, both Realteks, but with different GUIDs.
A search of the registry for the GUID finds nothing.
How can I stop this error I I can't find the device it is referring to? System seems to be working OK. We are running as VM on XenServer host. Guest is Win 2008R2 SP1, 24GB RAM, Exchange 2010
Is this a physical or virtual server?
Follow this https://technet.microsoft.com/en-us/library/ff184583.aspx and enable displaying non-present devices. Search for network cards no longer present
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You should also check these registry key areas:
HKLM\System\CurrentControl Set\Servic es\Tcpip\P arameters\ Interfaces and Adapters for old interface settings.
HKLM\System\CurrentControl
ASKER
Vitual (VM running on XenSever as stated in query)
ASKER
Device manager/Properties/Details doesn't actually show the GUID anywhere. If I look at a known one the GUID is not to be found, so this isn't useful for tracking down the ghost NIC.
Registry (HKLM\System\CurrentContro lSet\Servi ces\Tcpip\ Parameters \Interface s and Adapters) doesn't show the adapter referenced in the Event log. Shows the two Virtual NICS and the two Realteks, which have different GUIDs.
On Exchange, the External DNS Lookups was not configured (Use Network card was selected, but field was blank). I've now set it and the events have stopped occurring. Looks like the blank un-configured setting was triggering some rogue event. Would have been much more useful if address was given as 0000000-0000-0000-0000-000 00000. Points to Michael and thanks all for your suggestions.
Registry (HKLM\System\CurrentContro
On Exchange, the External DNS Lookups was not configured (Use Network card was selected, but field was blank). I've now set it and the events have stopped occurring. Looks like the blank un-configured setting was triggering some rogue event. Would have been much more useful if address was given as 0000000-0000-0000-0000-000