Also it might be that 2 & 4 are flat dead. They've probably been running for a very, very long time. It "suddenly" happened because they are old.
A third party security audit is the IT equivalent of a colonoscopy. It's long, intrusive, very uncomfortable, and when it's done, you'll have seen things you really didn't want to see, and you'll never forget that you've had one.
Also it might be that 2 & 4 are flat dead. They've probably been running for a very, very long time. It "suddenly" happened because they are old.
This is the sixth time we have created a thread about it... and we have become exceedingly efficient at it.
Probably not ALL of them, but possibly one failed. I think it's more of a misconfiguration of the switches than an actual hardware failure.
He did say they're in a warehouse, so they could have succumbed the environment. Most warehouses I've been in have a lot of soot if they use propane powered forklifts, and a lot of dust in general.
A third party security audit is the IT equivalent of a colonoscopy. It's long, intrusive, very uncomfortable, and when it's done, you'll have seen things you really didn't want to see, and you'll never forget that you've had one.
This is the sixth time we have created a thread about it... and we have become exceedingly efficient at it.
I am fairly certain these are in environmental cabinets inside the offices.... but I could be wrong... I have never been to the site personally.
I would think that the problem would not have gone away for 2 weeks if that was the case.... I could be wrong though .... would not be the first time ...Also it might be that they are flat dead. They've probably been running for a very, very long time. It "suddenly" happened because they are old.![]()
btw you can send your invoices to
Bastardized Systems
attn: Local BOFH
666 dev null st
Long Island, NY 11756
![]()
Depends on how they handle packetsWe had a switch where it would work fine once we restarted it and for about a week and then tank, turns out it wasn't handling collisions properly and crapped itself. Restarting it started the process all over again.
This one is on me
edit: also, good luck
This is the sixth time we have created a thread about it... and we have become exceedingly efficient at it.
thanks, I will be sure to update you guys on what we find.
thanks
Thomas