Security Patch for Q823803 causes RAS startup failure

On July 23, 2003, Microsoft issued Microsoft Security
Bulletin MS03-029: Flaw in Windows Function Could Allow
Denial of Service (Q823803).

Installing this patch on my NT 4.0 Server causes my RAS
server to no longer initialize properly. The event log
shows the error:

Point to Point Protocol engine was unable to load the
module.

Without RAS, I am unable to use this system for dialup or
VPN connections.

I uninstalled the patch and the system now works fine.

Use caution.

john
Thu Jul 24 15:01:55 CDT 2003

"Doug" <metroma781@hotmail.com> wrote

> On July 23, 2003, Microsoft issued Microsoft Security
> Bulletin MS03-029: Flaw in Windows Function Could Allow
> Denial of Service (Q823803).
>
> Installing this patch on my NT 4.0 Server causes my RAS
> server to no longer initialize properly. The event log
> shows the error:
>
> Point to Point Protocol engine was unable to load the
> module.

Ditto. And it also causes MBM (Mother Board Monitor), which tells me
the M/B temperature, to fail.

> Without RAS, I am unable to use this system for dialup or
> VPN connections.
>
> I uninstalled the patch and the system now works fine.

Ditto.

> Use caution.

At least it can be uninstalled, and appears to have done no lasting
damage.

John Howells

mla_tk
Thu Jul 24 15:15:38 CDT 2003

"Doug" <metroma781@hotmail.com> wrote in message news:<070d01c3518c$d0f3b650$a401280a@phx.gbl>...
> On July 23, 2003, Microsoft issued Microsoft Security
> Bulletin MS03-029: Flaw in Windows Function Could Allow
> Denial of Service (Q823803).
>
> Installing this patch on my NT 4.0 Server causes my RAS
> server to no longer initialize properly. The event log
> shows the error:
>
> Point to Point Protocol engine was unable to load the
> module.
>
> Without RAS, I am unable to use this system for dialup or
> VPN connections.
>
> I uninstalled the patch and the system now works fine.
>
> Use caution.


I've got the same problem. Q823803 installs a new version of
shell32.dll. I assume this has something to do with running active
desktop on top of NT4. I have only one NT machine with this issue and
this one has active desktop installed. The other NT boxes a running
the classic shell and don't expose the problem. However this is only
an assumption. It could be related to some other configuration
difference. Uninstalling Q823803 resolved the PPP initialization
error.

tk