board logo
Posted by: drdread - 05 February 2025 09:31:08
I have a weird selection of errors that come up intermittently, sometimes several times a day. It starts with: Log Name: System Source: NETLOGON Date: 2/5/2025 7:15:31 AM Event ID: 5782 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: DC2.domain.local Description: Dynamic registration or deregistration of one or more DNS records failed with the following error: No DNS servers configured for local system. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="NETLOGON" /> <EventID Qualifiers="0">5782</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-02-05T07:15:31.493258000Z" /> <EventRecordID>7743</EventRecordID> <Channel>System</Channel> <Computer>DC2.domain.local</Computer> <Security /> </System> <EventData> <Data>%%9852</Data> <Binary>7C260000</Binary> </EventData> </Event> [/code] Then we get: Log Name: System Source: q57nd60a Date: 2/5/2025 7:15:31 AM Event ID: 4 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: DC2.domain.local Description: HP Ethernet 1Gb 4-port 331i Adapter: The network link is down. Check to make sure the network cable is properly connected. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="q57nd60a" /> <EventID Qualifiers="32773">4</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-02-05T07:15:31.461996400Z" /> <EventRecordID>7744</EventRecordID> <Channel>System</Channel> <Computer>DC2.domain.local</Computer> <Security /> </System> <EventData> <Data>\Device\NDMP2</Data> <Data>HP Ethernet 1Gb 4-port 331i Adapter</Data> <Binary>00000000020030000000000004000580000000000000000000000000000000000000000000000000</Binary> </EventData> </Event>[/code] Then: Log Name: System Source: q57nd60a Date: 2/5/2025 7:15:38 AM Event ID: 11 Task Category: None Level: Information Keywords: Classic User: N/A Computer: DC2.domain.local Description: HP Ethernet 1Gb 4-port 331i Adapter: Network controller configured for 1Gb full-duplex link. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="q57nd60a" /> <EventID Qualifiers="16389">11</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-02-05T07:15:38.105317000Z" /> <EventRecordID>7746</EventRecordID> <Channel>System</Channel> <Computer>DC2.domain.local</Computer> <Security /> </System> <EventData> <Data>\Device\NDMP2</Data> <Data>HP Ethernet 1Gb 4-port 331i Adapter</Data> <Binary>0000000002003000000000000B000540000000000000000000000000000000000000000000000000</Binary> </EventData> </Event>[/code] Log Name: System Source: q57nd60a Date: 2/5/2025 7:15:39 AM Event ID: 4 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: DC2.domain.local Description: HP Ethernet 1Gb 4-port 331i Adapter: The network link is down. Check to make sure the network cable is properly connected. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="q57nd60a" /> <EventID Qualifiers="32773">4</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-02-05T07:15:39.519551700Z" /> <EventRecordID>7747</EventRecordID> <Channel>System</Channel> <Computer>DC2.domain.local</Computer> <Security /> </System> <EventData> <Data>\Device\NDMP2</Data> <Data>HP Ethernet 1Gb 4-port 331i Adapter</Data> <Binary>00000000020030000000000004000580000000000000000000000000000000000000000000000000</Binary> </EventData> </Event>[/code] Log Name: System Source: HP Ethernet Date: 2/5/2025 7:15:45 AM Event ID: 2 Task Category: Network Device Level: Error Keywords: Classic User: N/A Computer: DC2.domain.local Description: If the Network Interface is an Ethernet Port, the Ethernet Port has transitioned from OK to Error. If the Network Interface is an Ethernet Team, the Ethernet Team has transitioned from Fully Redundant, Degraded Redundancy or Redundancy Lost to Overall Failure, due to a failed team member. User Action View the Ethernet and Ethernet Team Member status in the HPE Network Configuration Utility (NCU) if you are using Windows Server 2008. For Windows Server 2012 users, view the status with Microsoft teaming Management UI..View the System Event Log for additional information. WBEM Indication Properties AlertingElementFormat: 2 0x2 (CIMObjectPath) AlertingManagedElement: "\\DC2\ROOT\HPQ:HP_WinEthernetPort.DeviceID="{3468F9CD-4E37-477C-97D8-B1D3BFBC3524}",CreationClassName="HP_WinEthernetPort",SystemCreationClassName="HP_WinComputerSystem",SystemName="DC2.domain.local"" AlertType: 2 0x2 (Communications Alert) Description: "If the Network Interface is an Ethernet Port, the Ethernet Port has transitioned from OK to Error. If the Network Interface is an Ethernet Team, the Ethernet Team has transitioned from Fully Redundant, Degraded Redundancy or Redundancy Lost to Overall Failure, due to a failed team member." EventCategory: 9 0x9 (Network Device) EventID: "2" EventSubCategory: 11 0xb (Ethernet Port) ImpactedDomain: 4 0x4 (System) IndicationIdentifier: "{083DA59C-105A-40FE-A687-FFEF0CFF7CF7}" IndicationTime: "20250205071531.649000+000" OSType: 117 0x75 (Microsoft Windows Server 2016) OSVersion: "10.0.14393" PerceivedSeverity: 6 0x6 (Critical) ProbableCause: 7 0x7 (Communications Subsystem Failure) ProbableCauseDescription: "Network Interface Lost Connectivity" ProviderName: "HP Ethernet" ProviderVersion: "10.60.0.0" RecommendedActions[0]: "View the Ethernet and Ethernet Team Member status in the HPE Network Configuration Utility (NCU) if you are using Windows Server 2008. For Windows Server 2012 users, view the status with Microsoft teaming Management UI..View the System Event Log for additional information." Summary: "The Network interface has lost connectivity." SystemCreationClassName: "HP_WinComputerSystem" SystemFirmwareVersion[0]: "2.40_02-17-2017" SystemFirmwareVersion[1]: "2.40 _02-17-2017" SystemGUID: "38353338-3734-5A43-3237-32393032544C" SystemModel: "ProLiant ML350 Gen9" SystemName: "DC2.domain.local" SystemProductID: "835847-035" SystemSerialNumber: "CZ272902TL" TIME_CREATED: 133832133457107527 0x1db779dc63e5a47 For more information, please contact HPE Support. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="HP Ethernet" /> <EventID Qualifiers="49152">2</EventID> <Level>2</Level> <Task>9</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-02-05T07:15:45.835812600Z" /> <EventRecordID>7749</EventRecordID> <Channel>System</Channel> <Computer>DC2.domain.local</Computer> <Security /> </System> <EventData> <Data>If the Network Interface is an Ethernet Port, the Ethernet Port has transitioned from OK to Error. If the Network Interface is an Ethernet Team, the Ethernet Team has transitioned from Fully Redundant, Degraded Redundancy or Redundancy Lost to Overall Failure, due to a failed team member.</Data> <Data>View the Ethernet and Ethernet Team Member status in the HPE Network Configuration Utility (NCU) if you are using Windows Server 2008. For Windows Server 2012 users, view the status with Microsoft teaming Management UI..View the System Event Log for additional information.</Data> <Data>AlertingElementFormat: 2 0x2 (CIMObjectPath) AlertingManagedElement: "\\DC2\ROOT\HPQ:HP_WinEthernetPort.DeviceID="{3468F9CD-4E37-477C-97D8-B1D3BFBC3524}",CreationClassName="HP_WinEthernetPort",SystemCreationClassName="HP_WinComputerSystem",SystemName="DC2.domain.local"" AlertType: 2 0x2 (Communications Alert) Description: "If the Network Interface is an Ethernet Port, the Ethernet Port has transitioned from OK to Error. If the Network Interface is an Ethernet Team, the Ethernet Team has transitioned from Fully Redundant, Degraded Redundancy or Redundancy Lost to Overall Failure, due to a failed team member." EventCategory: 9 0x9 (Network Device) EventID: "2" EventSubCategory: 11 0xb (Ethernet Port) ImpactedDomain: 4 0x4 (System) IndicationIdentifier: "{083DA59C-105A-40FE-A687-FFEF0CFF7CF7}" IndicationTime: "20250205071531.649000+000" OSType: 117 0x75 (Microsoft Windows Server 2016) OSVersion: "10.0.14393" PerceivedSeverity: 6 0x6 (Critical) ProbableCause: 7 0x7 (Communications Subsystem Failure) ProbableCauseDescription: "Network Interface Lost Connectivity" ProviderName: "HP Ethernet" ProviderVersion: "10.60.0.0" RecommendedActions[0]: "View the Ethernet and Ethernet Team Member status in the HPE Network Configuration Utility (NCU) if you are using Windows Server 2008. For Windows Server 2012 users, view the status with Microsoft teaming Management UI..View the System Event Log for additional information." Summary: "The Network interface has lost connectivity." SystemCreationClassName: "HP_WinComputerSystem" SystemFirmwareVersion[0]: "2.40_02-17-2017" SystemFirmwareVersion[1]: "2.40 _02-17-2017" SystemGUID: "38353338-3734-5A43-3237-32393032544C" SystemModel: "ProLiant ML350 Gen9" SystemName: "DC2.domain.local" SystemProductID: "835847-035" SystemSerialNumber: "CZ272902TL" TIME_CREATED: 133832133457107527 0x1db779dc63e5a47 </Data> <Data>For more information, please contact HPE Support.</Data> </EventData> </Event>[/code]

Posted by: drdread - 05 February 2025 09:33:17

Your Windows Server 2022 (DC2.domain.local) on an HPE ProLiant ML350 Gen9 is experiencing intermittent network disconnections that are causing Netlogon DNS failures. The logs suggest that your HP Ethernet 1Gb 4-port 331i Adapter is dropping the network link, which then triggers domain controller failures.

šŸ” Analysis of the Errors

  1. NETLOGON Event 5782 (No DNS Servers Configured)

    • This error happens when the Domain Controller (DC2) fails to register or deregister DNS records due to network loss.
    • Since this happens at the same time as network disconnection, it's a symptom, not the cause.

  2. HP Ethernet Adapter Event 4 (Network Link Down)

    • Indicates that the NIC (Network Interface Card) lost connectivity.
    • This suggests network cable issues, driver problems, or a hardware fault.

  3. HP Ethernet Adapter Event 11 (Network Configured for 1Gbps Full Duplex)

    • This means the adapter reconnects but then disconnects again shortly afterward.
    • The disconnection and reconnection cycle suggests a flapping network connection.

  4. HP Ethernet Event 2 (Transitioned from OK to Error)

    • This error confirms a critical network issue.
    • The system recognizes that the network connection is failing intermittently.
    • The error also suggests possible failure in network teaming (NIC bonding) if you have NIC Teaming configured.

šŸ›  Fixing the Issue Step by Step

1. Check Physical Network Connections

āœ… Inspect the network cable:

  • Make sure the Ethernet cable is properly connected.
  • Try replacing the cable with a new, Cat 6 or Cat 6a cable.

āœ… Check the switch port:

  • If the NIC is connected to a network switch, check if the switch port is stable.
  • Try moving to a different switch port.

āœ… Verify power & cooling on the server:

  • Overheating or power fluctuations can cause NIC instability.

2. Update HP Network Drivers & Firmware

Since this is an HP ProLiant ML350 Gen9, your HP Ethernet 1Gb 4-port 331i Adapter may have an outdated driver or firmware causing the issue.

šŸ”¹ Download and install the latest drivers:

  1. Go to the HPE Support website:
    šŸ‘‰ HPE ProLiant ML350 Gen9 Drivers
  2. Look for "HP Ethernet 1Gb 4-port 331i Adapter" drivers.
  3. Download and install the latest firmware and driver updates.

šŸ”¹ Check your current driver version:

Get-NetAdapter | Select-Object Name,DriverVersion,DriverProvider

If the driver version is outdated, update it using:

Update-Driver -Name "HP Ethernet 1Gb 4-port 331i Adapter"

3. Disable Energy-Efficient Ethernet (EEE)

Energy-Efficient Ethernet (EEE) can cause link instability on HP adapters.

šŸ”¹ Disable it via PowerShell:

Set-NetAdapterAdvancedProperty -Name "HP Ethernet 1Gb 4-port 331i Adapter" -RegistryKeyword "*EEE" -RegistryValue 0

Alternatively:

  1. Go to Device Manager ā†’ Network Adapters.
  2. Find the HP Ethernet 1Gb 4-port 331i Adapter.
  3. Right-click ā†’ Properties ā†’ Advanced Tab.
  4. Locate "Energy-Efficient Ethernet (EEE)" and disable it.

4. Set the NIC to a Fixed Speed (Disable Auto-Negotiation)

Sometimes, auto-negotiation causes instability when it constantly switches between speeds.

šŸ”¹ Force 1Gb Full-Duplex mode:

Set-NetAdapterAdvancedProperty -Name "HP Ethernet 1Gb 4-port 331i Adapter" -RegistryKeyword "*SpeedDuplex" -RegistryValue 4

Alternatively:

  1. Open Device Manager.
  2. Go to Network Adapters ā†’ HP Ethernet Adapter.
  3. Click Properties ā†’ Advanced.
  4. Find "Speed & Duplex" and set it to 1Gbps Full Duplex.

5. Check NIC Teaming (If Enabled)

Your logs mention "Redundancy Lost", suggesting NIC Teaming might be failing.

šŸ”¹ Verify teaming configuration:

Get-NetLbfoTeam

If it's enabled but unstable, consider disabling NIC Teaming and testing with a single NIC:

Remove-NetLbfoTeam -Name "YourTeamName"

Reboot the server and test the connection without teaming.

6. Reset TCP/IP Stack

If networking issues persist, reset TCP/IP:

netsh int ip reset
netsh winsock reset
Restart-Computer

7. Reconfigure DNS Settings

Since this is a Domain Controller, make sure it's using itself as the primary DNS:

  1. Open PowerShell:

    Get-DnsClientServerAddress -InterfaceAlias "Ethernet"

  2. If it's not set to the DCā€™s IP, change it:

    Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses ("127.0.0.1", "YourSecondaryDNS")

  3. Restart NETLOGON & DNS Services:

    Restart-Service Netlogon
Restart-Service DNS

šŸš€ Summary of Fixes

Step Action
1 Check & replace network cables and switch ports
2 Update HP NIC drivers and firmware
3 Disable Energy-Efficient Ethernet (EEE)
4 Set NIC Speed to 1Gb Full Duplex
5 Verify NIC Teaming & Disable if unstable
6 Reset TCP/IP stack
7 Ensure DC uses itself as DNS server

šŸ›  Next Steps

  • Monitor the server after applying these fixes.
  • If issues persist, consider replacing the NIC or testing a PCIe NIC instead of the onboard HP NIC.

This should stabilize your domain controller and prevent random network disconnects. šŸš€ Let me know if you need more help!