Website on W2003 server with IIS 6.0.

I am kind of new to this, I have a website on a W2003 server.
Description: the World of Dance
IP address: 192.168.1.9
TCP port: 8002
Connection Timeout 120 sec and logging enabled MS IIS LOG FILE FORMAT.

I can access site via D:\Dance\Index.html, but in browser error: HTTP 400
bad request.

More information

This error (HTTP 400 Bad Request) means that Internet Explorer was able to
connect to the web server, but the webpage could not be found because of a
problem with the address.

For more information about HTTP errors, see Help.


Part of logfile below.
2007-07-25 12:51:03 217.105.136.66 5836 192.168.1.9 8002 HTTP/1.1 GET
/index.html 400 - Hostname -
2007-07-25 12:51:09 217.105.136.66 5837 192.168.1.9 8002 HTTP/1.1 GET
/index.html 400 - Hostname -
2007-07-25 12:51:56 217.105.136.66 5838 192.168.1.9 8002 HTTP/1.1 GET
/index.html 400 - Hostname -
2007-07-25 12:52:53 127.0.0.1 3168 127.0.0.1 8002 HTTP/1.1 GET /index.html
400 - Hostname -
2007-07-25 12:55:24 192.168.1.9 3262 192.168.1.9 8002 HTTP/1.1 GET
/index.html 400 - Hostname -

Any idea how to solve this?

RE: Website on W2003 server with IIS 6.0.

On server itself, problem is solved. However from client still nog connection.
browsing in internet explorer to http://82.72.97.25:8002 gives invalid
request. (400). I have forwarded this port on the router. Any ideas?


"MGBodifee" wrote:

> I am kind of new to this, I have a website on a W2003 server.
> Description: the World of Dance
> IP address: 192.168.1.9
> TCP port: 8002
> Connection Timeout 120 sec and logging enabled MS IIS LOG FILE FORMAT.
>
> I can access site via D:\Dance\Index.html, but in browser error: HTTP 400
> bad request.
>
> More information
>
> This error (HTTP 400 Bad Request) means that Internet Explorer was able to
> connect to the web server, but the webpage could not be found because of a
> problem with the address.
>
> For more information about HTTP errors, see Help.
>
>
> Part of logfile below.
> 2007-07-25 12:51:03 217.105.136.66 5836 192.168.1.9 8002 HTTP/1.1 GET
> /index.html 400 - Hostname -
> 2007-07-25 12:51:09 217.105.136.66 5837 192.168.1.9 8002 HTTP/1.1 GET
> /index.html 400 - Hostname -
> 2007-07-25 12:51:56 217.105.136.66 5838 192.168.1.9 8002 HTTP/1.1 GET
> /index.html 400 - Hostname -
> 2007-07-25 12:52:53 127.0.0.1 3168 127.0.0.1 8002 HTTP/1.1 GET /index.html
> 400 - Hostname -
> 2007-07-25 12:55:24 192.168.1.9 3262 192.168.1.9 8002 HTTP/1.1 GET
> /index.html 400 - Hostname -
>
> Any idea how to solve this?

Re: Website on W2003 server with IIS 6.0.

On Jul 25, 6:50 am, MGBodifee
wrote:
> On server itself, problem is solved. However from client still nog connection.
> browsing in internet explorer tohttp://82.72.97.25:8002gives invalid
> request. (400). I have forwarded this port on the router. Any ideas?
>
>
>
> "MGBodifee" wrote:
> > I am kind of new to this, I have a website on a W2003 server.
> > Description: the World of Dance
> > IP address: 192.168.1.9
> > TCP port: 8002
> > Connection Timeout 120 sec and logging enabled MS IIS LOG FILE FORMAT.
>
> > I can access site via D:\Dance\Index.html, but in browser error: HTTP 400
> > bad request.
>
> > More information
>
> > This error (HTTP 400 Bad Request) means that Internet Explorer was able to
> > connect to the web server, but the webpage could not be found because of a
> > problem with the address.
>
> > For more information about HTTP errors, see Help.
>
> > Part of logfile below.
> > 2007-07-25 12:51:03 217.105.136.66 5836 192.168.1.9 8002 HTTP/1.1 GET
> > /index.html 400 - Hostname -
> > 2007-07-25 12:51:09 217.105.136.66 5837 192.168.1.9 8002 HTTP/1.1 GET
> > /index.html 400 - Hostname -
> > 2007-07-25 12:51:56 217.105.136.66 5838 192.168.1.9 8002 HTTP/1.1 GET
> > /index.html 400 - Hostname -
> > 2007-07-25 12:52:53 127.0.0.1 3168 127.0.0.1 8002 HTTP/1.1 GET /index.html
> > 400 - Hostname -
> > 2007-07-25 12:55:24 192.168.1.9 3262 192.168.1.9 8002 HTTP/1.1 GET
> > /index.html 400 - Hostname -
>
> > Any idea how to solve this?- Hide quoted text -
>
> - Show quoted text -


Please report the Host header bindings that you have configured the
website to accept.

The 400 Hostname error means that you failed to configure the website
to accept the host header of the forwarded request.

What is the host header of the forwarded request? You need to
determine that from the router's documentation since it is responsible
for the forwarding.

If you cannot figure out the host header that the router forwards
with, you may want to configure the IIS website to accept any request
over the forwarded port, which should solve your issue. However, if
you need to run multiple websites over that forwarded port, then you
MUST figure out the host header that the router is forwarding with.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: Website on W2003 server with IIS 6.0.

Dear David,

Reïnstalling IIS solved the problem. Works fine now. Thanks anyway.

"David Wang" wrote:

> On Jul 25, 6:50 am, MGBodifee
> wrote:
> > On server itself, problem is solved. However from client still nog connection.
> > browsing in internet explorer tohttp://82.72.97.25:8002gives invalid
> > request. (400). I have forwarded this port on the router. Any ideas?
> >
> >
> >
> > "MGBodifee" wrote:
> > > I am kind of new to this, I have a website on a W2003 server.
> > > Description: the World of Dance
> > > IP address: 192.168.1.9
> > > TCP port: 8002
> > > Connection Timeout 120 sec and logging enabled MS IIS LOG FILE FORMAT.
> >
> > > I can access site via D:\Dance\Index.html, but in browser error: HTTP 400
> > > bad request.
> >
> > > More information
> >
> > > This error (HTTP 400 Bad Request) means that Internet Explorer was able to
> > > connect to the web server, but the webpage could not be found because of a
> > > problem with the address.
> >
> > > For more information about HTTP errors, see Help.
> >
> > > Part of logfile below.
> > > 2007-07-25 12:51:03 217.105.136.66 5836 192.168.1.9 8002 HTTP/1.1 GET
> > > /index.html 400 - Hostname -
> > > 2007-07-25 12:51:09 217.105.136.66 5837 192.168.1.9 8002 HTTP/1.1 GET
> > > /index.html 400 - Hostname -
> > > 2007-07-25 12:51:56 217.105.136.66 5838 192.168.1.9 8002 HTTP/1.1 GET
> > > /index.html 400 - Hostname -
> > > 2007-07-25 12:52:53 127.0.0.1 3168 127.0.0.1 8002 HTTP/1.1 GET /index.html
> > > 400 - Hostname -
> > > 2007-07-25 12:55:24 192.168.1.9 3262 192.168.1.9 8002 HTTP/1.1 GET
> > > /index.html 400 - Hostname -
> >
> > > Any idea how to solve this?- Hide quoted text -
> >
> > - Show quoted text -
>
>
> Please report the Host header bindings that you have configured the
> website to accept.
>
> The 400 Hostname error means that you failed to configure the website
> to accept the host header of the forwarded request.
>
> What is the host header of the forwarded request? You need to
> determine that from the router's documentation since it is responsible
> for the forwarding.
>
> If you cannot figure out the host header that the router forwards
> with, you may want to configure the IIS website to accept any request
> over the forwarded port, which should solve your issue. However, if
> you need to run multiple websites over that forwarded port, then you
> MUST figure out the host header that the router is forwarding with.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>