I'd agree on that ! -----Original Message----- From: Craig Humphrey [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 8:43 AM To: '[EMAIL PROTECTED]' Cc: [EMAIL PROTECTED] Subject: RE: IIS listens to port 80 on 0.0.0.0
Odd. I had the same problem with HTTPS (IIS was listening on port 443 on all IPs and I wanted to run another service on one IP on port 443) and the hack worked for me. I guess it's another fix from Microsoft where "your milage may vary". Sorry I couldn't be more helpful. Later'ish Craig > -----Original Message----- > From: Sarbjit Singh Gill [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, 25 September 2002 2:51 PM > To: Craig Humphrey > Cc: [EMAIL PROTECTED] > Subject: RE: IIS listens to port 80 on 0.0.0.0 > > > Tried that KB article already. Does not work. I just need the > IIS service to > listen to 80 on the IP that I want it to. > > Cheers > Gill > > -----Original Message----- > From: Craig Humphrey [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 25, 2002 5:05 AM > To: '[EMAIL PROTECTED]' > Cc: [EMAIL PROTECTED] > Subject: RE: IIS listens to port 80 on 0.0.0.0 > > > It's a "feature" of IIS5. By default it listens on port 80 > on all available > IP addresses (0.0.0.0). > This can be fixed: > http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q238131&; > > Hope that helps. > > > -----Original Message----- > > From: Sarbjit Singh Gill [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, 24 September 2002 9:05 PM > > To: [EMAIL PROTECTED] > > Subject: IIS listens to port 80 on 0.0.0.0 > > > > > > Greetings, > > > > Recently I realized that my IIS was not responding to port 80 > > requests. > > > > After running active ports, realized it was only listening to > > port 80 on > > 0.0.0.0 > > > > It is a w2k pro, sp2 patched with pre-sp3 hot fixes, and zone alarm. > > executed IIS Lockdown and BASELINE from Microsoft. I Discovered this > > recently because I installed Visual Studio .NET hence I ran > > the IIS lockdown > > to enable the IIS again. Previously IIS was disabled. > > > > Is this a security issue or just miss-configuration of the w2k pro. > > > > Cheers > > Gill > > >
