IIS7 - Host header / Default Document problems

I have a website that is housed in inetpub\wwwroot\mysite.
I have 2 sites listed in IIS7, each accessing the files in mysite, just each a bit differently.

mysite1 has a hostheader of mysite1.myorg.com, the Physical Path is C:\inetpub\wwwroot and a default document of logon.asp
mysite2 has a hostheader of mysite2.myorg.com and the Physical Path is C:\inetpub\wwwroot\mysite and a default document of logon2.asp

I have added local DNS entrys so both point to the proper IP.

When I go to mysite1.myorg.com/mysite I am taken to the logon page for mysite2.myorg.com.

I can go to mysite1.myorg.com/mysite/logon.asp and logon fine, but cant figure out why, even with host headers and a default document defined, that mysite1.myorg.com/mysite wont take me to the proper logon page.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

WadskiIT DirectorCommented:
Is the IP address each website listening on the same IP address?  I am guessing the mysite2 one is set to '(All Unassigned)' and is above the mysite1 .
if you change this to the same IP as the first it will work.
rdevitisAuthor Commented:
Thanks for the quick feedback, unfortunately though, both sites are set to the same IP.
WadskiIT DirectorCommented:
You've probably done this many times already but have you stopped and started the service?  You must do this as the changes don't commit until the service has been restarted.

10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

rdevitisAuthor Commented:
I did, and just did it again to make sure. No go. Thats what make this so much fun. Just as some background, I did have this working fine in IIS6 on a 2003 server. This is now IIS7 on a 2008 box, if I didnt mention that before.
WadskiIT DirectorCommented:
Can you check that the host headers for mysite1 don't exist in the container for mysite2?
Can you also temporarily remove  the mysite2 site and see what happens with the request to mysite1?

rdevitisAuthor Commented:
Can you check that the host headers for mysite1 don't exist in the container for mysite2?
Not exactly sure what you mean
rdevitisAuthor Commented:
It appears that there was some inheritance on default website which was overriding the default document settings I had on the sub sites. Very odd, dont remmeber it working that way in IIS6. Best part is I had the default site stopped.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.