Re: Why won't port 80 dissapear?

From: Aaron (a_at_1.net)
Date: 10/30/03 

Date: Thu, 30 Oct 2003 10:41:48 -0500

You can't remove have an empty value in the TCP attribute. If you don't
want port 80 open for HTTP traffic block it with your firewall -- or use
some code for force all HTTP connections to use HTTPS.

Shadowplay wrote:
> Well, what is the guidance for shutting off an http connection? In
> the properties of the webserver, I can change the TCP port from 80 to
> whatever and it is still going to be an http port correct? I have my
> TCP port as 80 and my SSL port as 443. I thought I could change my
> TCP port to be the SSL port number but then I get an error that they
> can't be both. We then decided to name the TCP port 8080, that still
> lists an http port open in a netstat -a. I can not have any http
> ports listed in a netstat call, only https.
>
> Am I making sense?
>
>
>
> "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message news:<uG04O7pnDHA.1960@TK2MSFTNGP12.phx.gbl>...
>
>>OK you installed a certificate, which will allow the server to listen for
>>https:// connections (typically to port 443), but what have you done to stop
>>to listening on port 80? It's still a webserver, and by default webserver's
>>listen on port 80...
>>
>>Did you remove port 80 from the HTTP bit the IIS MMC Snapin?
>>
>>Cheers
>>Ken
>>
>>"Shadowplay" <Anywherebuthere@hugeass.com> wrote in message
>>news:A86dnc7C99yjDD2iRVn-hA@comcast.com...
>>: We have an Nfuse webserver that is using IIS 5.0. We've installed the SSL
>>: certificates to run the webpages through an https connection but when we
>> do
>>: a netstat -a, we still see the http port listed as active. It doesn't
>> have
>>: any foreign connections, it just seems to be connected to localhost only.
>>: Our security team is busting our balls to get it off of there. Anyone
>> have
>>: any ideas on what to do? We can change the port to 8080, or we can create
>>: another webserver with the wizard and maybe that will help. Does anyone
>>: have any suggestions? Is this a bug in IIS5.0?
>>:
>>:

Relevant Pages

  • Summary: Tcp/Udp port mapping (equivalent of firewall NAT)
    ... existing NIC port & bind the UPS software to this address. ... and anything else gets sent to the one listening ... a UPS software that makes use of Tcp 6003. ...
    (SunManagers)
  • Re: 2 Default instances on Active/Active
    ... on a different TCP port and/or pipe name. ... on a separate node, and each is listening on TCP 1433, whenever a failover ... for both cluster and stand-alone systems with ...
    (microsoft.public.sqlserver.clustering)
  • Re: ISA2004 with SBS2003 Web Proxy Bind Error
    ... already using the same port or by a network adapter that is not functional. ... The failure is due to error: ... TCP sbs2003:nameserver sbs2003.sbs.local:0 LISTENING 2312 ...
    (microsoft.public.windows.server.sbs)
  • Re: IPSec and outgoing HTTP
    ... You need to mirror that rule in order to all traffic in from tcp 80 ... It all seems to work ok except for outgoing http traffic. ... Websites still work. ... traffic from my IP on port 80 to any IP but it doesnt seem to work. ...
    (microsoft.public.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)