Thursday, June 15, 2006

Potential Patch Problem with MS06-025

I wanted to give everybody a warning about this, just in case you have issues, of course, if dialup is affected, I'm not sure how you'll see this. ;)
To quote SANS Internet Storm Center:
Published: 2006-06-15,
Last Updated: 2006-06-15 18:59:11 UTC by Lorna Hutcheson (Version: 1)

We have received some reports of a potential issue with MS06-025. Here is a snippet of what appears to be the problem as it was report to us:

"We received couple of calls that users are
not able to dial up after applying MS06-025 (KB911280).

I verified this on a test machine and it looks like it breaks dial up.

We have some scripts that need to be run in order to authenticate the user
properly after the dial up connection is established.

It looks like the patch prevents scripts from running at all. Even when I
turned on the terminal window (in interactive logon and scripting) I can't
log in manually at all. After the connection is established I can see the
Username prompt in the terminal window but I can't enter any data.

Uninstalling the patch fixes this."

Microsoft has confirmed they are getting some reports of this and have established a case number. If you are having similar problems, call Microsoft for free support, 1-(866) PC-SAFETY, and reference case number SOX060615700008.

Potential Patch Problem with MS06-025 (NEW)

1 comment:

  1. Yup. I've been doing the frantic phone call thing for a few hours, now. It does indeed break the TCP/IP stack as dialup sees it.

    I'm not aware of how many machines are affected. It didn't bother ours, nor most of those I know using dialup.

    Google on "Winsockxpfix" (without the quotes). I know Softpedia has it and I'm sure it can be gotten elsewhere. Run it and reboot, then rebuild the connectoid.



All comments are moderated.

Note: Only a member of this blog may post a comment.