KB911280 update problem

After installing XP Security Update KB911280 (to resolve a "remote code
execution security issue ... in the Routing and Remote Access service ") and
rebooting, the computer was unable to connect to the Internet. The
connection process would simply halt at the initiation of the logon script
(cis.scp) for Compuserve, refusing to run the script.

The question: Is there a setting somewhere that will allow the Network
Connection login script to run as it should after installation of this update?

It is definately KB911280 causing the problem. (I had to roll back after
installation of all updates and then install each separately to determine the
cause.) KB911280 is not now installed, of course. (Else I wouldn't be here.


I'm running XP Pro with SP2 and all other security updates and have no other
problems to report regarding updates outside of this.

Thanks,

MzM

"MzM" wrote:

> After installing XP Security Update KB911280 (to resolve a "remote code
> execution security issue ... in the Routing and Remote Access service ") and
> rebooting, the computer was unable to connect to the Internet. The
> connection process would simply halt at the initiation of the logon script
> (cis.scp) for Compuserve, refusing to run the script.
>
> The question: Is there a setting somewhere that will allow the Network
> Connection login script to run as it should after installation of this update?
>
> It is definately KB911280 causing the problem. (I had to roll back after
> installation of all updates and then install each separately to determine the
> cause.) KB911280 is not now installed, of course. (Else I wouldn't be here.
>
>
> I'm running XP Pro with SP2 and all other security updates and have no other
> problems to report regarding updates outside of this.
>
> Thanks,
>
> MzM
>

MzM <> wrote:

> After installing XP Security Update KB911280 (to resolve a "remote
> code execution security issue ... in the Routing and Remote Access
> service ") and rebooting, the computer was unable to connect to the
> Internet. The connection process would simply halt at the initiation
> of the logon script (cis.scp) for Compuserve, refusing to run the
> script.

Have you tried re-installing your Compuserve software *after* applying
911280?

--
Robin Walker [MVP Networking]

"Robin Walker [MVP]" wrote:

> Have you tried re-installing your Compuserve software *after* applying
> 911280?

Hi Robin,

No Compuserve software, it's just a standard TCP/IP network connection
running a logon script for that ISP. (In fact, that same old cis.scp file
has been included in Windows for years. In XP Pro, it's located under
system32 in the "ras" subfolder.)

This is not the "new" Compuserve running on the AOL platform (csi.com), but
the original service platform which requires temporary switching of port
databits and parity during logon. Which...hmmm...may be the problem right
there. (Old forgotten script getting shot down for suspicious behavior?)

MzM

Yep, should have paid more attention and posted this sooner...

A script.log was generated in the ras folder. It contains this entry:

> C:\WINDOWS\system32\ras\cis.scp(16) : 'set port' : an internal error occurred.

More like "getting warm" than a Bingo, but better than nothing. Sorry for
the delay.

MzM

I've found that KB91128 "breaks" the ability for the connection to pass any
info back to host you connect to. We have medical billing software which
transmits Medicare claims over a dialup connection. Medicare has a
requirement that an after-dial terminal window must be used to enter the user
ID & login, and then the PPP connection can be established. We found that
when the login prompt appeared on the post-dial window, we could not type
anything into it. Tried to use a script - same results. Once we uninstalled
KB911280, it worked just fine.

Since then, we've had 2 other users (1 XP, 1 2000) report the exact same
problem, with the exact same solution.

FYI - I called and attempted to repor the issue w/MS, using the support #
listed on the info page for KB911280 - I was told to either write a letter
(paper - to MICROSOFT?), or I could risk spending $250 up front to report it.
I explained I was attempting to do them a favor, but no use. A hell of a
lot differnent since I worked with MS in the late 80's and early 90's.


"MzM" wrote:

> After installing XP Security Update KB911280 (to resolve a "remote code
> execution security issue ... in the Routing and Remote Access service ") and
> rebooting, the computer was unable to connect to the Internet. The
> connection process would simply halt at the initiation of the logon script
> (cis.scp) for Compuserve, refusing to run the script.
>
> The question: Is there a setting somewhere that will allow the Network
> Connection login script to run as it should after installation of this update?
>
> It is definately KB911280 causing the problem. (I had to roll back after
> installation of all updates and then install each separately to determine the
> cause.) KB911280 is not now installed, of course. (Else I wouldn't be here.
>
>
> I'm running XP Pro with SP2 and all other security updates and have no other
> problems to report regarding updates outside of this.
>
> Thanks,
>
> MzM
>

MzM <> wrote:

> No Compuserve software, it's just a standard TCP/IP network connection
> running a logon script for that ISP. (In fact, that same old cis.scp
> file has been included in Windows for years. In XP Pro, it's located
> under system32 in the "ras" subfolder.)

Call Microsoft for free support, (1-(866) PC-SAFETY if you are in the USA),
and reference case number SOX060615700008.

--
Robin Walker [MVP Networking]

granth5 <> wrote:

> I've found that KB91128 "breaks" the ability for the connection to
> pass any info back to host you connect to. We have medical billing
> software which transmits Medicare claims over a dialup connection.
> Medicare has a requirement that an after-dial terminal window must be
> used to enter the user ID & login, and then the PPP connection can be
> established. We found that when the login prompt appeared on the
> post-dial window, we could not type anything into it. Tried to use a
> script - same results. Once we uninstalled KB911280, it worked just
> fine.


Call Microsoft for free support, (1-(866) PC-SAFETY if you are in the USA),
and reference case number SOX060615700008.

--
Robin Walker [MVP Networking]

Yes, I am another user with the same issue. Using XP to communicate
with a Cisco 2509 router that needs scripted login. It hangs at the
point where the script is expected to send the username, eventually
times out. Thank you Microsoft for this really (un)useful update.

Running XP Pro SP2 and all updates. (911280 installed automatically,
thanks very much, Microsoft. Cost me a couple of hours to sort it out)


Robin Walker [MVP] wrote:
> granth5 <> wrote:
>
> > I've found that KB91128 "breaks" the ability for the connection to
> > pass any info back to host you connect to. We have medical billing
> > software which transmits Medicare claims over a dialup connection.
> > Medicare has a requirement that an after-dial terminal window must be
> > used to enter the user ID & login, and then the PPP connection can be
> > established. We found that when the login prompt appeared on the
> > post-dial window, we could not type anything into it. Tried to use a
> > script - same results. Once we uninstalled KB911280, it worked just
> > fine.
>
>
> Call Microsoft for free support, (1-(866) PC-SAFETY if you are in the USA),
> and reference case number SOX060615700008.
>
> --
> Robin Walker [MVP Networking]
>

wrote:
> (911280 installed automatically,
> thanks very much, Microsoft. Cost me a couple of hours to sort it out)

Um, you told Windows to do that. Maybe now you'll disable Automatic
Updates and go to Windows Updates and choose what updates you want.

Alias