Another (Wasted) day…another dollar. Its not unheard of for a typical IT person to rant about dealing with printers. It seems they’re constantly the bane of any admin; not printing, needing special treatment, buggy drivers, buggy settings, etc. I often think I’m immune to a majority of the issues; I’ve been through EVERYTHING, fixed it all, and hey if I can get 1960s teletype machines working, I can get a friggin modern printer working. Well today, I was put back in my place…
Continue reading “Fiery Print Server ignores DHCP/DNS Changes with Papercut”3 Funerals and a Crappy Breakfast – My 2023
This started out just being titled 3 Funerals, but this awful breakfast on New Years eve just seemed appropriate for the finale of 2023.
Continue reading “3 Funerals and a Crappy Breakfast – My 2023”DIY Chamberlain/Liftmaster Garage MyQ Door Opener with Meross Smart Garage door Remote Module
As part of my home automation fun, I had a MyQ module paired to my garage door opener, which “wifi enabled” the opener. Once that was set up, I leveraged a plugin in Homebridge to talk to the MyQ API and present the door in Apple Homekit.
Continue reading “DIY Chamberlain/Liftmaster Garage MyQ Door Opener with Meross Smart Garage door Remote Module”Life
“If you’re going through hell, keep going.”
— Winston Churchill
RIP Jedi Jim Fisher, AJ3DI
There’s been a disturbance in the force. Since my last post, my world has been rocked a bit.
Continue reading “RIP Jedi Jim Fisher, AJ3DI”At&t 513 Terminal, Part II
In the first post I mentioned the dag was missing from the monitor, so while the tube is out, lets give the monitor some attention…
Continue reading “At&t 513 Terminal, Part II”At&t Model 513 Terminal, or Teletype 56D, or…
Talk about an identity crisis! I recently stopped by the swap meet at System Source, a computer museum just outside of Baltimore, Maryland, where I picked up this eighties masterpiece of a terminal. This…style terminal I believe is known by many monikers. This actual unit is labeled an At&t “513” on the front, and “Teletype 56D” on the back. (At&t bought Teletype Corp and often branded some of their final products with At&t nomenclature.) This unit was likely paired to an At&t Definity PBX, and simliar units could also be At&t 4425 as well as many other models (likely only minor firmware tweaks between them).
Posted on it was a sign that basically mentioned it was a “barn find”, and as such, no guarantees on it working, or ever working. As I’m a glutton for punishment, naturally I bought it. (I know the seller and he gave me a good deal on it).
Let’s see what’s inside…
Continue reading “At&t Model 513 Terminal, or Teletype 56D, or…”Sharing Printers – Windows 10 22H2 – Error 0x0000709
Once again, a fun little doozy with rabbit holes leading in all the wrong directions. A typical 5 minute thing turns into a 4 hour hair-pulling exercise! Tried to share 2 printers from a Windows 10 computer to another Windows 10 computer, and the other Windows 10 computer could not access them; they showed up as shared printers, but I got the dreaded 0x000000709 (note number of zeros may be off) error whenever I tried to connect to the printer.
Doing some searching leads you to believe this was due to a security update that was pushed some time ago to mitigate Print Nightmare, or perhaps a new issue having to do with RPC in Windows 11. (Why so many Windows 11 results when I clearly put Windows 10 in the search baffles me too). The real answer? Neither (ish).
Continue reading “Sharing Printers – Windows 10 22H2 – Error 0x0000709”Whirlwind
Figured I’d put up a personal blog post, as I think one is due.
To say the last few weeks have been a whirlwind of emotions amongst other things, would certainly be an understatement. While things could have been worse, it’s just been a whirlwind of stuff going on, starting with a trip, continuing with a funeral, and other “life” things.
Continue reading “Whirlwind”Firefox – Gmail/Google Sites lock up/fail to load
Figured I’d share this out so I can find it faster in the future if I need to switch PCs around. On the latest versions of Firefox, Google services seem to run into an issue where if you open things like Gmail, it’ll work for a while, then just…stop responding, but ONLY Googles sites stop responding.
Apparently it has to do with a setting in Firefox that’s handling a new TLS 1.3 feature (stuff thats a bit over my head), so I’ll simply share the article with the fix for it if anyone is running into this issue:
Can’t connect to Google since Firefox 100 | Firefox Support Forum | Mozilla Support
Long story short, go into Firefox config by browsing to about:config (click yes to the prompts), then search for security.tls.enable_0rtt_data, which will be set as TRUE. Set it to false using the ying-yang looking icon to the right, and then close/reopen Firefox. Gmail and other Google sites should now work as expected.