5 replies
by dewbryant Accepted solution
by slayer_ Accepted solution
by cg it Accepted solution
if it's set to use all unassigned addresses with host headers, then local lan users need to use the domain name [or public address and http port number].
Local lan users cann't use the private non routable address as IIS doesn't recognize the private address as belonging to the site. It only uses host headers which is the FQDN and that resolves to the public address.
by dewbryant Accepted solution
I figured out the problem, with assistance of another. We did traceroute and ping from routers and they were going thru but we couldnt figure out why it was going through. Until someone that works indepth with windows said that windows server 2008 has 3 firewalls. Which are Domain, Private, and public. We did configurations on public why we could see it using public address and not domain and private. But that was what was going on that domain and private were on and not letting anything pass through. We turned it off and could ping it from remote sites and website displayed. So if you are setting up web server 2008. I would watch out for that.
to do changes on it..its under my computer and right click do manage and click configurations and firewalls... I hope this helps someone else.
by cg it Accepted solution
well glad you found the problem.
I've found that the network and sharing center can really be a problem because any connection that can't reach the internet is labled public and has the public firewall setting applied which basically blocks everything.
This discussion is closed to new replies.
Trending Web Development posts
Sort by Trending