Re: localhost is all that will work
From: Krim140 (Krim140_at_discussions.microsoft.com)
Date: 12/30/04
- Next message: AndrewXPP: "Re: Attempt to add IIS 5.1 component and fail."
- Previous message: David Wang [Msft]: "Re: IIS 6 aspx"
- In reply to: Pam Will: "Re: localhost is all that will work"
- Next in thread: David Wang [Msft]: "Re: localhost is all that will work"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Dec 2004 20:19:02 -0800
"Pam Will" wrote:
> The URL to the outside world is mictrix3.memberins.com. It still is the 400
> Bad Request message that I receive here as well.
>
> ISAPI Filters tab -- ASP.NET_1.1.4322.2032 with a low priority.
>
> I believe the only thing that is between us and the outside world is our
> Cisco PIX firewall which again my Internet provider assured me was properly
> configured to accept the request. However, I don't see anything on the IIS
> logs that would indicate an attempt is even getting there so the best bet
> would be something is wrong the the PIX configuration?
>
> "Kristofer Gafvert" wrote:
>
> > Hello,
> >
> > This is what is happening.
> >
> > - The client looks up the IP of the domain name (Works, since the
> > webserver answers)
> > - The client opens a connection to the webserver (works, since the
> > webserver answers)
> > - The client writes an HTTP data stream to the webserver (works, this
> > is the request)
> > - The webserver answers the request, that the request was malformed.
> >
> > If this happens for all your clients on the Internet, then it is likely
> > that the problem is somewhere on the network and/or webserver. These
> > clients do not have any proxy in common (which can be the case if they
> > all are located on the same subnet), and they are not using the same
> > client (they are not in a controlled environment).
> >
> > So, we can rule out that the problem is the client.
> > We can also rule out that the problem is on the webserver, unless it
> > behaves differently depending on what IP was requested (if multihomed).
> >
> > > 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.
> >
> > I assume that the name is the domain name, right? When you do this, how
> > is the connection made? Does it go thru the firewall? Your webserver
> > must find the external IP, and it is not part of your local network, so
> > the connection need to made in another way. If this succeeds, depends
> > on the router. (so in some occasions, you will never be able to connect
> > to the external IP from the webserver itself, because it cannot find
> > the machine).
> >
> > So for simplicity, please do all testing accessing the external IP from
> > outside your local network.
> >
> > > 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.
> >
> > When you say that that it does not work for users on the Internet, what
> > does it mean that it does not work? Is it still the 400 Bad Request
> > message? Or is it simply that they cannot find the server?
> >
> > If the clients get a "400 Bad Request", they can find the webserver
> > (since the message is generated by the webserver).
> >
> > I'm trying to figure out if we see multiple problems, or "only" have
> > one issue.
> >
> > > 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.
> >
> > If we are talking about the "400 Bad Request" problem all the time,
> > then it cannot be DNS. It can still be the webserver, but i doubt.
> >
> > > Can you give me some more information on this cross over cable
> > > solution?
> >
> > I thought that your "external clients" was on the same Intranet. If
> > they are on Internet, accessing the website from different parts of the
> > world, then we do not need to do this.
> >
> > > 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.
> >
> > In IIS Manager, right click the website and click Properties. Click on
> > the ISAPI Filters tab. Do you find any filters listed?
> >
> > Is this website accessible for us via the Internet? Can you give us the
> > URL (or send me an email if you do not want to post it here). I know
> > that i do not have anything that can modify the HTTP header, so i would
> > like to test it from here, if possible.
> >
> > To sum up,
> >
> > It works on the local webserver, if you access it via localhost or
> > 127.0.0.1 (localhost will translate to 127.0.0.1 so that is no
> > surprise). It does however not work when you access the website using
> > its external IP. I *think* (i cannot know) that when you access it
> > using the external IP, the request will pass thru something (a proxy,
> > or something else), so that the request is made the same as the
> > external clients. This would explain that you cannot access the website
> > from the webserver when using the external IP.
> >
> > All external clients gives a "400 Bad Request" message.
> >
> > To me (right now), it sounds like something in between the webserver
> > and the clients modifies the HTTP header, causing this problem.
> >
> > Can you check the settings on the webserver if it uses any proxy?
> >
> >
> > --
> > Regards,
> > Kristofer Gafvert
> > www.ilopia.com
> >
> > Pam Will 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.
> > > >
> >
Hi Pam,
Did you make any changes to the default website?
Did you change the default website to a different one ?
Did you change the IP address assignment *All Unassigned* to some thing
different ?
Hope the above directives could be of some help.
- Next message: AndrewXPP: "Re: Attempt to add IIS 5.1 component and fail."
- Previous message: David Wang [Msft]: "Re: IIS 6 aspx"
- In reply to: Pam Will: "Re: localhost is all that will work"
- Next in thread: David Wang [Msft]: "Re: localhost is all that will work"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
