Re: listening on... interfaces

From: Mike Epprecht \(SQL MVP\) (mike_at_epprecht.net)
Date: 05/26/05 

Date: Thu, 26 May 2005 01:40:31 +0200

Hi

You have to configure IPSec at NIC level to disallow connections on the
public IP. By default and design, SQL Server will always listen on all IP's
and SQL Server can not be configured not to listen on them.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Rick" <Rick@discussions.microsoft.com> wrote in message
news:67BA2827-A522-40DB-B288-0C63A9A1797B@microsoft.com...
> The errorlog on my installation reports the following:
>
> SQL server listening on MY.INTERNAL.IP.1: 22847.
> SQL server listening on MY.PUBLIC.IP: 22847.
> SQL server listening on MY.INTERNAL.IP.2: 22847.
> SQL server listening on 127.0.0.1: 22847.
> SQL server listening on TCP, Named Pipes.
> SQL Server is ready for client connections
>
> How can I configure SQL to not listen at all on the public IP?
>
> Thanks.
> -Rick
>
>

Relevant Pages

  • Re: listening on... interfaces
    ... > Isn't it common to not want your SQL Server ... > to be listening to the wild wild internet? ... >> Mike Epprecht, Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.security)
  • Re: Connecting to MSDE Thru VB Without Machine Name
    ... broadcast, on which SQL Servers respond (Default protocol for SQL Server ... SQL Servers have to be running on Windows NT or Windows 2000 and have to ... SQL Server that listening on TCP/IP ...
    (microsoft.public.sqlserver.msde)
  • Re: SQL Server drops off port 1433 on first request - a clue?
    ... SQL Server by default listens on all your network interfaces. ... This normally happens if another process is holding on to the port 1433. ... >> When I run netstat just before this exchange, I see a sqlserver listening ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Server does not exist or access denied -Personal/Developer
    ... It turns out that Computer A and Computer B were not listening on port ... Additionally, SQL server was only listening on "Shared Memory, ... >>access Server A, and my code executing on Computer B can access Server A. ...
    (microsoft.public.sqlserver.connect)
  • Re: msde 2000 verify instance
    ... broadcast, on which SQL Servers respond (Default protocol for SQL Server ... SQL Servers have to be running on Windows NT or Windows 2000 and have to ... SQL Server that listening on TCP/IP ...
    (microsoft.public.sqlserver.msde)