When I arrived on duty this morning (i.e., got up and went to check my email), I discovered that LUGGABLE was disconnected from my wifi net. First thing I did a repair and opened up wifi icon. My faithful OREGON wasn't there. Hmm. I wnt to OLDLAP and it do was disconnected. Now I know Comcast is in their Mother's Day freeze so it's unlikely that it was them. SO I went and restarted the linksys wap.
I checked my UDP forwards that Azureus was griping about while I was there. They all were all their as I thought. udp 5000 – 5099 maps to 100, 5100 – 5199 maps to 101, you get the idea.
WAP restarts and I see the blinking lights on the WAP, the WAN, and the cable modem. SO I return OLDLAP is now connected. AND now to LUGGABLE, it too has reconnected.
Sort of. Look around and everything seems OK but it's running like mud. Lookout seems to be taking all the cycles. Blue Frog is offline and won't come back. Azureus is griping about UDP settings. No choice reboot. Argh! Reboot takes for ever because nothing is shutting down. Everything has to be closed out. Rebooted.
All coming up OK. Except blue frog. It takes a runtime error and says call hq. Call hq and they are offline for maintenance. Good service blue frog! There's a strike against them. Argh.
Everything else seems RTN (returned to normal) but how can you ever know with windows.
Takeaway: I would like to find a Flight Data Recorder for the PC. Something as trivial as ping a know good site (i.e., yahoo, google) say every 15 minutes and record the results. It runs routinely and logs when external connectivity is lost. If I had that on all my boxes, I might be able to trace the culprit. By know precisely when connectivity was lost, you'd at least have a fact. Now all I know is that it dies between bedtime and wakeup. Arghh, arghh!
Takeaway: Blug Frog still down.
Comments? Ideas?
Reinke Faces Life 