Interesting. I need to publish a Sharepoint site set to "anonymous" access.

Then I go to the respective server. In IIS Management console, I assign a
specific IP address to such site (that means I have total of two IP addresses
assigned to the respective NIC).

Then I set the site to anonymous access.
I set a "host header"=extmysite, port=80, IP=1.1.1.1

Then from a client in the corporate network, if I do:
http://extmysite.mydomain.com it works perfectly and I get to the site.
However, if I do:
http://1.1.1.1
If fails "400-bad request". Message is shown below.

Any idea why it is failing if I try to hit the IP address ??

The page cannot be found
The page you are looking for might have been removed, had its name changed,
or is temporarily unavailable.

--------------------------------------------------------------------------------

Please try the following:

If you typed the page address in the Address bar, make sure that it is
spelled correctly.

Open the 1.1.1.1 home page, and then look for links to the information you
want.
Click the Back button to try another link.
Click Search to look for information on the Internet.



HTTP 400 - Bad Request
Internet Explorer

Re: Why this error "400-Bad request" when trying to hit the IP address by Egbert

Egbert
Sun Oct 30 05:13:44 CST 2005

Maybe the RFC (I'm not that TCP/IP expert) does not allow this address
range...
Try something that is really local in the range

10.0.0.x
or 192.168.1.x

--
compatible web farm Session replacement for Asp and Asp.Net
http://www.nieropwebconsult.nl/asp_session_manager.htm

"Marlon Brown" <MarlonBrown@discussions.microsoft.com> wrote in message
news:D1E9F823-8B8A-4AEC-8B22-EFCE0280E03C@microsoft.com...
> Interesting. I need to publish a Sharepoint site set to "anonymous"
> access.
>
> Then I go to the respective server. In IIS Management console, I assign
> a
> specific IP address to such site (that means I have total of two IP
> addresses
> assigned to the respective NIC).
>
> Then I set the site to anonymous access.
> I set a "host header"=extmysite, port=80, IP=1.1.1.1
>
> Then from a client in the corporate network, if I do:
> http://extmysite.mydomain.com it works perfectly and I get to the site.
> However, if I do:
> http://1.1.1.1
> If fails "400-bad request". Message is shown below.
>
> Any idea why it is failing if I try to hit the IP address ??
>
> The page cannot be found
> The page you are looking for might have been removed, had its name
> changed,
> or is temporarily unavailable.
>
> --------------------------------------------------------------------------------
>
> Please try the following:
>
> If you typed the page address in the Address bar, make sure that it is
> spelled correctly.
>
> Open the 1.1.1.1 home page, and then look for links to the information you
> want.
> Click the Back button to try another link.
> Click Search to look for information on the Internet.
>
>
>
> HTTP 400 - Bad Request
> Internet Explorer
>


Re: Why this error "400-Bad request" when trying to hit the IP address by Kristofer

Kristofer
Sun Oct 30 06:59:58 CST 2005

Hello,

You say that you configured the website with a host header of extmysite.
But when you access the website by using the IP, either the IP is sent as
host header, or no host header at all is sent. This means that your
request did not match the configuration of IIS (where you specified a host
header value different than the one that was sent), and IIS replies with a
400 - Bad Request.

So with the information that is given in your post, the 400 Bad Request is
expected.


(I know nothing about sharepoint and cannot tell if this is also a
sharepoint issue somewhere)

--
Regards,
Kristofer Gafvert (IIS MVP)
http://www.gafvert.info/iis/ - IIS Related Info


Marlon Brown wrote:

>Interesting. I need to publish a Sharepoint site set to "anonymous" access.
>
>Then I go to the respective server. In IIS Management console, I assign a
>specific IP address to such site (that means I have total of two IP
>addresses
>assigned to the respective NIC).
>
>Then I set the site to anonymous access.
>I set a "host header"=extmysite, port=80, IP=1.1.1.1
>
>Then from a client in the corporate network, if I do:
>http://extmysite.mydomain.com it works perfectly and I get to the site.
>However, if I do:
>http://1.1.1.1
>If fails "400-bad request". Message is shown below.
>
>Any idea why it is failing if I try to hit the IP address ??
>
> The page cannot be found
>The page you are looking for might have been removed, had its name changed,
>or is temporarily unavailable.
>
>--------------------------------------------------------------------------------
>
>Please try the following:
>
>If you typed the page address in the Address bar, make sure that it is
>spelled correctly.
>
>Open the 1.1.1.1 home page, and then look for links to the information you
>want.
>Click the Back button to try another link.
>Click Search to look for information on the Internet.
>
>
>
>HTTP 400 - Bad Request
>Internet Explorer

Re: Why this error "400-Bad request" when trying to hit the IP address by Ratatooie

Ratatooie
Mon Oct 31 11:11:04 CST 2005


"Kristofer Gafvert [MVP]" <kgafvert@NEWSilopia.com> wrote in message
news:xn0e93xx8eqdpy9002@news.microsoft.com...
> Hello,
>
> You say that you configured the website with a host header of extmysite.
> But when you access the website by using the IP, either the IP is sent as
> host header, or no host header at all is sent. This means that your
> request did not match the configuration of IIS (where you specified a host
> header value different than the one that was sent), and IIS replies with a
> 400 - Bad Request.
>
> So with the information that is given in your post, the 400 Bad Request is
> expected.
>
>

Making the binding in IIS unique to that virtual web should make it work.

I.e. take 1.1.1.1 off the default web by switching from "Any Address" to the
other IP, likewise from any other virtual web.

IIS only knows how to respond to an IP address if there is only _one_
virtual site trying to respond on that address.