From Computerworld blog: Possible bug in Windows patch 902400

The following is excerpted completely from my Computerworld blog. Normally, I'd just give the highlights, but felt this was sufficiently important to give the full scoop on either blog.

A week ago, Microsoft released fix under KB article 902400 for security bulletin MS05-051. The patch is to fix a known vulnerability with the COM+ and Microsoft Distributed Transaction Coordination (MSDTC) subsystems in Windows.

Unfortunately, as many have found out, in certain circumstances the patch can break various network applications and prevent some tools from working properly.

A fix for some problems that may arise out of installation of the patch is detailed in MS KB article 909444.

There is also some information on turning on Transaction Internet Protocol (TIP) in Win 2000 machines after the patch in KB article 908620. TIP was disabled by default on XP and 2003 machines, so the article is probably not relevant for most XP or 2003 machines unless the administrator turned on TIP.

I think I have also stumbled onto an as yet undocumented problem related to this patch. I can no longer use Remote Desktop Protocol (RDP) to connect to the console session of the two servers that received the patch. So I'm using UltraVNC for these servers for the time being until I can fix the problem.

As good as UltraVNC is versus other flavors of VNC, it's still not as good performance wise as RDP.

Anyhow, so far I haven't found a solution to the problem. And Server 2003 isn't logging any information on why RDP can't connect to console in Event Viewer either.

The only errors that I have seen are on pop-ups that appear after the attempt to connect fails. I get either "Error [7051]: The requested session is not configured to allow Remote   Control." if I try connecting from Terminal Services Manager, or if I attempt to connect using RDP "Error connecting to existing session for <username> (Id 0). The operation completed successfully." pops up.

All the fixes I've found on Microsoft or on Google (there's that search problem rearing it's ugly head again) to date, haven't resolved the issue.

Oh, and the fact that this latest round of updates requires a restart is further validation that Windows has room to improve in this area with the next version.

If anyone has any ideas, let me know.

Comments

[Deepak]

Great post. Thanks for posting this.