Lamb0 and Kdawgca,
I'm reasonably sure that an automatic firmware update was the cause of the surprise router reset on 9/22, which was followed by a return to default settings and a router reboot. Verizon "probably" had nothing to do with it. Below is what preceded the reset....
The day before the event, I was tweaking the router's settings on it's webpage. I saw the firmware update feature and noticed that the router's firmware version was more recent than the latest ActionTec version listed on the page. I've seen manufacturers avoid posting their most current update for the general public, while at the same time incorporating it in a very recently manufactured device. Lo and behold, the router's label showed the latest update, while the page showed a previous one as the most recent one. I was confused, so I mistakenly "forced" the update to the previous version. In addition, I changed the method of incorporating updates, from not checking for them to checking automatically but taking no action. In this case, an email was to be sent to me. I received no email at any point.
It's clear that I should not have reverted back to a previous update version, although everything worked the same with either version. At the time of the event, the router must have checked the ActionTec website, found the latest firmware version and updated it. Checking the router website after the event, I found that the latest version is indeed being used as it was before I intervened. I also recall that each time I manually reset the router, all of my custom settings were lost and the default settings took their place. I didn't notice the ability to save my custom settings to a text file, until recently. In the future, I will save to a file before I do a reset. A reset is sometimes the only way to return a non-responsive router to working order. But the end result is the same as when the router is first attached to a pc system.....the use of it's default settings. Naturally, I disabled the "automatic update check" feature, allowing me to see whether they posted an update and if so, choosing the time to install the update when it will have the least amount of impact on me. In this way, I won't be surprised!
By the way, my initial call to Verizon tech. support was to get a solution to a problem that has plagued me since my July 3rd FiOS installation, but not during the time I was using a DSL modem with the Linksys router. When I logoff, restart, return from hibernate or from a shut down, the laptop's wireless adapter detects the router's broadcasting of my network within seconds. But when I go to sleep mode via the power button or via the Start Menu and return to the desktop, the acquisition of my network connection is delayed by almost a minute. It finds my network, but can't seem to connect to it quickly. Even when I manually force the connection, I still had to wait.
I tried many things with the Verizon tech., and nothing worked. Then I started thinking of the many settings for the laptop's wireless adapter, and came upon something I'd seen countless times. In the Power Management tab was this check box "Allow the computer to turn off this device to save power." I've always kept it unchecked, because I usually use my laptop in bed with the battery pack removed to enhance it's lifespan. As illogical as it seemed to me at the time, I checked the box and went into sleep mode. When I returned to the desktop, the laptop connected to the network within 1 or 2 seconds. Being a skeptic, I repeated the test a few more times and the result was the same every time. THAT issue has been resolved, although I don't know why allowing the wireless adapter to be turned off would be the solution. I'm thinking that this feature never entered the mind of the tech., since he didn't see the properties page of the wireless adapter, as I did.
This mystery seems to be solved.....