M
Mogaba
Hello,
I encountered some weird behaviour with the network in Windows Server 2016. The server model is ASUS RS700-E9-RS4 with Intel I350 (linked) and X550 gigabit network adapters.
I made a fresh installation of Windows Server 2016 Standard and joined the server to the domain. After every boot, there were 3 errors in the event viewer:
1) Error 1129: the processing of Group Policy failed because of lack of network connectivity to a domain controller.
The symptoms are identical to those in the article:
https://support.microsoft.com/en-us...-group-policy-event-1129-is-logged-when-you-s
I've been able to fix this by increasing policy processing wait time to 60s.
2) Error 10154: the WinRM service failed to create the following SPNs.
This was fixed by changing the startup type of the WinRM service from "Automatic" to "Automatic (Delayed Start)".
3) Error 1069: cluster resource "IP Address" failed (after I set up a failover cluster)
This was also fixed by changing the Cluster service startup type to "Delayed start".
There is also a warning on each boot (right after Kernel-Processor-Power messages):
ID: 27
Source: e1rexpress
"Intel(R) I350 Gigabit Network Connection
Network link is disconnected."
What I've tried before finally fixing the errors (none of it helped):
- installing latest drivers for the NIC;
- disabling IPv6;
- disabling power saving mode in the NIC settings;
- disabling all NICs except the one linked;
- disabling PXE in BIOS;
- switching to Intel X550 NIC;
- rejoining the domain;
- reinstalling Windows.
I found this related thread but I don't use teaming:
NIC Teaming on Server 2016 delays network availability on Domain Controllers causing problems with Active Directory
We have a bunch of Win2008 R2 servers working fine so I don't think this problem has anything to do with our domain or network structure.
I also tested Windows 2016 in our virtual environment (Proxmox) and it didn't show any errors so I guess this problem has something to do with Intel adapters?
Although all seems OK now (except the warning about network link disconnection), I'm still concerned about facing more issues when the server goes to production.
Any suggestions?
Continue reading...
I encountered some weird behaviour with the network in Windows Server 2016. The server model is ASUS RS700-E9-RS4 with Intel I350 (linked) and X550 gigabit network adapters.
I made a fresh installation of Windows Server 2016 Standard and joined the server to the domain. After every boot, there were 3 errors in the event viewer:
1) Error 1129: the processing of Group Policy failed because of lack of network connectivity to a domain controller.
The symptoms are identical to those in the article:
https://support.microsoft.com/en-us...-group-policy-event-1129-is-logged-when-you-s
I've been able to fix this by increasing policy processing wait time to 60s.
2) Error 10154: the WinRM service failed to create the following SPNs.
This was fixed by changing the startup type of the WinRM service from "Automatic" to "Automatic (Delayed Start)".
3) Error 1069: cluster resource "IP Address" failed (after I set up a failover cluster)
This was also fixed by changing the Cluster service startup type to "Delayed start".
There is also a warning on each boot (right after Kernel-Processor-Power messages):
ID: 27
Source: e1rexpress
"Intel(R) I350 Gigabit Network Connection
Network link is disconnected."
What I've tried before finally fixing the errors (none of it helped):
- installing latest drivers for the NIC;
- disabling IPv6;
- disabling power saving mode in the NIC settings;
- disabling all NICs except the one linked;
- disabling PXE in BIOS;
- switching to Intel X550 NIC;
- rejoining the domain;
- reinstalling Windows.
I found this related thread but I don't use teaming:
NIC Teaming on Server 2016 delays network availability on Domain Controllers causing problems with Active Directory
We have a bunch of Win2008 R2 servers working fine so I don't think this problem has anything to do with our domain or network structure.
I also tested Windows 2016 in our virtual environment (Proxmox) and it didn't show any errors so I guess this problem has something to do with Intel adapters?
Although all seems OK now (except the warning about network link disconnection), I'm still concerned about facing more issues when the server goes to production.
Any suggestions?
Continue reading...