| Tom Kaminski [MVP] 2004-11-15, 8:06 am |
| "James Leech" wrote:
> Thanks for the quick response. The Local Intranet / Internet aspect isn't
> one I had considered, but I've just checked and they both say Internet when
> addressing the intranet site and yet, my customers server still insists on
> asking for a username and password, whereas my server is happy to load the
> page without. I have however found one difference: I address site on our
> server as http://10.0.0.10:8080 and the customers site as
> http://192.168.1.10. whilst the IP addressing scheme is different (which I'm
> guessing doesn't matter), I specified a different port on my server. The
> reason behind this is that the default website already has * All Unassigned
> *, port 80 specified which I avoided using on our server and changed (to
> 8080) on my customers server.
>
> So perhaps I should be attacking this problem from a different angle. Lets
> go back to basics here: What is the correct way to add an intranet site to
> an IIS server with regards to its IP Address and Port; Should the sites IP
> address be specified? Should its port be 80 (which conflicts with the
> default website) or should it be changed? Should I stop or reconfigure the
> default website in order to avoid conflicts? Should I be using Host Headers?
>
> Once I have both sites setup 'properly' I can then perhaps workout what
> problems (if any) I really have. It would be great to see local intranet
> appear in the bottom right of my browser!
It's not really an IIS issue that's causing this:
http://support.microsoft.com/defaul...3&Product=ie600
The correct way to add a site? It doesn't really matter as long as each
site has at least one out of three things unique - IP, port, or host header
name.
|