Setting named instance to listen on static port - what about the loopback adapter?

  • I have set up my named SQL-2008 instance to listen on a static port: Config manager -> SQL Server Network Configuration -> TCP/IP Properties -> IP Addresses -> removed all entries and added my port number (1353) in "TCP Port" under IPAll.

    I then restarted the SQL instance, and this is what I see in the SQL ERRORLOG:

    2009-07-24 18:00:58.07 Server Server is listening on [ 'any' 1353].

    2009-07-24 18:00:58.07 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSTANCENAME ].

    2009-07-24 18:00:58.07 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$INSTANCENAME\sql\query ].

    2009-07-24 18:00:58.08 Server Server is listening on [ 127.0.0.1 1354].

    2009-07-24 18:00:58.09 Server Dedicated admin connection support was established for listening locally on port 1354.

    The loopback adapter is listening on a different port: 1354.

    Is this expected, and could someone enlighten me on what this loopback adapter is?

    Also, is my setup OK for configuring SQL with a static port?

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • The dedicated admin connection or DAC is a special connection setup by SQL Server. There is one per instance and it is usually 1 port higher than the instance. You cna read more about it here... http://msdn.microsoft.com/en-us/library/ms189595.aspx

    The Loopback Adapter is always 127.0.0.1 It's one of those special reserved IPs. It is the local interface of your network card for a network device. From your workstation you can ping itself via the loopback address by executing PING loopback. It should resolve your Machine Name in the first line and then successfully ping 127.0.0.1. You can read more about the loopback here... http://en.wikipedia.org/wiki/Loopback

    Hope that helps,

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • Luke L (7/28/2009)


    The dedicated admin connection or DAC is a special connection setup by SQL Server. There is one per instance and it is usually 1 port higher than the instance. You cna read more about it here... http://msdn.microsoft.com/en-us/library/ms189595.aspx

    The Loopback Adapter is always 127.0.0.1 It's one of those special reserved IPs. It is the local interface of your network card for a network device. From your workstation you can ping itself via the loopback address by executing PING loopback. It should resolve your Machine Name in the first line and then successfully ping 127.0.0.1. You can read more about the loopback here... http://en.wikipedia.org/wiki/Loopback

    Hope that helps,

    -Luke.

    Thank you, that answers my question.

    Much appreciated! 🙂

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply