Re: Services listening on all ports?



I think httpcfg.exe will allow you to do what you want.

"tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
news:egQ%230IqOHHA.4172@xxxxxxxxxxxxxxxxxxxxxxx
Yes IIS does bind to all addresses.

Apache does the same thing by default but if you add the address into the
connector line it will only bind to that address. That takes care of the
Apache issue.

But IIS will connect to all addresses even if you specifically set each
website to be a different address. In our case, if we set up 10 addresses
on the Nic card and set up our 4 web sites to access 4 of the address, it
will still grab all the addresses - preventing Apache from running. If we
manually start Apache to grab one of the addresses not used by IIS first
(from the Services window) and then start IIS - IIS will fail. The web
server will show as started but it won't handle any of the pages.

The solution, apparently (am in the process of testing and I believe it will
work) is a program from MS called httpcfg.exe which you can run to set up a
listener list. I assume what happens is that IIS will look for a listener
list and if it finds it, it will only bind to the addresses on the list. If
there is no list it will bind to all addresses. So in my case, I will put
all the address except the one that Apache will use and that will solve the
problem. It doesn't matter what order they start in as IIS won't even look
at the Apache address.

I am not sure what they did before W2K3 and XP SP2 as I believe it came out
then and I don't believe works for IIS5.

Wish me luck and thanks,

Tom


"Mike Lowery" <selfspam@xxxxxxxxxxxxxxxx> wrote in message
news:eBG4MbnOHHA.3544@xxxxxxxxxxxxxxxxxxxxxxx

"tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
news:%23sLpdDnOHHA.3872@xxxxxxxxxxxxxxxxxxxxxxx

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?

That depends on the service. You always have to specify a port number (or
use whatever is default) but it can either listen to all IP addresses (also
usually default) or a specific IP address. Most services (including IIS)
allow you to specify a specific address, as well as port, to listen on.






.



Relevant Pages

  • Re: I am going crazy..IIS 5.1 XP pro Not working correctly
    ... Are you running both IIS and Apache on port 80? ... IE when it can't even open a connection to the server, ...
    (microsoft.public.inetserver.iis)
  • Re: mailform hacking
    ... > I moved my Apache to a non-standard high port when I ... Moving services to arbitrary ports breaks that service for ... the few relevant lines in the mass of IIS attempts, ...
    (comp.os.linux.security)
  • RE: NT/2000 vs Unix based Web Servers
    ... the choice of web server platform borders on religious hysteria. ... In the case of IIS vs. ... Apache, which is the most common comparison made, each one has a lot to ...
    (Security-Basics)
  • Re: Apache vs IIS
    ... Windows Server not on my Linux Server so there for I would chose IIS. ... Not that Apache is bad but ASP.NET is far easier and faster to create good web forms in. ... PHP on a IIS server is rather easy to run once you install PHP on a PC but if you only use PHP why not use Apache for Windows. ...
    (alt.php)
  • Re: Services listening on all ports?
    ... Apache does the same thing by default but if you add the address into the ... But IIS will connect to all addresses even if you specifically set each ... listener list. ... I thought that when you created a service to listen on a port you had ...
    (microsoft.public.windows.server.networking)