Re: Ports
From: Steve Thompson (stevethompson_at_nomail.please)
Date: 11/17/04
- Next message: Kevin McDonnell [MSFT]: "RE: continued..."
- Previous message: Rand Boyd [MSFT]: "Re: SQL Server 6.5 - probe account"
- In reply to: Cal: "Ports"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 17 Nov 2004 13:04:29 -0500
I just answered your question in microsoft.public.sqlserver.server
Steve
"Cal" <anonymous@discussions.microsoft.com> wrote in message
news:715301c4cbf7$8a9d1ed0$a301280a@phx.gbl...
> I need to find out what tcp ports Sql Server 2000 needs.
> 1433 is the standard network-accessed port, right? And
> isn't it 80 that the web comes through?
>
> The reason I'm asking is because our security group came
> by and showed me a list of ports mapped from our web
> servers through the firewall to various of my production
> sql servers. Furthermore, they know that none of these
> ports has had any traffic in the last three months. So of
> course they would like to close these access holes up
> since they're not being used.
>
> Most of these dead ports are 1433 which is incorrect
> right? i.e. the web would not generally directly hit 1433
> to access Sql Server? Plus isn't that a security risk?
>
> I also see 1100, 1199, 7050 mapped in? Those aren't
> standard ports used for anything Sql Server related, right?
>
>
- Next message: Kevin McDonnell [MSFT]: "RE: continued..."
- Previous message: Rand Boyd [MSFT]: "Re: SQL Server 6.5 - probe account"
- In reply to: Cal: "Ports"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|