Accessing the web server 'on the intranet' implies accessing via the local LAN. If it's not on the LAN then, by definition, you can't do it....

Have you worked out where the bottleneck is on the existing internet connection. As Michel suggested you should probably compare response times with that for a simple (no data) page.

>I already have one site Binding defined, which currently has a host name that is pointed from another site where the domain is defined. Its IP address is the WAN IP address of the server.
>
>To add a new binding, what do I put into the host name and what IP address should I use. Please note that this server is hosted as a dedicated server at a third party.
>
>Thanks again.
>
>
>>I think the default is to accept traffic from all IP addresses for port 80. But to check in IIS Manager:
>>Select the web site in question.
>>In the right hand panel under 'Actions' click 'Bindings...'
>>You should see :http Port:80 Ip Addess : *
>>If not you can add an entry to allow the specific intranet IP address.
>>
>>(The above, of course, assumes that the machine itself had a network connection on that address....)
>>HTH
>>Viv
>>
>>>IIS 7.5
>>>
>>>
>>>>Is the server IIS 6 or IIS 7 ?
>>>>
>>>>>How do I get the web site configured to a local network address? Thanks.
>>>>>
>>>>>Bob
>>>>>
>>>>>>Whether the Intranet connection will supply a faster response depends on *why* the Internet response takes 3 seconds in the first place. It should certainly be faster to actually deliver a page (but no faster in the composing of it) IAC if you are using IIS you can easily configure it to respond to both the external IP and a local network address (e.g 10.x.x.x). If you need more detail on how to do so just shout......