ChannelInsider bemoaned bad password policies and practices late last week.

It's a problem. Security (unfortunately) is my specialty, so I know it's a problem. But it's going to get worse before it gets better.

First GeCAD, now Sybari.

Microsoft has been buying smaller anti-virus firms and discontinuing their Linux and Unix product lines.

Trust, schmust. When your god is Big Business, that means Big Business can do no wrong, so when you're the U.S. government, you let companies like Microsoft do whatever they want. The problem is that Unix antivirus products are extremely useful, especially in Microsoft shops.

If you've ever tried to run Knoppix on a Compaq or HP Proliant with a Smart Array controller, you probably got a rude surprise.

Here's how to make the hard drive(s) show up.

It's the time of year that a lot of people buy computer equipment, and wireless networking is one of the things people look for. But what things should be on the shopping list?

I was hoping you'd ask that question.

I still work on a lot of Compaq Proliant 1600s. In their day, they were a very versatile server, packing lots of drive bays and open expansion slots into a 5U package. They were also very reliable.

Now that they are five years old or even older, they are less so. But I've collected some good suggestions from Compaq and HP technicians about working on them.

Usually when a Backup Exec remote agent refuses to respond and stopping and starting the service does no good (verifiable by creating a new job and attempting to connect to the remote server, only to find the drive selection boxes greyed out), the solution is to reboot.

There's a last-resort method more appropriate for production servers.

One of the reasons Windows Server 2003 and XP haven't caught on in corporate network environments is that Microsoft has yet to demonstrate any real benefit to either one of them over Windows 2000.

Believe it or not, there actually is one benefit. It may or may not be worth the cost of upgrading, but if you're buying licenses now and installing 2000, this information might convince you it's worth it to install the current versions instead.

There is a little-known issue with Windows XP and network printing that does not seem to have been completely resolved. It's a bit elusive and hard to track down. Here are my notes and suggestions, after chasing the problem for a couple of weeks.

I got an odd Backup Exec error message on Thursday night that I wasn't able to find in Veritas' knowledge base.

The error code is 0x3a18 - 0x 3a18 (14872). Since it seems otherwise undocumented, I might as well document what I know about it.

(Subtitle: My coworkers' favorite new Dave Farquhar quote) If your product isn't suitable for use on production servers, then why didn't you tell us that up front and save us all a lot of wasted time?

(To a Veritas Backup Exec support engineer when he insisted that I reboot four production web servers to see if that cleared up a backup problem.)