Do Windows Servers Have a Limit to the number of domains hosted?

[hannamyluv]

I am not a hardware person AT ALL, and there is nothing like having a client who knows nothing about their own servers...

I have a client whose last IT person up and left abruptly. In the mean time, we have added a new website to their server which already hosts many, many little sites.

With the new site, if I set it up as I think (at least as far as I can understand the directions and in comparison to the other domains on the box) it suppose to be, the server will not serve the site up when the DNS is pointed at it.

But, if I use the DNS Manager in Network Solutions (their domains are registered there) and point using the IP, the site will get served up.

This would technically solve the problem, except that no one at the site where the server lives (and is the client's office) can get to the site. Everyone else in the world can get to the site, just not anyone there in the same location as the server.

Can someone help me make it so the site can be reached by everyone? Do Windows servers just have a limit to the amount of domains you can host on them and this is why?

[TheNige]

Are the host headers (domain name and IP) set up on the website in IIS?

[gettopreacherman]

No, there is not a limit, though you may want to limit them regardless, as you can get bogged down if you get traffic spikes...I have one server and 30+ sites, assigned to 6 IP Addresses, should be fine. Make sure the host headers have both instances of the site name:

site.com
www.site.com

Also, make sure that the network for the client doesn't ignore particular IPs...my guess is that the network is forwarding internal traffic straight to the server Without going outside and back...