Give us the cheat codes to your industry/place of work!

  • Skyline969@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    I work in the magical world of ISPs. If you’re having an internet issue, reboot your router and/or modem before calling in. It may not seem like much to you, but many background processes happen when you do so. This can be useful to troubleshoot where the issue lies. There’s a reason why techs will make you do so when calling in. And yes, they can tell on their end if and when you do so. So don’t bullshit them by saying you already did it if you didn’t.

    • OsrsNeedsF2P@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      I feel like some people “lie” about rebooting their modem simply because they don’t know how to reboot it

      • Skyline969@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 months ago
        1. Unplug the power
        2. Wait ~30 seconds, just to ensure it’s good and off
        3. Plug it back in

        Fortunately there are no commands to enter or buttons to click. They’re designed to handle losing power.

    • Brown5500@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      Yeah, but we all know that no matter how many times that I have already done, tech support won’t talk to me until we do it again together

      • Skyline969@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 months ago

        If I had a nickel for every time a full power cycle fixed it all, I’d be rich. However, if you did power cycle before and call in again, often it’s an issue that needs deeper investigation. In that case, the tech can likely watch the process of your equipment coming online in realtime to see where the issue is happening. Network entry, authentication, package application, DHCP, it can often be monitored as it’s happening. A reboot while on the phone starts the process right from the beginning so it can be monitored to determine what happens immediately and what happens after it sits for a while.

      • stoy@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        IT guy here, it is fairly common to make a change in the system™, and need to reboot the device for the change to take effect.

      • KISSmyOSFeddit@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        I work in tech support. An error I haven’t seen doesn’t exist. So yes, I’m going to re-trace the trouble-shooting steps with you.
        90% of the people who call in haven’t done it, but claim they did. Because they think I have a magic tech wand that can find and fix all problems, and that I just make them go through the motions because I’m lazy.