this post was submitted on 29 Dec 2023
22 points (86.7% liked)
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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I know this is stupid to ask but can you test setting up servers fresh from a .iso? No template, no domain join, no nothing that would create any predefined settings. If the issue doesnt persist, maybe there is a legacy gpo or something that forces it for domain recognition before allowing other network traffic. Or something completely different but we gotta corner the problem in with troubleshooting.
And also maybe create a script that's being fired at bootup. The script could write the timecode and the "ipconfig /all" and "route print" into a textfile every few miliseconds.
This would create large logfiles but might help. Since if you are even uncapable of pinging local adresses with IPv4 adresses, maybe the network stack just simply doesn't load fast enough.
Also some additional info might help with cornering it in such as:
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!
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
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.
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?
:D
I knoooow. That's what i feared most. Luckily i lacked the balls to cross the final frontier 😁
This comment needs to come up in a search.
Thought I edited my post for this reason. Gotta do it again 😁
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!