Win 2016 server problem with loosing connection

Target audience: System Administrators
Used tools: PowerShell, Event Viewer, Task Schedular
What’s the purpose: Automatic repair network connection with Windows server 2016

What’s the problem ? We have a PC Lenovo Tiny M73 with CPU G1820T, 2GB RAM, 320GB HDD as Windows Server Standard 2016

At first – to make server software to work on this hardware, you have to install LAN driver Intel® Ethernet Connection I217-V

Then – the server work – even not so quickly, with only 2GB RAM, but works !

The next problem is that 1-2 times in a month something goes wrong with NIC – there are no ping to the server but you can use its shared resources and connect to the server with Remote Desktop Connection (RDP) – NetBIOS working but TCP/IP – not. When I restart NIC, the things working out OK – so far we have a problem – stop working NIC and how to resolve it – by restarting NIC But – but remain the the problem – how to understand that NIC is not working ? Now – it’s done when somebody call to tell that the application from the server did not working and then we have to manually restart NIC Then I find out that at the same time the servers’ NIC stoped working, one of our mini switch stopped working too. Now, it’s time to inspect the servers’ LOG files and find out what’s happened at the time of interruption.

And here is the result : The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: 

       Adapter Name : {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx}
       Host Name : sxxxxxxxxx
       Primary Domain Suffix : xxxxxxxxxt.xxx
       DNS server list :
             xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx
       Sent update to server : <?>
       IP Address(es) :
         xxx.xxx.xxx.xxx

        - System 
        - Provider 
        [ Name]  Microsoft-Windows-DNS-Client 
        [ Guid]  {1C95126E-7EEA-49A9-A3FE-A378B03DDB4D} 
        EventID 8015
        Version 0 
        Level 3 
        Task 1028 
        Opcode 0 
        Keywords 0x4000000000000000

The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running at this time. You can manually retry DNS registration of the network adapter and its settings by typing ‘ipconfig /registerdns’ at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

Solution :

  1. Make PowerShell script for restarting NIC interface
  2. Make a custom event view for EventID = 8015
  3. Attach script for restarting NIC interface to the the custom event view and add it to task scheduler !!!
Published By
Categorized as LAN