Has your Windows operating system ever bugged you with this error message:

And oh no, not just that one! I'm talking about any one of these pesky messages:

• Cannot delete file: Access is denied.

• There has been a sharing violation.

• The source or destination file may be in use.

• The file is in use by another program or user.

• Make sure the disk is not full or write protected and that the file is not currently in use.

by Jim Boyce | Apr 16, 2002

Takeaway: Windows XP has brought networking to a new level. But there are major differences between the Windows XP Professional version and Windows XP Home edition. Jim Boyce takes a look at both versions and the differences between networking features.

IPSec
With an increased emphasis on network security, many companies are looking for ways to secure network traffic across the LAN as well as across the WAN. IP Security, or IPSec, provides that means. IPSec lets Windows XP Professional authenticate and encrypt all IP traffic to and from the computer.

IPSec functions at the endpoints of the connection—only the two computers engaged in the secure connection need to support IPSec. Intermediary routers or computers that route the traffic need not support IPSec. For that reason, IPSec is easy to implement in a variety of scenarios, whether the computers are connected across a LAN, WAN, or remote access connection.

IPSec encrypts the IP traffic before it leaves the local computer, securely encapsulating the data to make it secure from sniffing or other compromise. The receiving computer decrypts the data. The result is a completely secure connection over the most public of networks, such as the Internet. Although IPSec might seem more suited to encrypting traffic between routers, it is also an important security mechanism to secure traffic between individual computers. If you need to provide secure connections between client systems or between client and server, and a router-to-router solution isn’t feasible, IPSec could be a major consideration for choosing Professional over Home Edition.

Remote Desktop
Those of us who have been in the IT community for very long are familiar with remote control applications like pcAnywhere and VNC. In fact, I use VNC and pcAnywhere on a daily basis for remote systems management. I also use them as an alternative to KVM switches for managing systems right in my own office. I like the response speed of pcAnywhere and the price of VNC (free) and its support for UNIX and Macintosh platforms.

Remote Desktop lets you connect to and use a remote computer running Windows XP Professional. Remote Desktop is a bit like a lightweight Terminal Services server, although as with most remote control applications, you can connect only one connection at a time to the remote computer. However, one connection to a client computer is generally all you really need. Remote Desktop works like other remote control applications: It’s similar to sitting in front of the computer, except the performance is slower. The actual speed depends on the available bandwidth between the client and server.

You can use almost any Windows platform as a client to connect to and use a remote Windows XP Professional computer. Windows XP Home Edition includes a Remote Desktop Connection client, but not the server component. In addition, the Windows XP Professional CD includes Remote Desktop client software you can use on any platform.

You might not always have access to a client computer with the Remote Desktop Connection client installed, but that isn’t a problem if you’ve planned ahead. The version of IIS included with Windows XP Professional includes a Remote Desktop Web Connection component—a combination of ActiveX controls and other components that lets remote users initiate a Remote Desktop connection to the computer from a Web browser. The session appears in the browser window rather than in a dedicated Remote Desktop Connection client window. The Remote Desktop Web Connection components don’t have to be installed on the computer to be remotely managed. Instead, you can install the components on a Web server on the same network as the computers to be managed and connect through that one Web server to each of the Windows XP Professional computers on the network that has Remote Desktop enabled. This is a great feature that lets users access their systems from public Internet nodes.

Offline Files
The Offline Files feature in Windows XP originated in Windows 2000 and is carried over to Professional, but not the Home Edition. Offline Files creates a local cache of shared network files and folders, enabling you to continue to work on them even when the shared resource is unavailable—such as when the server is down or the client computer is disconnected from the network.

Offline Files is an excellent way to provide consistent and seamless access to network resources. The feature is nearly transparent to the user, which should mean relatively few support calls. However, you should also implement the Encrypting File System (EFS) if you need to ensure the best possible security.

EFS
EFS provides cialis generic price on-the-fly encryption/decryption of NTFS volumes, folders, and files. EFS is included in Windows XP Professional, but not the Home Edition. Encryption is handled by a secondary file system driver and is completely transparent to the user, who doesn’t even need to know that a given folder on his or her computer is encrypted. The driver encrypts and decrypts the data on the fly, and encrypting a folder and its contents is as simple as setting a single attribute for the folder.

Simple File Sharing
Simple File Sharing (SFS) is one feature that confuses a lot of people who are new to Windows XP. SFS makes sharing pretty much a one-click operation and doesn’t require that the user know anything about permissions. However, SFS causes all remote access to the computer to be authenticated against the local Guest account. While this provides easy sharing for users, it also offers little in the way of granular control over access to resources. You can’t grant read-only access to one user or group and grant change permission to another because they are all authenticating against the same account. SFS is enabled by default for Windows XP Professional computers in a workgroup but is disabled for domain members.

With SFS enabled, the Security tab of a folder’s property sheet is hidden, making it rather difficult to set ACLs on the folder. You can turn off SFS on a Windows XP Professional computer to make the computer act just like Windows 2000 in terms of sharing. Windows XP then lets you configure ACLs on the folder and apply restrictions on a per-user or per-group basis. However, Home Edition doesn’t provide a way to turn off SFS. Instead, you have to boot the computer in Safe Mode to access a folder’s Security tab. While this gives advanced users a way to control sharing, it’s hardly a user-friendly approach to controlling file system access.

IIS
Windows XP Professional includes a stripped-down version of Internet Information Services (IIS), enabling a Windows XP Professional computer to host one Web and one FTP site on the computer. Home Edition doesn’t include IIS.

The management interface is the same for IIS as that on Windows 2000. Like IIS on Windows 2000 Professional, Windows XP Professional is limited to 10 concurrent connections. This makes IIS a good choice for sharing printers that make use of the Internet Printing Protocol (IPP) and provides resources to other computers on the LAN when the traditional resource-sharing methods aren’t ideal. It also lets users host and control their own personal Web sites. Plus, there is nothing to stop a Windows XP Professional computer from acting as a public Internet server in situations where the 10-connection limit isn’t a factor. For example, you might use Windows XP Professional as an inexpensive staging server to test Web sites prior to publishing to the final target server.

IIS also includes the SMTP service to allow the computer to act as an SMTP server. The SMTP service accepts incoming connections as well as outgoing connections, but it is intended more as an SMTP relay service than a full-blown e-mail server. The service doesn’t provide mailboxes but does support a drop folder for incoming messages not forwarded to another server. While you could write an application to pull messages from the drop folder, it isn’t worth the effort considering the minimal cost of the many third-party e-mail servers that run on Windows XP. So the SMTP service is useful mainly as an outgoing e-mail server for messages generated by forms or scripts on the local computer. It’s also useful for users who need to send outgoing messages for accounts hosted on remote servers that don’t allow mail relay from the user’s network.

What they have in common
Both Professional and Home Edition support some new features that simplify networking and add capabilities. For example, both let you bridge network interfaces, which can be handy in a home or small office network where you need to connect two disparate networks, such as a new wireless segment and an existing wired segment. Both also let you maintain an alternate TCP/IP configuration for a network interface. This is great for users who have one configuration for the notebook at the office and a different configuration for it at home.

New wireless technologies are supported by both versions for easy setup and configuration of wireless devices. Another commonality is the lack of NetBEUI. Although NetBEUI is included on the Windows XP CD, Setup no longer lists it as an available protocol. Instead, you have to click Have Disk and browse to the CD to install it.

So which one is right for my company?
What’s the bottom line? If you need domain membership and group policy, improved security through IPSec or EFS, or granular protection of shared folders, Windows XP Professional is the solution. If not, you can take advantage of the other new features and streamlined interface provided by Home Edition. At a difference of $100 a seat, you might save a bundle on your next deployment.

November 2nd, 2007

The list, available here (registration required), focuses on popular, widely deployed Windows programs that are often very difficult for an IT department to locate or patch and, as Bit9 explains, “represent unexpected and unquantified vulnerabilities in an enterprise IT environment.”

[Gallery: Ten free security utilities you should already be using ]

Yahoo’s standalone IM client, which has been riddled with security holes all year, is #1 on the list. The buggy Yahoo Widgets software also makes an appearance at number 9.

Apple’s QuickTime media player and iTunes music download software also feature high on the list.

Strangely, Microsoft does not feature heavily on the Bit9 list. In fact, a Microsoft product appears only once on the list — Windows Live MSN Messenger at #4.

The Bit9 explanation:

The reason most Microsoft software doesn’t make the list is because by now most companies have a pretty good process in place for identifying, patching, and fixing vulnerable Microsoft software. The same cannot be said for apps cialis generic brand like Firefox, iTunes, and other packages.

That does make sense but it’s hard to imagine Internet Explorer 6, the world’s most widely used — and heavily targeted — browser, not making an appearance on this list.

I could also make the argument that Microsoft Word, which has struggled with zero-day attacks and multiple code execution hole, should be high on any list of most-vulnerable Windows apps.

Here’s the top-ten from Bit9:

1. Yahoo! Messenger 8.1.0.239 and earlier
2. Apple QuickTime 7.2
3. Mozilla Firefox 2.0.0.6
4. Microsoft Windows Live (MSN) Messenger 7.0, 8.0
5. EMC VMware Player (and other products) 2.0, 1.0.4
6. Apple iTunes 7.3.2
7. Intuit QuickBooks Online Edition 9 and earlier
8. Sun Java Runtime 1.6.0_X
9. Yahoo! Widgets 4.0.5 and previous
10. Ask.com Toolbar 4.0.2.53 and previous

As I always recommend for Windows users, be sure to scan your system for security holes and apply all the necessary patches. Secunia’s free Web-based software inspector is a great place to start. A downloadable version is also available.

Do you print a lot of envelopes with your MS Word documents?

Ever wonder how to dress up your envelope with a picture or business logo?

If you're thinking that might be a wonderful way to give your mailings that extra "punch," you're in the right place, because that's exactly what we're going to discuss today!

So, let's get down to business of turning this:

Into this:

Or, any design that suits your needs (or your mood of the moment).

In older versions of MS Word, you need to begin in the ever handy Envelopes and Labels window (Tools menu, Envelopes and Labels choice).

In Word 2007, you need to go to the Mailings ribbon and click the Envelopes button on the far left.

Once in that window, enter your delivery and return addresses as normal and then click on the Add to Document button.

You will then be returned cialis generic best price to your document, but with one major difference. You should see an envelope at the top of your document (before the first page).

If you don't see the envelope, you probably aren't in the Page Layout or Print Layout view (the name depends on the version of Word you're using). To switch your view, go to the View menu/ribbon and select the correct view.

Now, you can click into the envelope and use the Insert menu/ribbon, Picture choice to insert the picture you'd like to use (you know, the exact same thing you'd do in any document).

It can be moved, resized, etc. just like clipart in all Word files. Right clicking on the picture will allow you to adjust its properties in the Format Picture choice. (I found that I had to change the wrapping style and text alignment to get the text to start next to the top of the picture, instead of the bottom).

You can also highlight the addresses to change the font or text content, using the menus the same as you would for any Word document.

Now, I find it useful to have an envelope saved in a blank document. That way, I can simply keep changing the delivery address on the envelope. (For printing just the envelope, I make sure I've got the cursor on the envelope and I then choose Current Page in the Print window).

This method will really allow you to spice up your envelopes. So, go on, be creative and have fun!

• It can’t identify 16 of the 17 students without conducting interviews or doing forensic investigations, according to Dale Smith, director of network services. Nine of the students accessed a P2P net from the school’s wireless network. Smith testified that he can’t determine “whether the content was accessed by the individual assigned that user name or by someone else using the computer associated with the user name.”
• More importantly, the AG’s office says the RIAA is engaging in unethical behavior towards the court. Despite the fact that deputy AG Randolph Geller told RIAA counsel Katheryn Coggon that the school would preserve all the relevant data, the RIAA said in its subpoena request that:

there was a “very real danger the ISP will not long preserve” the data it wanted.

Having just taken the California Bar’s professional responsibility exam I can tell you such a misrepresentation could result in disciplinary action, IMO.

Since it would take so much effort to ID the students, the RIAA is essentially shifting its own investigatory burden onto the state.

“In short, the subpoena requires the University to create discoverable material to assist Plaintiffs in their litigation rather than merely disclose existing documents,” argues the school, citing case law that indicates that non-parties “are not required to create documents that do not exist, simply for the purposes of discovery.”

Critically, says the Electronic Frontier Foundation, the school argues that the DMCA is the appropriate procedure for the RIAA to identify John Does.

The last argument, if accepted by the court, could radically change the nature of the RIAA’s 4-year litigation campaign against music fans. Currently, the recording industry’s strategy relies on pressuring universities into handing over student targets, either by having the university deliver “pre-litigation settlement letters” to students or, failing that, forcing universities to respond to subpoenas obtained after filing a “John Doe” lawsuit. If these avenues are blocked, the recording industry would have to undertake its own investigatory efforts to determine who to sue.

Whether the university wins or loses its effort, it’s nice to see it standing up on behalf of its students, rather than simply giving in to recording industry demands.