Hi

A newly installed Exchange 2013 Server (Mailbox and Client Access roles) shows every 5 minutes the event id's 16025 and 205 in the eventlog.

Both events are shown twice at the same time. First 205 then 16025 and again 205 and 16025.

Level: Error
Id 205 - Source: MSExchange Common
Id 16025 - Source: MSExchangeFrontEndTransport

Both have exactly the same description:
No DNS servers could be retrieved from network adapter 0957d69c-9b06-4b72-aa6b-ac825435b485. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results

Get-NetworkConnectionInfo shows the following results:
RunspaceId  : e854435f-ffbe-4ccb-81d9-7e729284e26a
Name        : Microsoft Hyper-V Network Adapter
DnsServers  : {10.10.32.34, 10.10.32.42}
IPAddresses : {10.10.32.45, 10.10.32.44, fe80::9cb9:ad68:c7cc:2052}
AdapterGuid : 0957d69c-9b06-4b72-aa6b-ac825435b485
MacAddress  : 00:1D:D8:B7:1E:2A
Identity    : 0957d69c-9b06-4b72-aa6b-ac825435b485
IsValid     : True
ObjectState : Unchanged

Mailflow is working, I would like to get rid of these error events.

Any suggestions?

Regards
Peter

• Edited by PeterN22 Friday, March 27, 2015 7:43 AM

To resolve these errors, try one of the following methods:

Open the Exchange Management Console locally on the Hub Transport server or Edge Transport server. Configure the internal DNS lookups to use all available network adapters, or a specific adapter that exists on the Hub Transport server or Edge Transport server.

or

Open the Exchange Management Shell. Run the Get-NetworkConnectionInfo cmdlet locally on the Hub Transport server or Edge Transport server. Note the GUID of the network adapters. Use the GUID of the desired network adapter as the value for the InternalDNSAdapterGUID parameter on the Set-TransportServer cmdlet. If you want to use the DNS settings of all available network adapters, enter a GUID of 00000000-0000-0000-0000-000000000000.

• Edited by Blake Jason Friday, March 27, 2015 10:44 AM
• Proposed as answer by Allen_WangJFMicrosoft contingent staff, Moderator Tuesday, April 07, 2015 1:37 AM
• Unproposed as answer by PeterN22 Tuesday, April 07, 2015 12:58 PM
• Proposed as answer by Blake Jason Wednesday, April 08, 2015 3:20 AM

Hi Allen

I already followed the two TechNet articles, still the same Problem.
I also followed your steps 1-3, still no success, and mail flow still works fine.

Please keep in mind, the source is not MSExchangeTransport, it's MSExchangeFrontEndTransport.

I have also tried to set the InternalDNSAdapterGUID using the Set-TransportServer as well as Set-FrontendTransportServer command.

Any other suggestion?

Regards
Peter

• Edited by PeterN22 Tuesday, April 07, 2015 1:08 PM

Anyone?

Not sure if you found an answer for this but I had the same problem and it drove me nuts. My DNS was fine and everything I found kept pointing to a problem with it.

Well I ended up checking the Register this connection's address in DNS on the Exchange NIC and that fixed it for me.

Hope that helps. 

Hi

Sorry english is not my native language. I'm not sure if I understand you correctly.

You checked the dns entry this Exchange nic made on the dns Server?

Regards
Peter