Host headers not working

I have several web sites working on my server and they are currently all working on differant ports - this will change when I get the Host headers working.

Note that web names I use are not real but are shortened from their real names.

www.james.com (default) and www.emma.com are both at godaddy and forwarded to 58.105.224.107 (my real IP address) with no port numbers.

Side note : I have 2 other web domains forwarded on from godaddy with port numbers and they work fine.

If I type in james.com I get the right web page, type in emma.com and I goto james.com. So I read Microsoft help and learn about host headers (and done a google search).
I give both web sites a host header but then both come back with a 'page not found' error. I delete the host header for james.com and james.com works fine again, I try www.james.com as the host header and it doesn't work, I try james.com as the header and it doesn't work - I delete the host header and james.com works fine.

Where have I gone wrong?

On further investigation I have stopped james.com and only had emma.com working on port 80.
I have set up the host header as www.emma.com and I get a 'Invalid hostname' error.

Hi,
been having similar issue i suppose, not to keen on the whole setup or what IIS does behind scenes exactly so im having issues troubleshooting.

Problem, people can no longer access website served from my wwwroot folder through IIS.

Past, ran webserver for years problem free, this problem occured all of a sudden, i did not change any IIS or system settings. I have not installed anything new except Sygate firewall which I removed via add/remove programs.

I can access my sites from the host machine and from another computer in my home via the routered network.

My system sits in the DMZ of the router, always has.

The IP set in IIS matches the one given by the router.
My DNS etc is always updated with my IP and double checked, it looks normal. (no-ip.com) Great service.

Windows firewall is disabled, I use AntiVIR for malware protection, tried disabling it, no change.

Full router/modem/comp reset did nothing. Checked for IP change after, all normal.

Netstat returns the following,
TCP localhost:18350 ESTABLISHED
TCP localhost:1450 ESTABLISHED
TCP 192.168.2.1:1050 CLOSE_WAIT
TCP 192.168.2.1:1052 CLOSE_WAIT
TCP 192.168.2.1:1053 CLOSE_WAIT

No idea really if that matters. Shouldnt port 80 be listening?
I have no idea about these things at this level, though I am learning more and more as I TRY to troubleshoot.

Did installing Sygate suddendly disable a system service needed for IIS to function? Did Sygate alter a dll or file or something that IIS uses?
It may not even be related to installing Sygate, im just guessing since around that time it seemed the problem began.
Now with Sygate removed though the issue is still there.

Is there anyway to do a repair on IIS to restore its original operating files? Or a diagnostics program that will look through my IIS for problems?

Any help would be greatly appreciated.
Thanks,

Steve

Hi Steve

Unfortunatley I can't help you but my problem turned out to be that the DNS server I was using (godaddy) wasn't sending the host headers with the web address.
A quick email to their customer support and I got the reply wthin 2 minutes (I'm in Australia which means they had someone working there at 1 in the morning!) which told me how to fix my problems, I then fixed it and it all works now

James

I also use godaddy and was wondering what info they gave you, I was planning on having 2 websites with different names and if I run into this problem it would be good to already know the answer.