*Source: Microsoft Watch (
http://www.microsoft-watch.com/conte...9TX1K0000535)*
_______
In the last post, I explained about a switch to Windows Live OneCare (
http://www.microsoft-watch.com/conte...ws_update.html) after Microsoft May updates hosed Grisoft AVG 7.5. This morning, OneCare is freaking me out.
Earlier in the morning, I successfully connected to my corporate network using Cisco VPN. But just a little bit ago, the software repeatedly failed to connect. I noticed the connection failure, with an error "442," would occur when OneCare changed the status of the connection.
Apparently, OneCare doesn't think too much of my corporate connection and switches status from "automatic" to "restricted" during VPN connection. This has been the case since I installed OneCare last week. So, why the futz now?
More...