Saturday, April 24, 2010

IPSec service won’t start

When this happens, all TCP/IP traffic stops. If you try to restart the service, you may receive this message:

Error 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.

If you look in the Event Log, you’ll see that IPSec has entered block mode. The recommendation is to disable IPSec services and restart the server. Don’t follow that advice.

To get everyone working quickly, stop the DNS Server service. Then start the IPSec service start. Restart the DNS Server service and everything should be back to normal – at least for now.

This behavior is due to a problem after installing update MS08-037 which addressed DNS vulnerabilities.

To avoid the problem in the future, you’ll need to edit the registry key that lists the DNS port reservations. Check out the details here for more info.

Saturday, April 17, 2010

.NET Framework Corruption Issues

When a .NET Framework becomes corrupt, correcting the problem can be time consuming. Specifically, if .NET 1.1 is corrupt, all subsequent .NET Frameworks releases installed must also be removed. If just version 3.5 has an issue, the earlier releases can be left alone if there’s no problem.

We came across a .NET problem that prevented the removal of two of the four Framework releases. Aaron Steiner’s .NET Framework Cleanup Tool easily removed all corrupted remnants and permitted us to reinstall everything quickly.

Saturday, April 10, 2010

Using Printers With Remote Desktop Protocol

The updates to the Terminal Services and Remote Desktop Protocol printing functionality in Windows 2008 and 2008 R2 has been great in our experience. However, on occasion, it’s not always as seamless as you would hope.

That’s not to say that it’s Microsoft’s fault – it’s usually a result of the printer manufacturers. Due to the myriad of drivers available for even a single printer model, printer names get mismatched and sometimes it’s just a few characters like a version number or a dash that causes problems.

For example, a LaserJet 5 could appear as a LaserJet 5 Series, Laserjet 5 Series PCL6, etc. depending on the version of the driver and the exact printer model.

Instead of removing and reinstalling the matching driver, Microsoft has a workaround in this KB. To summarize, you’ll see event ID 1111, 1105 or 1106 in the system logs. Create a registry key and a corresponding .inf file that matches the printer name variations. Works great.

There’s also a Printer Driver Redirection Wizard that automates the creation of the .inf file if you need more help.

Saturday, April 3, 2010

CEICW error on SBS 2003

This week, we saw a SBS server run the following message when running the CEICW:

“This wizard can only be run on a Small Business Server computer.”

Since the wizard only appears on a Small Business Server computer, we were a bit puzzled. As it turns out, this is the result of a missing registry key. MS has posted a hotfix for it and you can request it here.

Thursday, April 1, 2010

Office 2010 RTM

Microsoft Office 2010 was released to manufacturing last week. If you’ve got a TechNet or MSDN subscription, you can check it out today.

We’ve been working with the Technology Preview and Beta versions since last August. It’s a solid product, so when it’s available for purchase in the coming weeks, there’s no need to hold off.

The addition of the “ribbon” interface to Outlook, Publisher, Project and Visio are excellent.