Sending spyware report

  • Thread starter Thread starter david
  • Start date Start date
D

david

Everytime I try to send spyware report I get error "
Please check your proxy settings".. What should the
settings be?
 
Settings which work for Internet Explorer should work for Microsoft
Antispyware. I have a machine which has this symptom to test with, but can
only work with it after business hours, and carefully.

I don't know of a cause for this behavior. I do know that if you set proxy
settings into the Internet Explorer settings, Microsoft Antispyware uses
those settings. However, for most home users, there are no such settings

Not enabling Spynet reporting turns out to have no effect on this reporting
function--I've just tested this.

So--don't look too hard. I don't know the specific cause of the issue, nor
any workaround.
 
I wonder how many people have their browser set to automatically detect
proxy settings even though that option does not need to be checked?

Also, I wonder how many of these Unable to Update problems are for people
who are forced through a proxy server by their service provider based on the
dns entries set on their machine?

My former cable service provider would force you to use their proxy by
redirect so I would set my dns entries manually to a couple of UU.net
caching servers instead and avoid the proxy redirect problem.

JohnF.
 
JohnF. said:
I wonder how many people have their browser set to automatically detect
proxy settings even though that option does not need to be checked?

Also, I wonder how many of these Unable to Update problems are for people
who are forced through a proxy server by their service provider based on the
dns entries set on their machine?

My former cable service provider would force you to use their proxy by
redirect so I would set my dns entries manually to a couple of UU.net
caching servers instead and avoid the proxy redirect problem.
Click to expand...

Do we have ISPs who uses proxyservers ? thought that was
Internet history.

For corporate networks I can understand why they uses proxys.

Nevertheless I think its a bug in this report function.
 
The automatically detect slows down the initial connection, but doesn't
interfere with it beyond that, as far as I've spotted.

The proxy thought is interesting. We've had some runs of users with either
persistent bad downloads, persistent receipt of the wrong build version
download, or persistent corrupted downloads, some of which might be due to
caching issues.

The test machine I've got which can't send a report is behind ISA server
2000, which is an automatic proxy. However, most other machines on that
network can send reports fine.

That particular machine is an upgrade of retail XP over OEM Windows 2000.
I've got another machine with that same upgrade path in the same office
which I should check to see if it has the same issue. Hmm--NOPE. So much
for that idea.
 
Cablemodem networks force all their people through proxy/caching servers to
cut back on bandwidth.
 
JohnF. said:
Cablemodem networks force all their people through proxy/caching servers to
cut back on bandwidth.
Click to expand...

Hmmm strange, but maybe it is so with cable, beacuse one
argument
to use proxys was to minimize bandwithusage beacuse every
popular website
was inside this proxy already, but with todays p2p traffic
this webtraffic
is minimal compared to p2p traffic. And we also have a complete
different situation with backbones.

I have seen numbers from corerouters that 90 % is p2p
traffic nowadays.

I know from xDSL that this is done with switches inside the
DSLAM equipment.

And for overall bandwith usage ISPs can controll traffic
inside their corerouters,
peeringrouters etc.
 
Back
Top