Services listening on all ports?

I have been trying to run IIS and Apache Tomcat on the same Server using the
same Port (80 for http and 443 for https). I am trying to do this by using
multiple IP address on the same Nic card. This would allow me multiple
sockets for the same port.

With all my research it seems that most services seem to listen on ALL IP
addresses on the same machine for a particular port (25 SMTP, 53 DNS, 80
HTTP). I found you can tell IIS NOT to listen to a particular IP Address
which would allow Apache to connect to that IP Address and listen to 80 and
443 at the same time as IIS.

What I don't know is if this is normal. I did add another IP Address to my
Nic card and tried to do a "telnet address port" for all the ports open on
my machine. They were ALL open for both addresses. I thought that when you
created a service to listen on a port you had to give it an IP Address and
Port Number to create a socket.

If you create a service, is it going to listen on all IP Addresses?

Thanks,

Tom


.

Relevant Pages

  • Re: Save As saves link to WMV instead of video file
    ... for IIS HTTP to WMS HTTP on the same IP address. ... Both services cannot share the same port and IP address ... or to every playlist (WMS) for that to work - a world of pain. ...
    (microsoft.public.windowsmedia.server)
  • IIS6.0 W2K3 Disabling Socket Pooling
    ... All this websites runs on http port 80. ... We have desided that one IIS ...
    (microsoft.public.inetserver.iis.security)
  • Re: SBS 2003 and Outlook RPC over HTTP issues
    ... , but some of my clients do not want users to ... definitely closed now cause when I open it up http: ... the article is incorrect in stating that port 80 is needed. ... that port 443 and port 80 must be open to use RPC over HTTP. ...
    (microsoft.public.windows.server.sbs)
  • Re: Public Website on SBS 2003
    ... hosting and PROTECTING a website is specialist field and ... As leythos says you need to open HTTP port to the www. ... network settings are on servers internet connections. ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS 6 conflict using port 443 for NON-SSL traffic
    ... Just to make sure I am understanding you correctly, after this enhancement ... think it may be possible to use this enhanced HTTPS.SYS with IIS 6 on WS03? ... > HTTP.SYS in WS03 did not allow one port number to be used for both HTTP ...
    (microsoft.public.inetserver.iis.security)
Loading