Sysadmin

7467 readers

2 users here now

A community dedicated to the profession of IT Systems Administration

No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
[email protected]
[email protected]
[email protected]
[email protected]

founded 1 year ago

MODERATORS

[email protected]

Weird problem driving me crazy (Win, Domain, Network) (lemmy.zip)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

20 comments fedilink hide all child comments

[Update:Solution]

It was my router which set STP on by default. Switching it off (in smaller networks) or using RSTP made the delays go away.

[/Update]

Hóla!

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

[–] [email protected] 9 points 7 months ago (2 children)

NVM, I finally found the culprit by accident…my switch enabled STP (slow) by default. Switching it off or using RSTP fixed the delays. Thanks for helping anyway man!

[–] [email protected] 4 points 7 months ago (1 children)

Holy moly Networking Class... I'm getting flashbacks to my time when in the Simulated Cisco Environment we tried the SPT out and yes you are right. It takes a short but nonetheless weird amount of time for it to timeout.

Thanks for giving me the updates. If I or somebody else ever has similar symptoms maybe they will find this thread :D

I gotta say I think I would never had targeted SPT as the culprit. Though to be fair I only use dumb switches in my homelab and at the corp, the Networking department gatekeeps the nice stuff a bit :3

Anyway, I'm happy you found out and were able to fix it. <3

[–] [email protected] 4 points 7 months ago (1 children)

If I'd tell you that I was trying to fix that shit for over a year now and gave up 4 times already....

Yeah totally. Would've never thought the culprit there. But it started to make total sense. Only lan. Only physical. Even switching the nic off and on again. But not in a vm. There was only one denominator here. The effing switch.

Well, if you use pro-stuff at home, better be a pro lol. Thanks anyway man. It nudged me in right direction.

At this point I was willing to try sacrificing sheep or reading a manual.

[–] [email protected] 3 points 7 months ago (1 children)

You were ready for reading the manual. Darn good that you've made it without passing that line. Once you pass it you never come back to being sane again, you know?

[–] [email protected] 3 points 7 months ago

I knoooow. That's what i feared most. Luckily i lacked the balls to cross the final frontier 😁

[–] [email protected] 3 points 7 months ago (1 children)

This comment needs to come up in a search.

[–] [email protected] 1 points 7 months ago

Thought I edited my post for this reason. Gotta do it again 😁