IIS 5 & IIS 6
Host header name trouble
Last post Jun 06, 2008 08:57 AM by tomkmvp
Jun 05, 2008 03:44 PM|dzima|LINK
I'm having a trouble with the host header names that I cannot solve.
I have a Windows Server 2003 with IIS running on it, and multiples site with the following configuration:
SITE -> (HOST HEADERS)
Site A -> (default IP:siteA.com:80, default IP:www.siteA.com:80)
Site Ax -> (default IP:x.siteA.com:80)
Site B -> (default IP:www.siteB.com:80)
Site C -> (default IP:www.siteC.com:80)
Site A is the Default site.
I have 4 computers that can access each site from IE 7 and IE 6, but there are some computers (not all) outside of my business that cannot access Site Ax. These computers have IE 6 and nothing appears to be wrong with the HTTP request (since I check the
iis logs and the host header is recieved OK for each site request).
So why I can access site Ax from some computers and cannot acces from some others?
Thanks for the time.
Jun 05, 2008 08:07 PM|tomkmvp|LINK
What does "cannot access" mean exactly? What happens if you ping those names from the "non working" computers?
Jun 05, 2008 08:20 PM|dzima|LINK
It means that when these computers request the Site Ax, the IE get other site. In this case, the IE gets the Default site (Site A).
The ping goes OK. It resolve the name succesfully.
I didn't say it, but all the sites share same IP address.
I hope these help a bit more.
Jun 06, 2008 05:37 AM|Rovastar|LINK
Somewhere you must be pointing to wrong place either DNS, which you think you have not got, or some redirection in IIS/code.
Although it doesn't look from what you said like a DNS problem. please check with nslookup,
www.dnsstuff.com running the dns report on your problem sub-domain might highlight issues.
As you said:
(since I check the iis logs and the host header is received OK for each site request).
This implies that it is a redirection in code/IIS. If I understand you correctly they is an entry in the IIS log files for your sub-domain x.sitea.com.
So what do the logs say? Please post them here. What is the http status of these request? Is it always one page? What is the code of that page - a redirect based on browser type would be too easy would it but have a look at the code.
Is there a corresponding entry in the log files for the top domain sitea.com? What page (referrer) did they come from?
With this information you can piece together what is happening?
Also you suspect IE versions as a potential problem.
How far have you looked into this? I think this is unlikely but lets see if we can troubleshoot that.
Do other browser firefox, IE8 beta, etc have this problem?
Is it always that IE6 fail and IE7 is ok? You imply the sub-domain is viewable for us on the outside post a link. I have access to IE6
What other user agent properties do they have, OS version, etc? e.g. maybe 2000 and XP pre-SP2 with IE6 fail but other browsers are ok on these OS and IE6 is ok on XP SP2 or above. (ummh just thought I don't know the useragent string for new XP SP3 I presume
it will be SV2 entry)
You can gain all this information from the IIS logs.
Could you install IE6 on your machine and see if it is happening? Or spoof the user agent string to imply you have IE6. That way it will function as IE6 when connecting to the server.
Do the ones that fail have any other pattern?
I hope these questions help, there are still a lot of things to try to narrow down the problem areas.
Jun 06, 2008 08:57 AM|tomkmvp|LINK
... what's strange though is it works for some clients and not for others. If IIS was "broken" I would think it wouldn't work for anyone, so I suspect a client issue somehow ...