No DNS servers could be retrieved from network adapter %1. Verify that the computer is connected to a network and that the Get-NetworkConnectionInfo cmdlet returns results.

Details
Product: Exchange
Event ID: 16025
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: InvalidAdapterGuid
Message: No DNS servers could be retrieved from network adapter %1. Verify that the computer is connected to a network and that the Get-NetworkConnectionInfo cmdlet returns results.
   
Explanation

This Error event indicates the specified network adapter that is configured for internal DNS lookups on the Microsoft Exchange Server 2007 Hub Transport server or Edge Transport server is invalid.

Internal DNS lookup servers are used to resolve IP addresses inside the Exchange organization. The following options are available for internal DNS lookups:

  • Use specific DNS servers. This option does not apply to this Error event.

  • Use network adapter settings.

By default, internal DNS lookups are performed by using the DNS settings of all available network adapters in the Hub Transport server or Edge Transport server. If you want to use the DNS settings of a specific network adapter for internal IP address resolution, you can use the following methods:

  • Set the InternalDNSAdapterGUID parameter on the Set-TransportServer cmdlet in the Exchange Management Shell. The value of this parameter is the GUID of a network adapter that exists in the Hub Transport server or Edge Transport server. The network adapter GUID can be found by using the Get-NetworkConnectionInfo cmdlet.

  • Set the value on the Internal DNS Lookups tab in the properties of the Hub Transport server or Edge Transport server in the Exchange Management console. You select the network adapter from a drop-down list.

The most likely cause of this error occurs when you try to select a specific network adapter for internal DNS lookups in an Exchange Management Console session that was not started locally on the Hub Transport server or Edge Transport server. The network adapters that appear in the drop-down list are the network adapters that exist on the computer from which the Exchange Management Console session was started.

   
User Action

To resolve this error, do one of the following:

  • 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.

  • 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.

For more information, see Configuring Transport Server Properties.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply