Recently, during testing of a new XP SP2 image, we found one of our
applications which integrates with Office 2003 SP1 (Outlook) could not
connect via VPN. The really strange thing was that last year's image -
XP SP1 / Office 2003 - had no problem even after applying XPSP2 and
Office2k3 SP1 to it.
On a hunch (in desperation?), I tried applying a fix described in MSKB
Q244474 - How to force Kerberos to use TCP instead of UDP in Windows
Server 2003, in Windows XP, and in Windows 2000 -
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q244474 which
fixed the problem!
Hope this helps.
Jerry
-----Original Message-----
From: Windows NTBugtraq Mailing List
[mailto:NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM] On Behalf Of Darryl J Roberts
Sent: Tuesday, April 19, 2005 9:11 PM
To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
Subject: MS05-019 Breaks VPN
After installing the update in Microsoft Security Bulletin MS05-019 on
two servers at a customer site, we are no longer able to connect via VPN
to terminal services on those servers...
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message. Any
disclosure, copying, or distribution of this message, or the taking of any
action based on it, is strictly prohibited.
--
NTBugtraq Editor's Note:
Most viruses these days use spoofed email addresses. As such, using an
Anti-Virus product which automatically notifies the perceived sender of a
message it believes is infected may well cause more harm than good. Someone who
did not actually send you a virus may receive the notification and scramble
their support staff to find an infection which never existed in the first
place. Suggest such notifications be disabled by whomever is responsible for
your AV, or at least that the idea is considered.
--
