Network connection (domain profile) domain connection shows as “unauthenticated”

We experience inability to access local owa site, from time to time accessing domain file resources was experiencing outage.

Among a lot articles/blog posts we followed the article https://serverfault.com/questions/413052/domain-connection-shows-as-unauthenticated

Overall, we thoroughly tested:

• DHCP leases and reservations on DC (running the dhcp role), no multiple entries for the offending workstations
• Remove from Domain and join again.
• IPV6 uncheck and recheck
• Winsock reset using:
  • Netsh winsock reset catalog
  • netsh int ipv4 reset reset.log
  • netsh int ipv6 reset reset.log
  • Restart
• Rename computer name
• Antivirus disabled
• Remove the network adapters from Device Manager, then Scan for new hardware to re-install the NICs.
• Restore your Windows Firewall Profiles to defaults: Run wf.msc and click “Restore Default Policy”

All the above were tested as standalone and combined.

The workstations behavior was rather strange as:

1. When you switched to static ip, everything seems to work.
2. WORKSTATION responded providing domain communication needed ports: 135, 139, 445.

But after a restart everything was back to “not normal”.

What was it?

The issue appeared on a Realtek GbE Adapter on a Windows 10 workstation.

This workstation was originally a Windows 7 Pro having no issues with jumbo frames

Was upgraded to Windows 10 Pro, jumbo frames were not a problem for a long time.

But the issue appeared right after the Windows 10 upgrade to latest built (2004).

After turning jumbo frames option to disabled, the workstation returned to normal operation.

Not the best, but it works! We will come back to this upon updates on Windows 10 appear next month.