HOSTS file ignored by IE6!!!

[Glaucus]

seer wrote:
It's probably unrelated, but does your PC have more then 1 NIC ? Are there any more gateways defined in those NICs ?

Nope, just the one NIC.

Also, what happens if you go to http://127.0.0.1 or http//localhost ?

127.0.0.1 gives me this:
Server Error
The following error occurred:
[code=CANT_CONNECT_LOOPBACK] Cannot connect due to potential loopback problems

localhost gives me:
The page cannot be displayed

The strange thing is, if enter localhost twice in a row, the 2nd time it seems to go off searching for it indefinetly, and times out.

As a last test, hook up another computer on the lan and try to acces the website either bij DNS name or IP adress..

Already did that. The 2nd PC has no problem accessing my machine, either using the IP address or a domain name specified in it's hosts file.

May not give anything to help, but it's worth to check it just in case..

Well, thanks for trying.  :-)

  - Mike

[seer]

127.0.0.1 gives me this:
Server Error
The following error occurred:
[code=CANT_CONNECT_LOOPBACK] Cannot connect due to potential loopback problems

localhost gives me:
The page cannot be displayed[/b]

Try this;

tracert 127.0.0.1 in a CMD console, if you get more then 1 hop, you've got a problem, 1 I never seen before ;-)

Does your host file have a localhost entry ? Should be there as a standard (127.0.0.1 localhost)

And because another machine can acces the webpage by DNS, you pretty much excluded the webserver/apache as the problem..

[Jope]

Glaucus wrote:
Unless there's another location where I can check for a proxy, I am not using a proxy and never was.

No automatic configuration script either?

The messages you were getting seriously looked like proxy messages..

[seer]

The messages you were getting seriously looked like proxy messages..

But then, local addresses are not through a proxy or DNS server.. Ofcourse, IE must be told to do that by the proxy settings..

[Glaucus]

Okay, did the trace route:
$ tracert 127.0.0.1

Tracing route to localhost [127.0.0.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  localhost [127.0.0.1]

Trace complete.

Mike@mike-xp ~
$ tracert localhost

Tracing route to mike-xp [127.0.0.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  localhost [127.0.0.1]

Trace complete.

Mike@mike-xp ~
$ tracert mike

Tracing route to mike [192.168.1.100]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  mike [192.168.1.100]

Trace complete.


Incase you're wondering, I'm using Cygwin/Bash.

As for my hosts file, I trimmed it down to two entries:
127.0.0.1  localhost
192.168.1.100 mike

I then did an ipconfig /flushdns * ipconfig /displaydns:
$ ipconfig /displaydns

Windows IP Configuration

         mike
         ----------------------------------------
         Record Name . . . . . : mike
         Record Type . . . . . : 1
         Time To Live  . . . . : 602457
         Data Length . . . . . : 4
         Section . . . . . . . : Answer
         A (Host) Record . . . : 192.168.1.100


         1.0.0.127.in-addr.arpa
         ----------------------------------------
         Record Name . . . . . : 1.0.0.127.in-addr.arpa.
         Record Type . . . . . : 12
         Time To Live  . . . . : 602457
         Data Length . . . . . : 4
         Section . . . . . . . : Answer
         PTR Record  . . . . . : localhost


         100.1.168.192.in-addr.arpa
         ----------------------------------------
         Record Name . . . . . : 100.1.168.192.in-addr.arpa.
         Record Type . . . . . : 12
         Time To Live  . . . . : 602457
         Data Length . . . . . : 4
         Section . . . . . . . : Answer
         PTR Record  . . . . . : mike


         localhost
         ----------------------------------------
         Record Name . . . . . : localhost
         Record Type . . . . . : 1
         Time To Live  . . . . : 602457
         Data Length . . . . . : 4
         Section . . . . . . . : Answer
         A (Host) Record . . . : 127.0.0.1

Just get's stranger and stranger doesn't it?

And yes, no proxy, no startup script. It's is however set to Automatically detect settings.

  - Mike

[Glaucus]

Ummm....  I think I fixed it....  Boy do I feel silly now. I unchecked the Automatically detect settings button and all seems to be working fine now!!! So, umm...  I guess IE was detecting the settings all wrong, but I swear I've always had that checked. Strange. Oh well, it seems to be working now. On the plus side, I've learned a great deal about Windows networking! Thanks for all the help guys! :-D

  - Mike

[seer]

127.0.0.1 localhost
192.168.1.100 mike

Not sure if that is correct, you may want to try

127.0.0.1 localhost
127.0.0.1 mike

I'm running a webserver on my work PC at home, and only use the default host file.. But I don't know if Apache requires it or not (I just use IIS..)

I don't think it's a DNS error as your PC shouldn't need to access a DNS to find it's own DNS name.. Offcourse, you can always try to disable the NIC, do another DNS flush and try to it again with the NIC still disabled..