On Sat, 17 Jun 2006, Stephen Bird wrote:
My tech support friend has the impression there are not many
people using dial-up with a script. Perhaps this is why MS
didn't test or weren't aware of what could happen.
True. My original post stated: "use a dial-up connection (and
use a script to logon)". I should have highlighted the "(and
use a script to logon)" part to avoid causing undue concern.
The "Known issues" section of the MS MS06-025 article itself
describes dial up scripting as ancient and rare.
---------------------------
<http://support.microsoft.com/kb/911280>
An issue has been confirmed involving dial-up connections which
use the terminal window or dial-up scripting. Dial-up terminal
windows or scripting is an older technology rarely used by most
modern dial-up connections. If dial-up scripting is used in a
connection, the connection may stop responding. This does not
affect any dial-up connections that do not use dial-up
scripting. This issue may affect direct dial connections to a
corporate or university network or to some ISPs (Internet
Service Providers). Microsoft is working on developing and
testing a revision to this update which will address this
issue. If you need to use these dial-up scripting or terminal
window features do not install security update MS06-025
(KB911280) until the revised version is available. More
information on dial-up scripting can be found at
http://www.microsoft.com/technet/archive/winntas/proddocs/network/xns10.mspx
Virtual private network (VPN) connections are not affected by
this issue; dial-up scripting is not supported in VPN
scenarios.
---------------------------
--
----------------------------------------
The WIN-HOME mailing list is powered by L-Soft's renowned
LISTSERV(R) list management software. For more information, go to:
http://www.lsoft.com/LISTSERV-powered.html
