Host Header problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Chris - 29 Dec 2005 14:05 GMT

I am trying to use the host header config within IIS 6 to indentify our
intranet site by a different name. Right now you can get to the intranet
site by typing: \\servername\intranet. I've added the host header info to
have it point to the ip address 192.168.2.5 (port 80) with a new name of
fred.domainname.com. It appears to be working for one users (who is in
charge of the website and she just types Fred in the address bar of IE) but
when I try it, I get a web page that says "You are not authorized to view
this page." Can't figure out why. I have "God Rights" on everything....

Any insight would be appreciated.

Chris

Reply to this Message

Christopher Reed - 29 Dec 2005 14:09 GMT

Check the document settings and make sure that your default document is
among the list.

Signature

Christopher A. Reed
"The oxen are slow, but the earth is patient."

>I am trying to use the host header config within IIS 6 to indentify our
> intranet site by a different name. Right now you can get to the intranet
[quoted text clipped - 10 lines]
>
> Chris

Reply to this Message

Chris - 29 Dec 2005 15:27 GMT

I assume you mean the documents tab on the Default Web Site properties page.
If so, I did check and it is listed under "enable default content page." If
this is different, please let me know.

Thanks for the quick response.

Chris

> Check the document settings and make sure that your default document is
> among the list.
[quoted text clipped - 12 lines]
> >
> > Chris

Reply to this Message

Ratatooie - 29 Dec 2005 16:30 GMT

Usually the default document missing and "browse folders" off results in the
"Browsing folders is prohibited" error (a specific access denied error).

You need to match the IP with DNS either via a hosts file on each computer,
or via your DNS server on your network. Host headers look for traffic with
that particular combination and then use the corresponding virtual web to
respond.

You can't just type "fred" if it is "fred.domainname.com". You MUST type
"fred.domainname.com".

But it sounds like you don't have the DNS part done yet, so the request is
not seen by the web server properly.

>I assume you mean the documents tab on the Default Web Site properties
>page.
[quoted text clipped - 27 lines]
>> >
>> > Chris

Reply to this Message

Kristofer Gafvert - 29 Dec 2005 16:52 GMT

Hello,

Can you please check the IIS log file (located in
C:\Windows\System32\LogFiles\W3CNNN where NNN is the id number of the
website), and paste the log entry for a failed request here.

Make sure you are logging sc-status, sc-substatus and sc-win32-status, as
we need that to be able to help.

If you cannot find a log entry that matches your request, it may be
because your request is not getting to the webserver (which means that you
have a DNS issue), and "You are not authorized to view this page" is
returned from another machine.

Signature

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

>I am trying to use the host header config within IIS 6 to indentify our
>intranet site by a different name. Right now you can get to the intranet
[quoted text clipped - 8 lines]
>
>Chris

Reply to this Message

Chris - 29 Dec 2005 18:28 GMT

Here is the logfile..... sorry if you didn't want the entire thing. I'm
pretty sure I have DNS setup properly (as asked by Ratatooie.....).

Thanks again.

#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2005-12-29 16:53:59
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port
cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2005-12-29 16:53:59 W3SVC72964590 172.16.10.5 GET /home.asp - 80 -
172.16.109.164 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 403 1 0
2005-12-29 16:54:08 W3SVC72964590 172.16.10.5 GET /home.asp - 80 -
172.16.109.164 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 403 1 0
2005-12-29 16:54:13 W3SVC72964590 172.16.10.5 GET /home.asp - 80 -
172.16.109.164 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 403 1 0
2005-12-29 16:54:20 W3SVC72964590 172.16.10.5 GET /intranet - 80 -
172.16.109.164 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 404 0 2
2005-12-29 16:54:25 W3SVC72964590 172.16.10.5 GET /intranet - 80 -
172.16.109.164 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 404 0 2
2005-12-29 16:54:28 W3SVC72964590 172.16.10.5 GET /intranet - 80 -
172.16.109.164 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 404 0 2
2005-12-29 16:55:15 W3SVC72964590 172.16.10.5 GET /home.asp - 80 -
172.16.109.164 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 403 1 0
2005-12-29 17:00:38 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:00:46 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:00:51 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:01:11 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:01:25 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:01:35 W3SVC72964590 172.16.10.5 GET /intranet - 80 -
172.16.109.164 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 404 0 2
2005-12-29 17:03:03 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:03:23 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:03:33 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:04:53 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:04:56 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:04:57 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:05:03 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:05:06 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:05:19 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:05:29 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:05:31 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2005-12-29 17:41:15
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port
cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2005-12-29 17:41:15 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.249

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:41:32 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.249

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:41:41 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.249

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
2005-12-29 17:42:06 W3SVC72964590 172.16.10.5 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.249

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2005-12-29 17:53:29
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port
cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2005-12-29 17:53:29 W3SVC72964590 172.16.10.40 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.175

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.
NET+CLR+2.0.50727) 500 0 0
2005-12-29 17:55:28 W3SVC72964590 172.16.10.40 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.175

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.
NET+CLR+2.0.50727) 500 0 0
2005-12-29 17:59:19 W3SVC72964590 172.16.10.40 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.10.40

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.
NET+CLR+2.0.50727) 500 0 0
2005-12-29 18:10:04 W3SVC72964590 172.16.10.40 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.175

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.
NET+CLR+2.0.50727) 500 0 0
2005-12-29 18:11:09 W3SVC72964590 172.16.10.40 OPTIONS / - 80 -
172.16.109.175 Microsoft-WebDAV-MiniRedir/5.1.2600 200 0 0
2005-12-29 18:11:09 W3SVC72964590 172.16.10.40 PROPFIND /c$ - 80 -
172.16.109.175 Microsoft-WebDAV-MiniRedir/5.1.2600 501 0 64
2005-12-29 18:11:09 W3SVC72964590 172.16.10.40 PROPFIND /c$ - 80 -
172.16.109.175 Microsoft-WebDAV-MiniRedir/5.1.2600 501 0 0
2005-12-29 18:11:09 W3SVC72964590 172.16.10.40 PROPFIND /c$ - 80 -
172.16.109.175 Microsoft-WebDAV-MiniRedir/5.1.2600 501 0 0
2005-12-29 18:11:09 W3SVC72964590 172.16.10.40 PROPFIND /c$ - 80 -
172.16.109.175 Microsoft-WebDAV-MiniRedir/5.1.2600 501 0 0
2005-12-29 18:11:09 W3SVC72964590 172.16.10.40 PROPFIND /c$ - 80 -
172.16.109.175 Microsoft-WebDAV-MiniRedir/5.1.2600 501 0 0
2005-12-29 18:11:16 W3SVC72964590 172.16.10.40 OPTIONS / - 80 -
172.16.109.175 Microsoft-WebDAV-MiniRedir/5.1.2600 200 0 0
2005-12-29 18:15:35 W3SVC72964590 172.16.10.40 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0
#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2005-12-29 18:21:52
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port
cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2005-12-29 18:21:52 W3SVC72964590 172.16.10.40 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 64
2005-12-29 18:21:52 W3SVC72964590 172.16.10.40 GET /home.asp

|71|80040e14|Line_1:_Incorrect_syntax_near_')'. 80 - 172.16.109.164

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 0

> Hello,
>
[quoted text clipped - 22 lines]
> >
> >Chris

Reply to this Message

Kristofer Gafvert - 29 Dec 2005 19:33 GMT

Hi,

In your log file i see three different status codes: 403.1, 404.0 and 500.
None of these gives "You are not authorized to view this page".

The 403.1 error indicates that execute access is denied. This is a setting
in IIS that is not dependent on the user (so you, and another user cannot
see different behavior). This status code does however only show up a few
times in the beginning of the log, is it possible that this was resolved
later?

The 500 error code indicates an error on the ASP page. The code (your ASP
code) may make a difference between users, so it is possible that the page
works for one user, but not for another. It is however unlikely, and would
not give the error message you see in your browser.

I cannot at this moment tell why you have 404 for a /intranet request. If
no such file is found, it should generate a "courtesy redirect"[1], and
the status code should be 301. I don't think however that this is related
to your issue.

Just to clarify, the page you are trying to browse (and that gives you the
"You are not authorized to view this page") is home.asp?

Can you please verify that the time in the log is the same as when you
tried to browse the page. Because so far, the log file does not match the
error you see, hence i believe that the error message you see is not
coming from this server. And you did check the right log (so you did not
mix up the website IDs)?

[1]
http://support.microsoft.com/kb/298408/EN-US/

Signature

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

>Here is the logfile..... sorry if you didn't want the entire thing. I'm
>pretty sure I have DNS setup properly (as asked by Ratatooie.....).
[quoted text clipped - 168 lines]
>>>
>>>Chris

Reply to this Message

Chris - 29 Dec 2005 20:32 GMT

Kristofer,

I really appreciate your time in looking at this. Some of the errors have
been resolved because I was doing some troubleshooting when these were
generated. I did take care of the "access denied" error but in any syntax,
when I type fred.doamainname.com, I get a page that says... The Page cannot
be found, HTTP 400 - Bad Request. Also, I changed the ip address to another
address, so that I can have seperate addresses for each website (future will
have this server hosting many websites)... might make it easier to
administor.

Yes, accessing home.asp and I'm not sure on the time on the logfile. I
noticed it was a much later time then when I accessed the site. The server
time is correct but not sure why the logfile is a different time.

Chris

> Hi,
>
[quoted text clipped - 205 lines]
> >>>
> >>>Chris

Reply to this Message

Kristofer Gafvert - 29 Dec 2005 21:54 GMT

Hi,

400 - Bad Request can happen if there is no website associated with the
host name.

When you created the website, did you specify a host name? Does this match
the one you use (fred.domainname.com)?

Go into the properties of this website, and on the "Web Site" tab click
the Advanced button. Does the identities of the website match what you use
when accessing the website (IP, port and host header, the host header can
be empty if you use separate IPs for each website)?

IIS logs (by default) in GMT time (as per the standard), and that can
explain the time difference.

Signature

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

>Kristofer,
>
[quoted text clipped - 239 lines]
>>>>>
>>>>>Chris

Reply to this Message