Microsoft Hotfix KB968389 (Networking Products)
At 31 AUG 2009 12:45:55PM Harold Vance wrote:
This post is just an FYI for anyone contemplating the installation of some recent Microsoft hotfixes. We installed KB968389 on our Windows 2003 SP2 server on Sunday 08/28/09. Server config includes Universal Driver 4.5, OpenInsight 8.08 and Arev 3.12.
After the installation of this hotfix and the first reboot, the Windows XP clients (which were also rebooted) were unable to attach certain data volumes. Even though all of our data volumes are in the same parent folder and even though the permissions are set at the parent, the clients were unable to attach some of the volumes. We could not figure out why some volumes would attach and others would not. The revmedia files in the affected volumes had not been changed in months. There were no visible problems with any of the Rev*.* files. There were no hardware (disk) issues reported in the Event log.
We then rebooted the server again, and the clients were able to attach all volumes without error. However, we noticed major performance issues with the btree extract process and with Arev suspend operations. The btree extracts ran extremely slowly – even for tables with only five records. Also, running a Suspend in Arev would sometimes lock/freeze the NTVDM session.
At any rate, we identified hotfix KB968389 as having an impact on Windows Authentication and we also discovered that it requires manual registry changes. We did not perform the suggested changes as we had no way of knowing how they would affect our domain security in general. We therefore chose to remove this hotfix, and the removal cleared up all of the performance issues we were having between client and server.
Again, this is just an FYI on some problems that we had with KB968389.
At 31 AUG 2009 05:48PM Eric wrote:
http://support.microsoft.com/kb/968389
After applying this patch, all authentication processes will get back to you after lunch.
At 01 SEP 2009 09:00AM Jared Bratu wrote:
Thank you for the detailed report. I read through the Microsoft KB support posting and the hotfix requires a registry change to opt-in.
Can you verify, did your system administrator opt-in or did simply installing the hotfix cause the problem?
Was there a difference between AREV and OI. Did OI work correctly and AREV encountered trouble?
At 05 OCT 2009 07:04PM Harold Vance wrote:
Jared, pardon the delay. Simply installing the hotfix caused the problems. We did not change the registry per Microsoft's instructions.