[softwarelist] Re: [softwarelist] Re: [softwarelist] Re: [softwarelist] Re: [softwarelist] Windows update (OT for list). Was: OvnPro 2.77 type 5 errors

In message <f644331e50.Alan.Adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
          Alan Adams <alan@xxxxxxxxxxxxxxxx> wrote:

> In message <9ec72e1e50.Alan.Adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
>           Alan Adams <alan@xxxxxxxxxxxxxxxx> wrote:

Apologies if following up my own followup to my own message upsets 
you...

The following is part of the info from Microsoft about the update 
KB957687 which went out yesterday, and appears to be causing some 
problems.
====
This security update resolves two privately reported vulnerabilities 
and one publicly disclosed vulnerability in Microsoft Server Message 
Block (SMB) Protocol. The vulnerabilities could allow remote code 
execution on affected systems. An attacker who successfully exploited 
these vulnerabilities could install programs; view, change, or delete 
data; or create new accounts with full user rights. Firewall best 
practices and standard default firewall configurations can help 
protect networks from attacks that originate outside the enterprise 
perimeter. Best practices recommend that systems that are connected to 
the Internet have a minimal number of ports exposed.

This security update is rated Critical for all supported editions of 
Microsoft Windows 2000, Windows XP, and Windows Server 2003, and 
Moderate for all supported editions of Windows Vista, and Windows 
Server 2008. For more information, see the subsection, Affected and 
Non-Affected Software, in this section.

The security update addresses the vulnerabilities by validating the 
fields inside the SMB packets. For more information about the 
vulnerabilities, see the Frequently Asked Questions (FAQ) subsection 
for the specific vulnerability entry under the next section, 
Vulnerability Information.
====
In other words, there are changes to the SMB server within Windows. I 
would not be surprised therefore if it caused problems for non-Windows 
systems emulating SMB.

However my tests with and without the patch fail in exactly the same 
way, just sooner without the patch than with it.

Make of that what you will.


>> In message <JX7IcIB1h3bJFwXJ@xxxxxxxxxxxxxxxxxxx>
>>           David Pilling <flist@xxxxxxxxxxxxxxxxxxx> wrote:

>>> In message <096f1d1e50.pnyoung@xxxxxxxxxxxxxxxxxxxx>, Dr Peter Young
>>> <pnyoung@xxxxxxxxxxxx> writes
>>>>FWIW, my Windows machines have been updated with anything offered by
>>>>the upgrade program, and so far at any rate I can communicate with (at
>>>>least one of) them using the new version of LanMan98. I was worried

>>> Like one of those movies where zombiefication befalls anyone who goes to
>>> sleep, the lure of afternoon tea proved too strong and I left my PC
>>> alone. Returning I was greeted with the triumphant announcement "Windows
>>> updated your computer!".

>>> I know this is true because copying files from RISC OS has stopped
>>> working again.

>>> What would be interesting is if the version of Lanman has anything to do
>>> with this, I've not updated my Iyonix for a long time. Currently it
>>> shows me Lanman version 2.30, 16th. Feb 2004.

>> I'm using LanM<an98 v1.22, (10 Mar 2004). I just tried copying a
>> folder of Audio CD files, in WAV format. It locked up the filer action
>> window somewhere between 500M and 1G. The Windows update ran
>> yesterday.

>> I have the new version of LanMan98, but I need to reboot to turn off
>> the okld one, which is refusing to go away - "LanMan98 is in use".

> To continue: I set up LanMan98 V2.00 (05 Oct 2008), and tried again.

> It failed at 750MBytes transferred, just as the previous version did.

> I then removed the KB958687 Windows security patch, and tried again.
> It failed at 380MBytes! (It might be because I was counting the
> previous transfers over the link at the same time.

> I RMKilled the LanMan98 module, and quit the filer, then ran LanMan98
> again. It timed out connecting.

> I rebooted the XP PC - NOT the Iyonix. After rmkilling and restarting
> LanMan98, the connection works again. This suggests to me that the
> timeout is caused by something going wrong on the PC end, not in
> RISC OS.

>>> Incidentally, I tried my RISC PC earlier today, and that had stopped
>>> working too.

>>> Perhaps Drobe could do the story "Crisis for Microsoft as network
>>> problems cut Windows off".








-- 
Alan Adams, from Northamptonshire
alan@xxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
To unsubscribe or subscribe goto: http://www.freelists.org/list/davidpilling

Other related posts: