....
I typed in ? AutoSearch and it took about 2 minutes and I was directed
to an MSN search page. I dont know if this is what was supposed to
happen or not but that is what happened. Thanks
The MSN search page is the default URL for searches from the
Address bar. This proves that you have search from the Address bar
enabled and that you don't have a customized URL for it.
However, it should not be taking 2 minutes to respond.
That could still be sign of a search hijacking by spyware.
E.g. the site which a search query is first being directed to
is some other site which is out of service or overloaded and underpowered.
Normally it would be operating efficiently and transparently
so you wouldn't notice that your query had been surreptitiously intercepted
before being forwarded to the intended search provider.
You haven't disclosed your OS. If it is NTx you could use
some of its command line tools to try to examine the details
needed by a search query.
E.g. in a cmd window enter:
nslookup search.msn.com
FWIW when I do that I see:
<example>
Non-authoritative answer:
Name: a134.g.akamai.net
Addresses: 206.167.78.32, 206.167.78.24
Aliases: search.msn.com, search.msn.com.nsatc.net
search.msn.com.edgesuite.net
</example>
Next try:
ping -n 1 search.msn.com
<example>
Pinging a134.g.akamai.net [206.167.78.32] with 32 bytes of data:
</example>
In this case we are just using it to see what address is
being used. It doesn't really matter if there is a response.
If a significantly different address is being used than
one that nslookup showed it could indicate a problem
with the lookup or that an incorrect override is in place.
Next try using telnet to simulate the request that IE does.
This is actually a better connectivity test than ping because
it involves the actual destination port that would be needed.
E.g. enter in the cmd window:
telnet search.msn.com 80
You would expect the screen to clear at which point you
could paste and enter the following request:
GET /results.aspx?q=autosearch&FORM=I7AW HTTP/1.1
If that is accepted (in my case it wasn't which is interesting)
you might then have to paste and enter:
Host: search.msn.com
Alternatively you could trace the actual request made by IE
and see what is really going on (e.g. using a tool such as
FiddlerTool connected as a proxy--which is what I used
to capture the correct syntax of both the GET request
and Host: header.)
HTH
Robert
---