For a long time I've got this horribly annoying problem: Upon bootup, ANY domain-machine that is using LAN (no probs with wireless) has an idle-time with "there's no network!" of about 1-2mins until they discovered the network. BUT only windows-machines. Linux boxes get net instantly. Also on LAN.

Setup: 2 Domaincontrollers, Server2019. Both are DNS, one is DHCP and NPS for WIFI. All machines have fixed IPs, the DHCP is just for wireless clients.

I have tried everything I could think of, like NIC-Drivers, OpenDHCP, temporarily changed the switch from a managed one to a dumb one, changed the NIC in the server, let only one DC be alive at a time, rejoined the domain, the usual sfc/dism-approach and whatnot.

I asked once on reddit, but everyone just told me "that's DHCP!", yet it's (seemingly at least) not. All have fixed IPs, but using dhcp doesn't change a thing.

So I'm clueless again, hoping for some nerd that's nerdier than me to have an idea :)

you are viewing a single comment's thread
view the rest of the comments

[–] Dyskolos@lemmy.zip 3 points 2 years ago* (last edited 2 years ago)

no. Also physical machines.
hypervisor is proxmox. But there's only linux-machines which all have no problems.
yes also bare metal servers. They both are.
the forest is old (2003 or so) and migrated a lot. I created it. I already tried disabling all gpos and returning to default.

Will try the wiresharking approach. Good hint. Didn't even think of it. The bootup-log-script is also a good idea. Will do that. Thanks man!