Fri. May 29, 2020 – fifth Friday this month…

Hot and damp, possibly sunny.

Yesterday was a dog’s breakfast. Depending on where you were in Houston you either got no rain or were dumped on. I got dumped on.

Got my errands done later than I’d have liked, and then went to my client’s house. And the tale of woe continues. More issues with connectivity both on the internal network and externally to the internet.

The AT&T tech was NOT good. He failed to save the account credentials to the DSL modem (which he replaced, as the other one got hit by lightning.) He also used the wrong account and failed to test it with the client’s devices. Seems that AT&T DSL will accept almost anything for account name and password, and tell you it connected to the internet. You can even use the built in tools to ping or traceroute, and they work. But if you launch a browser, you get an AT&T “fix the problems with your connection page” and a wizard that bombs out because of java errors when using Ipads. Iphones and laptops work, but not ipads. Much time was spent trying different combinations of account and password, until finally I got two to match. Before I could do that though, the wizard broke another way. I’d changed the default local lan IP address and gateway for the router to match our internal xxx.xxx.10.xxx scheme. The wizard NEEDS you to have not changed any settings in the box for it to complete. SO MUCH SUCK.

After finally getting the DSL box configured, ports forwarded, rules created, we could finally get out to the internet, but some of the local lan stuff didn’t work… specifically our ipads couldn’t talk to our AV control system. After thinking it was a config issue, and wasting a bunch of time looking at that, I looked at the switch.

Some blinkenlights, not enough blinkenlights. Turns out, the lightning strike on AT&T’s line came in through the copper, smoked the DSL power wart (which shut down the UPS it was plugged into) but not the actual modem, and also smoked the port on the network switch it was connected to. I moved it to another port and got that back up but still no connection to some local hardware. MORE troubleshooting and I discover more dead ports on the network switch. Swap it out for an old HP switch I brought ‘just in case’ and viola, we’re back up. Score one for ‘hoarding’ gear.

Now I’m wondering what gear might have gotten a ‘tickle’ through the network switch and will be failing over the next year…

Moral of the story, lightning strikes have weird consequences. Everything connected to the piece that got hit should be considered suspect. And, AT&T DSL support sucks dead bunnies.

I got home very late, but with a working system behind me. Dinner was more saute’d frozen shrimp, and some instant rice. My wife made it for the kids and I had a plate waiting.

Oh, I took the trash out and realized I’ve got a bunch of rotten potatoes stored. That is going to be my gruesome task today, after swim team practice… cleaning out that mess. Then see if the above ground pool has all the necessary parts, and get sidetracked building same…

But hey, we got an extra Friday this month.

Keep your awareness up, and avoid crowds.

And keep stacking.

n