• @[email protected]
      link
      fedilink
      151 year ago

      Yeah, wireless printers can eat my refuse. I just spent a fruitless hour fixing my neighbours printer. Their crime? Restarting the router spooked the printer connection to the network. Shit system integration and poor documentation make this job needlessly painful.

      • @[email protected]
        link
        fedilink
        91 year ago

        I have a wireless Canon. Has worked flawlessly for years. Never had any issues. Replace the ink every now and again and it keeps chugging.

        • @[email protected]
          link
          fedilink
          51 year ago

          I believe you. We can make wireless stuff work if we really want to. My Bluetooth headset links with the phone perfectly every time. Attempt the same trick with Teams on a PC, forget about it. Wifi generally seems quite solid these days but if I get a choice I will use ethernet. It would have to be really bad to warrant going back to wired headphones but with a printer, meh. I don’t walk around my house with it and run a few copies from the kitchen.

        • Dark Arc
          link
          fedilink
          English
          31 year ago

          Same experience with a brother printer connected via WiFi.

          • @[email protected]
            link
            fedilink
            11 year ago

            Partner hasn’t had issues either actually. Normally I’m in full agreeance about printers, and wifi printers. But this one has been solid.

    • @[email protected]
      link
      fedilink
      51 year ago

      Eh, for SOHO users with a clear 2.4GHz space, probably works well enough. But for us IT people… We Know

    • @[email protected]
      link
      fedilink
      21 year ago

      If anybody has issues with your printers wireless connection constantly dropping. Try setting a static IP address for the printers wifi connection. I’ve fixed 3 wireless printers by doing this. My wife’s work bought her a new wireless laser printer 2 years ago. Thing would lose its ip address every time it went into sleep mode, and it would only reacquire an IP address about half the time. Changed it to a static IP address, and now it always just works.