Windows Live OneCare Tweak
Working for a Microsoft Partner provides me with the opportunity to run Microsoft products well before they hit the street. Often times I do that. That was the case with Windows Live OneCare. I started running it quite a while ago and it seemed to be a good product for just about all my Windows Desktop Security needs. It wasn’t until I signed up for the full license that I began to run into some interesting issues. One of which was that my Microsoft-based VPN client began to fail, which was quite annoying.
Anyhow, after an afternoon of googling about it and troubleshooting to try to figure out what was causing the issue, I finally boiled it down to either the Windows Firewall or OneCare. Well, they are one in the same when you are running OneCare. Long story short, I found and fixed the problem, which was that by default Microsoft disables the port for the connection that Microsoft’s own VPN Client needs to connect. Why? I don’t know. Ask Bill Gates. What I do know is how to change the setting, so I thought I would share that here.
1) Find the OneCare Icon in the System Tray. It looks like this, but could be Green, Yellow or Red.
![]()
2) Click on View or Change Settings

3) Select the Firewall Tab

4) Select the Advanced settings button

5) Select the Ports and Protocols Tab, scroll all the way down in the list and make sure that VPN - General Routing Encapsulation (GRE) is selected.

6) Click OK, then OK again, then close OneCare.
Test your VPN and it should connect just fine. No more cryptic Error 721 or Error 800 messages. Just a good smooth connection to your office so that you can put in those Bill Lumbergh weekend hours from the comfort of your own couch. Happy TPS Reporting. Don’t forget the cover sheet!






