So glad it’s Friday.. what a freaking week this was

Posted by TechieJay23@reddit | talesfromtechsupport | View on Reddit | 10 comments

Okay guys, it’s Friday, time for our end of the week jobs that left us speechless lol.

So this time I’m working on a printer. Regional tech says it’s getting an APIPA IP address. No problem, I get on site thinking it’ll be quick. Check the data drop, activated and good to go. Patch cable’s fine. I can get out to the internet, easy. Printer isn’t on our DHCP reservation list, so I go ahead and add it. Reboot the printer… still getting that APIPA address 🤔

I check and recheck everything. Swap patch cables on the closet side. I knew it was on the data VLAN but still wanted to be sure. None of it made sense. 40 minutes later. finally, it pulls an assigned IP. Like wtf 😭

Mind you, we’re in the middle of switch upgrades across every school in the district, moving from Avaya to Extreme. This school was just cut over recently. New gear, 5520 switch, auto-sense enabled on data ports. I know it can take a few minutes to fully connect, but not over 30+ minutes. Data jack side already tested and confirmed.

So what’s left? The infrastructure between the jack and the switch. Definitely not Cat 6… probably Cat 5. Yep, most likely Cat 5 🫠 And that would explain a lot, especially with newer switches and devices trying to auto-negotiate at higher speeds.

What are your thoughts? I’ve never seen anything like that before. A simple printer job turned into a 40-minute head-scratcher. Normally this is a 15–20 min fix tops.