I thought the solution was setting up the router, so that an outside ip
address was to be sent to a specific to ports 80 on one web site with the
same ip as the 2003 server and to port 81 to another web site with the same
ip as the 2003 server. I had a cisco engineer set this up. However, the port
81 site would always be stopped and there was an error message about a file
already in use. I next tried one web site with the same ip address
(192.168.1.10) as the server using port 80 and the second web site with a
different ip address (102.168.1.12) using port 80. I used the ip address of
each site in a browser inside the network. The only site that came up was
.10. A second cisco engineer told me that there is no way to pu t more than
one web site, reachable from the internet at large, on the same server. He
said there must be one mac address for each ip address. He also said that it
would not work if there were multiple ethernet cards in the router. One
other possible solution is some type of redirection using asp.net.
I do not understand what "headers" are, so I have not tried this.
The network card is somewhat expensive and has many features on it, maybe
the solution is in the card.
I have only gone briefly through microsoft's help file on multiple web
sites, but it does not seem to be saying anything that I have not tried.
Microsoft seems to be saying that it is so easy. That is nice, but that does
not make it work.
Please tell me how to get multiple web sites working on the same server.
David Jensen
Lots of people run multiple outside websites on IIS without troubles; it is
truly easy to configure from the IIS perspective. What is non-obvious for
most users is that they assume networking and routing happens magically when
it cannot, and none of that has anything to do with IIS nor Microsoft. But,
they blame Microsoft/IIS for not making their website work when they are
actually responsible...
How many IP addresses does your network card support. How many IP-Forwards
does your Cisco router support. When you straighten that out, configure IIS
to bind websites to the IP addresse and the rest should work. When you
configure networking to route traffic from one IP:Port to another internal
one, and IIS is bound to that internal one... things should work.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"davidjensenusa" <davidje...@discussions.microsoft.com> wrote in message
news:C6F0F219-BAB0-4E23...@microsoft.com...