Exchange – Event ID 205 and Event ID 16025

KB ID 0001251 


At a client this week, they were having a LOT of mail flow problems. Looking at the queue viewer, I could see that all their mail was sat in queues waiting to go into their mails stores. There was a queue for each mail store, and the error on each was “451 4.4.0 DNS query failed Exchange Server error in message queue“. Looking in the Application log it was full of Event ID 205, and 16025 Errors Stating;

Event ID 205

Source MSExchange Common

No DNS servers could be retrieved from network adapter {GUID} Check that the computer is connected to a network and that the Get-NetworkConnectionInfo cmdlet returns results.


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


First you need to get the ‘Identity” of your actual network card with a Get-NetworkConnectionInfo command, (make sure the correct DNS settings are set for this NIC, i.e. it’s not pointing to a PUBLIC DNS server!)  Once you have it, change the Transport service to use this new ID, with a Set-TransportServer command.

Set-TransportServer {Name-Of-Server} -InternalDNSAdapterGUID {GUID} -ExternalDNSAdapterGUID {GUID}

Set Transport Server GUID

Then Restart the Microsoft Exchange Transport Service and the Microsoft Exchange Mailbox Transport Service.

Related Articles, References, Credits, or External Links


Author: PeteLong

Share This Post On


  1. Brilliant – you’re a life saver. This affected me after a change of NICs on a VMWare server from E1000 to VMXNET3. Exchange 2016 on Server 2016. Nothing is ever simple in Exchange, that’s for sure…

    Post a Reply
  2. You’re really a life saver. I got this problem after a exchange server recovery installation. The nic of the recovered machine got a new guid, but the transport service knows the old one.
    The queue was full! After the PS cmd everything’s fine.
    Thank you very, very much!

    Post a Reply
  3. i followed the instructions, but got this error

    WARNING: The command completed successfully but no settings of ” have been modified.

    it didn’t take, because after reboot, i’m still getting the error.
    what are the troubleshooting steps i should do next?

    Post a Reply
  4. Lifesaver! Like Rob above I rolled by my vmware tools and vmxnet3 driver to see if it would resolve some Exchange/Outlook latency issues and it killed delivery of my emails to mailboxes – the queues had DNS errors. fixed using your solution in 1 minute.

    Lesson learnt: changing the vmtools/vmxnet3 driver results in the old NIC GUID hanging around – use this fix to resolve it 😉

    Cheers 😉

    Post a Reply
  5. It worked for me but there is a typo. M is written instead of N.

    InternalDMSAdapterGUID should be InternalDNSAdapterGUID


    Post a Reply
  6. Thanks Pete!
    Same issue, reinstall of vmware tools and different GUIDs after that.
    The mail server started delivering again after the procedure.

    Post a Reply
  7. This is helped me get mail flowing at the school I work at. Thank you so much!

    Post a Reply
  8. Sadly, did not work for me. Even after doing this the server throws the same errors.

    Post a Reply
  9. Awesome! Worked like a charm!

    Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *