Re: localhost is all that will work

From: Jeff Cochran (jeff.nospam_at_zina.com)
Date: 12/30/04 

Date: Thu, 30 Dec 2004 18:41:59 GMT

Make sure you have the site configured for "All Unassigned" IP
addresses and are not using host headers at all.

Jeff

On Wed, 29 Dec 2004 07:21:02 -0800, "Pam Will"
<PamWill@discussions.microsoft.com> wrote:

>Thanks for the reply. To clarify some points... localhost and 127.0.0.1 work
>on the local system where IIS is installed but the IP of the system as well
>as the name of the system will not bring up the website.
>
>By external I meant people on the Internet. They cannot use the NATed IP
>address or the one assigned via my Internet provider. However, I think this
>is more an issue of the fact that I cannot even get it to work internally on
>my own network.
>
>We do have a Cisco PIX firewall that my Internet provider maintains who
>assures me everything is setup correctly -- that it's a misconfiguration that
>I've done with IIS or something else (i.e., DNS). Yet they have provided me
>with no help either. DNS appears to have the information correctly.
>
>Can you give me some more information on this cross over cable solution?
>
>When I turn off the show friendly HTTP errors, I actually get nothing back?
>Does that sound right?
>
>I also do not know what you mean by third party ISAPI filters. I've
>installed IIS 6.0 from Windows installation. I see ASP.net if that might be
>what you are referring to.
>
>Again, thank you for your help thus far. I hope my answers help you on
>finding a solution for this issue. Thanks!
>
>"Kristofer Gafvert" wrote:
>
>> Hello Pam,
>>
>> 400 Bad Request usually means that the client is sending a bad request,
>> and IIS informs the client that it will not process the request,
>> because it is malformed. So it is not really an IIS issue, but more of
>> a client sending requests that is wrong.
>>
>> You say that it is working on the local machine. You also say that it
>> works only when using localhost. This makes me believe that when you
>> use anything else on the local machine (the IP or domain name), the
>> request first goes to another machine, for example a proxy.
>>
>> You also say that this happens for all(!?) external clients. Does all
>> these clients have something in common? Do they pass any
>> machine/router/firewall/proxy before they get to the webserver?
>>
>> There seems to be something in between the external clients and the
>> webserver that is causing the Bad Request. You can verify this if you
>> attach a machine directly to the webserver (via a crossover cable) and
>> try to access the website. If it works, then something on the network
>> is causing troubles.
>>
>> Can you please also turn off "Show Friendly HTTP Errors" in a
>> webbrowser that fails, and then browse the website. Do you get any more
>> information about the problem?
>>
>> I would also like to know if you have installed any third-party ISAPI
>> filters. What happens if you disable these third-party ISAPI filters?
>>
>> I hope we can get a solution for this!
>>
>> --
>> Regards,
>> Kristofer Gafvert
>> www.ilopia.com
>>
>> Pam Will wrote:
>>
>> > I have a win 2003 server with IIS 6.0 installed. I'm trying to get
>> > to my website from other workstations in the network or from the
>> > outside but the only address that will work is to be on that server
>> > and type localhost...
>> >
>> > Other workstations on the domain cannot access using the computer
>> > name, the IP, and I cannot access with what should be it's external
>> > name.
>> >
>> > I receive a HTTP 400 Bad Request message.
>> >
>> > I have a Cisco firewall in place. Not sure if I'm missing something
>> > there.
>> >
>> > My ultimate goal is to use this as a Citrix system using NFuse but I
>> > figured I'd better make sure I can crawl before I can run.
>> >
>> > Any help, articles, etc. would be greatly appreciated. Thank you.
>>

Relevant Pages

  • RE: Problems with wsdl-generated proxy clients
    ... you can also run a debuggeragainst the webservices' IIS process to see whether you can get any exceptions. ... \par We have a web service client app we use internally. ... \par Looking at the IIS logs, I didn't even see the request in the log. ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: IIS 5.0 : howto disable direct file linking?
    ... There is no setting in IIS to disable direct file linking. ... requested URL is valid IIS will serve it as long as the client making the ... request has appropriate permissions to view the content. ...
    (microsoft.public.inetserver.iis.security)
  • Re: localhost is all that will work
    ... I've done with IIS or something else ... installed IIS 6.0 from Windows installation. ... > 400 Bad Request usually means that the client is sending a bad request, ...
    (microsoft.public.inetserver.iis)
  • Re: localhost is all that will work
    ... 400 Bad Request usually means that the client is sending a bad request, ... and IIS informs the client that it will not process the request, ... and then browse the website. ...
    (microsoft.public.inetserver.iis)
  • RE: Going Crazy asp
    ... Your first example runs for me in IE, while your second does not - as expected since neither my web service nor my local machine run IIS. ... Because you do know that client side VBScript is only supported in IE, ...
    (microsoft.public.scripting.wsh)
Quantcast