locked
Server 2019 "not connected to the internet" issue after domain join or dc promotion RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi guys,

    I just wanted to share my solution to an annoying networking bug I found with freshly domain joined Windows 2019 servers  (not resolved after all updates have been installed as per 11/11/2019).

    After the reboot to join the domain (or a server becoming a dc), I found that, even though all IP settings are set properly, internet works, and ping and ipconfig show no issues or misconfiguration, Windows still shows that the server is "not connected to the internet".

    The solution to this, in my case, turned out to be simply clicking "Change connection properties" in Settings -> Network & Internet -> Status.

    After having clicked "Change connection properties", the connection immediately reestablished.

    This connection issue/bug creates a situation where the domain controller can't seem to connect properly with other domain controllers, resulting in Event ID 16647 Information events in the Event Viewer System log, stating "The domain controller is starting a request for a new account-identifier pool." It takes a reboot to get rid of these messages.

    I think this is a bug in 2019, as i haven't seen this with previous versions of Windows, so I hope this post may help some people that are running into the same issue. 

    &quotThanks!"



    • Edited by Ed-man Monday, November 11, 2019 3:07 AM
    Monday, November 11, 2019 3:03 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello,

    Thank you for posting in our forum.

    Thanks for your sharing the resolution !

    According to your description, we click "change connection properties" like the following picture.


    I also have win server 2019 and it joined domain. However,it works fine.

     
    >>resulting in Event ID 16647 Information events in the Event Viewer System log, stating "The domain controller is starting a request for a new account-identifier pool." It takes a reboot to get rid of these messages.
    For information on event ID16647, we can refer to the article: Event ID 16650: The account-identifier allocator failed to initialize in Windows Server 

     This problem occurs in one of the following scenarios:
     
    -When the relative ID (RID) Master is restored from backup, it tries to synchronize with other domain controllers to verify that there are no other RID Masters online. However, the synchronization process fails if there are no domain controllers available to synchronize with, or if replication is not working.

    -The RID pool has been exhausted, or objects in Active Directory that are related to RID allocation use incorrect values or are missing.



    Hope the information can be helpful and if there is anything else we can do for you, please feel free to post in the forum.

    Best regards,
    Cynthia

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, November 12, 2019 8:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

     

    Best Regards,

    Cynthia

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, November 14, 2019 9:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Just want to confirm the current situations.

     

    Please feel free to let us know if you need further assistance.

     

    Best Regards,

    Cynthia

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 15, 2019 9:48 AM