12
jonii
6y

Back when I started my career (12 months ago lol), I was in IT support. Having to deal with people who have hard times locating and reading off a sticker, let alone telling me their IP adress, only to realize it's the whole store that's offline, not only their PC (gosh do they ever talk with each other). So I decided to code a small tool that shows your hostname and IP adress, and pings the router, firewall and Google DNS. Aaand just in case the number for the IT hotline. Plan was that we could just tell them to double-click on that one icon on their desktop and read out what it says. We deployed it and I was happily waiting for it's time to shine (still a trainee I was also kinda proud of it), but when the network engineer found out, he wasn't happy about it at all. He was afraid too many people would open that new tool without us telling them to do so and/or forget to close it, producing a number of pings to the router, firewall and google. He went on about Google maybe blocking our IP if we produce too many pings and so on.
In my opinion he was kinda overreacting, but he wasn't that wrong and is a nice guy and responsible for our network, so we recalled the tool and never actually used it.

Comments
  • 8
    Really?
    A few pings and he thinks google will block you? Cmon bruh.

    Thats retarded. Lets just stop and think about how many 'GET /' requests google serves a day.

    What you planned to do was literally a drop in the ocean.
  • 3
    @D--M yep.. I even put a 5sec delay in it, so the ping wouldn't be continuous. But he was like "what if all our clients have that tool open!" (a few hundred)

    I think he was just upset, that he wasn't informed before deployment or we didn't talk to him about it, since it was a network-ish topic.
Add Comment