David
Sat Nov 25 04:26:54 CST 2006
By default, IIS does not listen to the ports you see from NETSTAT.
Thus, your networking and IIS configuration has already been customized
by some external system. Probably by SBS2003 as a part of its
integration. So, this is really not a problem with IIS but rather with
one's understanding of what is configured and how.
I suggest first contacting SBS newsgroup
(microsoft.public.windows.server.sbs) to see if there it has a
networking configuration wizard to do this for you -- because it sounds
like you have a multi-homed server which has its own tricky set of
network routing to configure. I don't want to see you tweaking IIS
setting independently and then getting SBS2003 confused somewhere down
the line because you didn't do the multi-homed server configuration
correctly and consistently.
I have seen examples of people misunderstanding the internal companyweb
and then getting into trouble with Visual Studio .Net later, etc.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Massimo wrote:
> I have windows server 2003 sbs premium.
>
> I have 2 ethernet with internal ip (172.18.81.116 and 172.18.81.114 ) and 1
> ethernet for external.
> I want use the second internal ethernet for web application over IIS
> (172.18.81.114).
>
> I can't set the second ip adress to any application or virtual directory of
> IIS.
>
> If i run netstat -ano i see bind 80 only 127.0.0.1; 172.18.81.116 and
> ethernet ip external.
>
> How can i do? I want iis application respond from 172.18.81.114.
>
> If i open iis manager and i go to specific virtual directory and try set ip
> 172.18.81.114 when i click to apply or ok error appear and i cant do it.
> Error say (in italiano ..impossibile raggiungere il percorso di
> destinazione..) that is it impossible find the network destination path.