Vista - IE 7 address bar unresponsive

I am having an interesting issue with Internet Explorer 7, under Windows
Vista Business RTM. In IE, when I type in a URL, such as www.microsoft.com
and press the enter key (or click the go button) nothing happens for a long
time. If I leave the browser window alone, about 5 minutes later the page
will load.

In my troubleshooting, I have found that typing in the full URL, e.g.
http://www.microsoft.com works just fine and loads the page right away. I’ve
also found that typing in the partial URL (e.g. www.microsoft.com) and
pressing CTRL+ENTER load the page right away also. Though, this doesn’t work
for non-.com addresses; e.g. www.uiuc.edu. Instead, IE tries to navigate to
www.uiuc.edu.com.

The most interesting thing I’ve found in my troubleshooting is that this
ONLY occurs when I am NOT in my office; when I’m disconnected from my active
directory network (my machine is joined to my University’s Active Directory
Domain). At the office, typing in www.microsoft.com works right away, but
from my home DSL or a café hotspot, I am plagued with the problem.

Has anyone else had this problem and been able to work around it? This
seems like some type of DNS bug associated with my Domain settings, but I’m
really not sure.

I concur with this bug. It is the singularly most frustrating problem with
IE7. I type something in the address bar and nothing happens, whether it is
an URL (without http:// prepended), or a search query. I count myself lucky
though- the delay for me is only about 10 seconds. I'm also working on
account roaming from its home domain, although I haven't verified that
things work fine when I'm actually connected to the domain. I'm running Vista
RTM.

"jBiehl" wrote:

> I am having an interesting issue with Internet Explorer 7, under Windows
> Vista Business RTM. In IE, when I type in a URL, such as www.microsoft.com
> and press the enter key (or click the go button) nothing happens for a long
> time. If I leave the browser window alone, about 5 minutes later the page
> will load.
>
> In my troubleshooting, I have found that typing in the full URL, e.g.
> http://www.microsoft.com works just fine and loads the page right away. I’ve
> also found that typing in the partial URL (e.g. www.microsoft.com) and
> pressing CTRL+ENTER load the page right away also. Though, this doesn’t work
> for non-.com addresses; e.g. www.uiuc.edu. Instead, IE tries to navigate to
> www.uiuc.edu.com.
>
> The most interesting thing I’ve found in my troubleshooting is that this
> ONLY occurs when I am NOT in my office; when I’m disconnected from my active
> directory network (my machine is joined to my University’s Active Directory
> Domain). At the office, typing in www.microsoft.com works right away, but
> from my home DSL or a café hotspot, I am plagued with the problem.
>
> Has anyone else had this problem and been able to work around it? This
> seems like some type of DNS bug associated with my Domain settings, but I’m
> really not sure.
>

"jBiehl" <jBiehl@discussions.microsoft.com> wrote in message
news:099007A4-4438-4F8D-8984-4FEEAA701A0A@microsoft.com...
>I am having an interesting issue with Internet Explorer 7, under Windows
> Vista Business RTM. In IE, when I type in a URL, such as www.microsoft.com
> and press the enter key (or click the go button) nothing happens for a long
> time. If I leave the browser window alone, about 5 minutes later the page
> will load.
>
> In my troubleshooting, I have found that typing in the full URL, e.g.
> http://www.microsoft.com works just fine and loads the page right away. I’ve
> also found that typing in the partial URL (e.g. www.microsoft.com) and
> pressing CTRL+ENTER load the page right away also. Though, this doesn’t work
> for non-.com addresses; e.g. www.uiuc.edu. Instead, IE tries to navigate to
> www.uiuc.edu.com.


You could do those too now using the new Prefix and Suffix options
in the Language Preference dialog. Previously a regedit would have
been required.

AFAIK search from the Address bar used to be required to enable the
Ctrl-Enter anachronism but it seems that this may no longer be true?
In that case disabling Search from the Address bar may do both things
for you--allow you to use Ctrl-Enter and bypass whatever it is that is
causing you such long waits when you don't use a protocol prefix on
a partial URL.


>
> The most interesting thing I’ve found in my troubleshooting is that this
> ONLY occurs when I am NOT in my office; when I’m disconnected from my active
> directory network (my machine is joined to my University’s Active Directory
> Domain). At the office, typing in www.microsoft.com works right away, but
> from my home DSL or a café hotspot, I am plagued with the problem.
>
> Has anyone else had this problem and been able to work around it? This
> seems like some type of DNS bug associated with my Domain settings, but I’m
> really not sure.


My guess is it's a symptom of spyware being present.


Good luck

Robert Aldwinckle
---

> You could do those too now using the new Prefix and Suffix options
> in the Language Preference dialog. Previously a regedit would have
> been required.

No, that didn't solve the problem.

> My guess is it's a symptom of spyware being present.

Again, no, this ioos a clean install of Vista Business (unless, of course,
it is Microsoft pre-installed spyware).

MS MVPs: There have been lots of posts on this issue with no response. Are
you going to address?

I would ask the IE MVP's who hang out in the internet explorer newsgroups.
There are quite a lot of them.

"jBiehl" <jBiehl@discussions.microsoft.com> wrote in message
news:05B63850-E976-4C97-AF89-E4ED9A9CF05E@microsoft.com...
>
>> You could do those too now using the new Prefix and Suffix options
>> in the Language Preference dialog. Previously a regedit would have
>> been required.
>
> No, that didn't solve the problem.
>
>> My guess is it's a symptom of spyware being present.
>
> Again, no, this ioos a clean install of Vista Business (unless, of course,
> it is Microsoft pre-installed spyware).
>
> MS MVPs: There have been lots of posts on this issue with no response.
> Are
> you going to address?