Loopback address does not work with the IE option Automatically detect settings

[dneiding]

If you are using WB and have your IE setting Automatically detect settings (from the IE Tools menu choose Internet Options, Connection tab, LAN Settings button) try this, go to http://localhost. If you do not have a Web server (IIS, Apache) on your computer you should get a page cannot be displayed error. If a Web server you will get the Web server’s help screen. Now, go to http://127.0.0.1. Ideally, you should get the same results. After all, localhost and 127.0.0.1 are the same. However, on my machine, when I go to http://127.0.0.1 I get forwarded to http://12.213.91.XXX/ (this is my WB modems IP) and get a Network Error (tcp_error) page.

If Automatically detect settings is off everything works fine…but I need this setting on in order to ensure proper authentication to some secure Web sites.

This behavior poses a real problem if you have software installed on your computer that uses 127.0.0.1; like Google Desktop Search for example. I don’t understand why the WB modem is not smart enough to know that the loopback IP should be resolved on the LAN and not try to go to the Internet. Or maybe it’s a Linksys router issue.

Any ideas?

[ProComm]

I'll play devil's advocate for a minute - in case I'm not fully understanding what your getting at.

Why use the automatic settings over entering the proxy directly and using the bypass feature for your local addresses?

[dneiding]

I'll play devil's advocate for a minute - in case I'm not fully understanding what your getting at.

Why use the automatic settings over entering the proxy directly and using the bypass feature for your local addresses?

I am using the Automatically detect settings option because when I don’t there a some secure Web sites that I cannot get to when behind WB. For example, my company has a Web page for internal use that is secured by Windows Authentication. If I do not use Automatically detect settings then I cannot access this site.

I called NRTC support today and they tried to help me with this problem. I told them it was up to them, they could either fix the 127.0.0.1 problem when Automatically detect setting is checked or fix the problem with Web sites that require Windows Authentication when unchecked; personally, I think the 127.0.0.1 issue is more straight forward.

Keep in mind that this behavior is only when behind WB. When I take my laptop to a hotel or a client’s office I can get to everything just fine, regardless of the automatically detect settings status.

[ProComm]

Ok - now I get it. They are using WinAuth instead of BasicAuth in IIS so that the user/pass isn't sent in the clear. Have same problems on DiRECWAY with similar scenario for remote users doing the same thing - crystal clear - I get it.

I know it's a PIA, our remote users have to toggle back and forth between auto and direct proxy settings.

Love the ultimatum you gave; but hope your not holding your breath!