The IT Blame Hierarchy 1. It's DNS. 2. It's the Network. 3. It's the Firewall. 4. (If all else fails) It's Storage.
@SharpNetwork I don’t see layer 8 in there… are you sure there is actually any problem at all? (Or it’s DNS)
@SharpNetwork Who are we kidding. 1. It's Windows and needs a reboot. User: I'll lose my tabs.
@SharpNetwork It's the Lennox bias from starlink according to a CCIE
@SharpNetwork It’s always DNS
@SharpNetwork Most of the time i see this: 1. It's just a glitch 2. We were hacked (but we dit not leak any data) 3. It was an intern's fault 4. It turned out to be DNS
@SharpNetwork “Can we just disable x security tool and try?” 😑
@SharpNetwork Uh, you forgot it's Security's fault.
@SharpNetwork 5. (If you manage Apple devices) it needs a device or app update.
@SharpNetwork The intern. Don’t forget the intern. 😉
@SharpNetwork Network is always #1 on the list. Always gotta prove them wrong
@SharpNetwork 1. it’s #CrowdStrike 2. It’s GPO 3. My attack script wasn’t suppose to run in PROD!
@SharpNetwork dns is the network, firewall is the network. storage, can't do that without network? :D
@SharpNetwork Lol, I just used in a sidebar conversation while on a call at work last week...
@SharpNetwork It's never the network, and when it is we blame dns till we fix it 🤭
@SharpNetwork Gotta have Active Directory on thr list 😆
@SharpNetwork This week already it was always DNS while I always blamed firs the Firewall then the network followed by some cursed words towards the local servers DNS cache 🙄
@SharpNetwork Going to say something controversial. All compute NICs and Network L2, L3, and SVI should auto default to MTU 9000. Period! If you are still set to 1500 MTU you are living in the past. There is no excuse.
@SharpNetwork Mamaging FW and Netowkr both in cloud, makes me a direct target evertime therr is P1 and P2. Worst luck? Lol
@SharpNetwork In my experience, 99% of the time, the real issue is sitting right in front of the screen! 😅
