If your software garbles this newsletter, read this issue at WindowsSecrets.com.
| YOUR NEWSLETTER PREFERENCES Change Delivery address: cpedley.kill-that-computer@blogger.com Alternate address: cgpedley@gmail.com Locale: Canada L3B 5N5 Reader number: 35034-18272 |
|
Windows Secrets Newsletter • Issue 178 • 2008-12-11 • Circulation: over 400,000
|
Table of contents TOP STORY: Microsoft DHCP bugs make Windows lose networking KNOWN ISSUES: A manual approach to reinstalling .NET Framework KNOWN ISSUES 2: Does the glitch in .NET patching put you at risk? WACKY WEB WEEK: Hang on, I've got the perfect song for this! LANGALIST PLUS: Boost performance by killing unneeded processes BEST SOFTWARE: Connect safely over open Wi-Fi networks PC TUNE-UP: Freeware helps to boot the bots off your network PATCH WATCH: Internet Explorer 7 is target of zero-day attack |
You're receiving only our free content. Use the following link to upgrade and get our paid content immediately: |
ADS
|
TOP STORY Microsoft DHCP bugs make Windows lose networking By Scott Spanbauer Numerous perplexed Windows users have discovered that attempting to connect their PCs (especially Vista) to their existing networks or Wi-Fi hotspots results in flaky or nonexistent connections. One reason: a change by Microsoft in Vista's Dynamic Host Control Protocol (DHCP) is causing conflicts with some networking hardware, which can require a Registry edit to fix. The many reports of Vista networking snafus range from the gravest of symptoms — no Internet connectivity at all — to occasional connection drops:
Network-connection problems are infuriating. Finding their source requires a step-by-step approach. Before editing your Registry for the umpteenth time or tossing your router into the trash, run through this network-troubleshooting checklist:
If your connectivity problems aren't resolved by using the points discussed above, you may be suffering from an even more obscure issue. If so, ruling out the tricky configuration problems I describe here may at least help you isolate the real problem and restore your network link.
|
ADS
|
KNOWN ISSUES A manual approach to reinstalling .NET Framework By Dennis O'Reilly The Dec. 4 Top Story in Windows Secrets described how to make sure your system has the Microsoft .NET that's needed by various applications, but doing so sometimes requires a brute-force approach. When it's time to reinstall vital Windows components — or the entire operating system — you'd best have a plan in mind. That's what reader Alan Crawford found out after stumbling through a reinstallation of Windows XP on one of his PCs:
Becky Waring's Dec. 4 parental-control software review (paid content) led reader Rob de Santos to tell us about a new way to use an old, reliable — and free — Internet security service:
Note that in her July 24, 2008, Patch Watch column (paid content), Susan Bradley described how to use the OpenDNS forwarding service to improve the security of routers and Web servers. Speaking of Susan, since her lead story about problems patching Microsoft's .NET Framework appeared on Dec. 4, she's dug up additional information. Although she usually writes for Windows Secrets' paid content, her follow-up on .NET appears today as a free column.
|
KNOWN ISSUES 2 Does the glitch in .NET patching put you at risk? By Susan Bradley People using Windows XP Service Pack 3 may not be offered all the .NET security patches their applications require. However, if none of your PC's programs requires a version of .NET Framework, this problem will have no impact on your system. My Dec. 4 Top Story stated that, due to a bug, Windows XP SP3 users aren't being offered security patches for Microsoft's .NET Framework 3.0. I'm publishing this special column today because several of you asked whether your XP SP3 systems are at risk as a result of this glitch. First I'll give you some background on .NET Framework, and then I'll describe how to tell whether you need to be concerned about the matter. Microsoft created .NET Framework to provide building blocks for applications. .NET is not a component of Windows itself. I strongly recommend that you avoid downloading .NET until you install an application that requires one, at which time the program will likely install the necessary version for you. To determine whether you have any versions of .NET Framework installed on an XP PC, open the Add or Remove Programs applet in Control Panel and look for entries reading Microsoft .NET Framework. If you don't see any such entries, you needn't worry about the update failure. If you do see .NET Framework in the list of currently installed programs, you need to make sure you're receiving all the updates your system requires. When you open the Microsoft Update service on Windows XP, you'll see buttons labeled Express and Custom on the Welcome screen. Click Custom to see three patching categories under Select by Type in the left pane: High Priority; Software, Optional; and Hardware, Optional. Figure 1. Clicking the Custom button on Microsoft Update's Welcome screen shows a list of high-priority and optional updates for your PC. While all three categories can be considered security-related, in reality only the top section lists critical patches. The second section shows optional patches for Windows and your apps; the third lists driver updates. Always install patches listed in the upper section. You can selectively install patches from the Software, Optional section, but I recommend that you never install driver updates directly from the bottom section. In the past, drivers I've downloaded from Microsoft's update service have caused problems. Instead, go to the vendor's own site and download driver updates from there. And remember: if the device isn't causing any problems, refreshing its driver software may be more trouble than it's worth. When I tested several XP SP3 systems, the upper section of the update window — which lists critical security patches — looked much the same as it did on XP SP2 machines. However, SP2 and SP3 showed many differences in the middle section listing optional software updates, including those for .NET Framework. There's a very good reason the updates in the middle section are listed as "optional." Until an application on your system requires .NET Framework to function, don't install any .NET Framework patches. Microsoft's update service will offer systems running XP SP2 an update to .NET Framework 3.0, but machines using XP SP3 won't see it listed among the optional patches. Because of this difference — and the fact that .NET installs can fail, as I discussed last week — I urge you to regularly use a third-party software-update service such as Secunia's free online Software Inspector or the company's standalone program, Personal Software Inspector (obtain PSI from its download page), to check the vulnerability of your PC's software. PSI scans for outdated and vulnerable versions of Sun's Java, Apple's QuickTime, Adobe's Flash and Acrobat, and other common programs that put your system and data at risk if they're not patched. After scanning 20,000 machines in a recent seven-day period, Secunia reported on Dec. 2 that fewer than 2% of the computers were fully patched. By the way, several readers notified me that they had problems with the Secunia software scanner. I'll investigate these issues and report what I find in a future Patch Watch column. Here's the bottom line: don't install any .NET Framework patches listed in Microsoft Update's "Software, Optional" section unless you're sure you have the corresponding .NET Framework installed on your system. Any application requiring a specific .NET Framework, such as Intuit's Quickbooks accounting program, will install the necessary version automatically. Once the Framework is on your machine, install any offered security patches for it, but be prepared for potential installation glitches. Aaron Stebner's .NET Framework cleanup tool (download page) can help you out if a .NET update gets stuck. You may have to uninstall that version of .NET and reinstall it, as described by Alan Crawford in this week's Known Issues column.
|
WACKY WEB WEEK Hang on, I've got the perfect song for this!
|
ADS
|
PERMALINKS Use these permalinks to share info with friends We love it when you include the links shown below in e-mails to your friends. This is better than forwarding your copy of our e-mail newsletter. (When our newsletter is forwarded, some recipients click "report as spam" and corporate filters start blocking our e-mails.) The following link includes all articles this week: http://WindowsSecrets.com/comp/081211 Free content posted on Dec. 11, 2008:
You get all of the following in our paid content:
Thanks in advance for your support! |
YOUR SUBSCRIPTION The Windows Secrets Newsletter is published weekly on the 1st through 4th Thursdays of each month, plus occasional news updates. We skip an issue on the 5th Thursday of any month, the week of Thanksgiving, and the last two weeks of August and December. Windows Secrets resulted from the merger of several publications: Brian's Buzz on Windows and Woody's Windows Watch in 2004, the LangaList in 2006, and the Support Alert Newsletter in 2008. Publisher: WindowsSecrets.com LLC, Attn: #120 Editor, 1700 7th Ave., Suite 116, Seattle, WA 98101-1323 USA. Vendors, please send no unsolicited packages to this address (readers' letters are fine). Editorial Director: Brian Livingston. Senior Editor: Ian Richards. Editor-at-Large: Fred Langa. Technical Editor: Dennis O'Reilly. Associate Editors: Scott Dunn, Stuart J. Johnston. Program Director: Tony Johnston. Program Manager: Ryan Biesemeyer. Web Developer: Damian Wadley. Editorial Assistant: Katy Abby. Copyeditor: Roberta Scholz. Chief Marketing Officer: Jake Ludington. Contributing Editors: Susan Bradley, Mark Joseph Edwards, Woody Leonhard, Ryan Russell, Scott Spanbauer, Becky Waring. Trademarks: Microsoft and Windows are registered trademarks of Microsoft Corporation. The Windows Secrets series of books is published by Wiley Publishing Inc. The Windows Secrets Newsletter, WindowsSecrets.com, Support Alert, LangaList, LangaList Plus, WinFind, Security Baseline, Patch Watch, Perimeter Scan, Wacky Web Week, the Logo Design (W, S or road, and Star), and the slogan Everything Microsoft Forgot to Mention all are trademarks and service marks of WindowsSecrets.com LLC. All other marks are the trademarks or service marks of their respective owners. YOUR SUBSCRIPTION PREFERENCES (change your preferences): Delivery address: cpedley.kill-that-computer@blogger.com Alternate address: cgpedley@gmail.com Country: Canada ZIP or postal code: L3B 5N5 Reader number: 35034-18272 Bounce count: 0 Your bounce count is the number of times your server has bounced a newsletter back to us since the last time you visited your preferences page. We cannot send newsletters to you after your bounce count reaches 3, due to ISP policies. If your bounce count is higher than 0 or blank, please visit your preferences page. This automatically resets your bounce count to 0. To change your preferences: Please visit your preferences page. To access all past issues: Please visit our past issues page. To upgrade your free subscription to paid: Please visit our upgrade page. To resend a missed newsletter to yourself: If your mail server filtered out a newsletter, you can resend the current week's issue to yourself. To do so, visit your preferences page and use the Resend link. To get subscription help by e-mail (fastest method): Visit our contact page. Subscription help by facsimile: 206-282-6312 (fax). Emergency subscription help by phone: 206-282-2536 (24 hours). HOW TO SUBSCRIBE: Anyone may subscribe to this newsletter by visiting our free signup page. WE GUARANTEE YOUR PRIVACY: 1. We will never sell, rent, or give away your address to any outside party, ever. 2. We will never send you any unrequested e-mail, besides newsletter updates. 3. All unsubscribe requests are honored immediately, period. Privacy policy HOW TO UNSUBSCRIBE: To unsubscribe cpedley.kill-that-computer@blogger.com from the Windows Secrets Newsletter,
|
No comments:
Post a Comment
Thanks for understanding that we need to prevent the nasties.