Windows 98 Critical Updates and June 30th 2006 cut off date. Really going to happen? How critical is this?



Windows 98 Critical Updates and June 30th 2006 cut off date. Really
going to happen? How critical is this?

Still have several networked Windows 98SE machines at a small
company, in addition to XP machines. All of the machines feature a
corporate anti-virus scanner, etc. Network is protected by a Cisco
Firewall.

Will keeping these machines on the network leave new security holes?
Most of Microsoft's critical updates seem to be for IE6 more than
anything.

These machines still suit our needs fine, so I'd hate to have to
replace them all just because of new security issues. Most of them
are 600 mhz, 128 megs ram. Our applications require more like 166
mhz, 32 megs of ram, etc. Too old to be worth investing in XP, but so
far we have yet to find a good reason to replace them.

Some of the machines do surf the web, usually with FireFox, check
e-mail, etc. I can handle a machine here and there getting infected,
but i'm more concerned about a network wide attack, and most
importantly our Windows 2000 server.

What are other small companies doing about the June 30th issue?

Thanks for any advice.



.



Relevant Pages

  • Re: Windows XP; Windows 98 & Windows NT 4.0 compatability
    ... >3) ICF is DISABLED on the XP Machines ... >4) I'm not quite sure what you mean on file sharing. ... >obviously I can see the XP machines on the 98 Network ... Windows XP is the latest attempt to merge the Windows 9x product line ...
    (microsoft.public.windowsxp.network_web)
  • Re: Is a Windows 98se computer more, or less, of a security threat with IE 5.5 (unused) & Firefo
    ... We aren't using any Windows ME machines at all. ... That might be a better solution, however Windows 98 does not support ... He's very knowledgable about network security, ...
    (microsoft.public.windowsupdate)
  • Re: File sharing fails.
    ... Still no working network is obvious.. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.basics)
  • Re: paging all socket geniuses
    ... Windows, my laptop, or me or all three are... ... about the absence of a network... ... Ping was a nice courtesy of a tamer Internet of the past. ... machines and firewalls are configured to block all ICMP traffic (which ...
    (comp.lang.lisp)
  • Re: Windows XP on a Macintosh network
    ... > with Windows machines. ... You'll have to look in your Mac's network ... > Printer Wizard works very well to add network laser printers to Windows ...
    (microsoft.public.windowsxp.network_web)