Windows cannot obtain the domain controller name for your computer network.
I just noticed that on some newer PCs we are getting an error event in the Application log, every time they are turned on, relating to not being able to find a DC and subsquent error events relating to the failure to find/process start-up scripts.
Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.
The event log shows one error for each start-up script that it fails to run (all of them). Presumably no Computer GPO settings apply either. However, when the user logs on, the user Group Polices and scripts do seem to apply properly.
After a bit of research I found this:
Cannot connect to domain controller and cannot apply Group Policy with Gigabit Ethernet devices
This suggests that the problem is related to the 1Gbit integrated NICs ("Realtek PCI GBE family controller" in our case) fitted to these PCs and the delay/fluctuation in establishing a connection (at 100MBit in our case).
The solution in the article is to disable a Windows feature call Media Sense
How to disable the Media Sensing feature for TCP/IP in Windows
which I am going to investigate.
But I wondered if anyone else has encounted this issue (affecting some PCs with 1Gbit NICs/driver), and how they resolved it?