W
Wayne
Ever since Sept 18, we are unable to connect to certain
websites. We have 60+ machines on our LAN and Bellsouth
as our ISP. We are running OS's from Win98-WinME. Only
the machines that are Win2k are able to connect with no
problem. Here are some of the Websites tested:
Can Connect
www.nascar.com
www.yahoo.com
www.govols.com
Cannot Connect
www.symantec.com (need to get live update badly)
www.microsoft.com
www.netscape.com
We have contacted Bellsouth which replyed that nothing has
changed. We have changed the name of the host file,
removed all spyware, upgraded to IE 6.0 SP1 and anything
else that we could dig up that came close to our problem.
None of the above has corrected the problem.
We are not the only ones with this problem. On Sept. 18
and thereafter, there has been several friends and co-
workers inform us that their home access is also doing the
same thing.
After intensely reading and reseaching, this problem is
not just local. There has been numerous postings about
this problem. Here are my questions:
I would like to know from all the others that have posted,
if this started on or around Sept. 17 - 18?
Is microsoft aware and working on it?
And has anyone found a solution?
Thanks
Wayne
websites. We have 60+ machines on our LAN and Bellsouth
as our ISP. We are running OS's from Win98-WinME. Only
the machines that are Win2k are able to connect with no
problem. Here are some of the Websites tested:
Can Connect
www.nascar.com
www.yahoo.com
www.govols.com
Cannot Connect
www.symantec.com (need to get live update badly)
www.microsoft.com
www.netscape.com
We have contacted Bellsouth which replyed that nothing has
changed. We have changed the name of the host file,
removed all spyware, upgraded to IE 6.0 SP1 and anything
else that we could dig up that came close to our problem.
None of the above has corrected the problem.
We are not the only ones with this problem. On Sept. 18
and thereafter, there has been several friends and co-
workers inform us that their home access is also doing the
same thing.
After intensely reading and reseaching, this problem is
not just local. There has been numerous postings about
this problem. Here are my questions:
I would like to know from all the others that have posted,
if this started on or around Sept. 17 - 18?
Is microsoft aware and working on it?
And has anyone found a solution?
Thanks
Wayne