

It’s not just you (as is with all these kinds of questions). It’s an observable trend. As complexity rises, potential for errors rise.
Homo Homini Lupus Est


It’s not just you (as is with all these kinds of questions). It’s an observable trend. As complexity rises, potential for errors rise.


Thanks, but… Wow, who would’ve thought it’s the other major contenders.


See my update on the problem. Already solved. Thanks for trying anyway, mate!


Already solved, thanks anyway man!


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


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


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.


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!


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!


deleted by creator


deleted by creator


Will do the bootup-script! Good idea.
The wireless were on a different VLAN. Also changed that for troubleshooting. Now everything is the same and got the same firewall-rules. Which i also completely disabled. And no, DHCP is the same for all too.


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!


Will investigate. Thanks for the hint.


Oh, it’s not INTERNET they don’t get, they get no net at all. It’s “unknown network” for a long time until they finally display “” and only then I can access the LAN. From there on, everything works fine.


deleted by creator
That too. But also proportional to growing complexity. More complex things to manage makes more room for mistakes in management. With maybe even the epitome being “ah fuck it”