Post reply

Sql 2005 Named instance starts until I assign it a static port

  • March 7, 2008 at 1:11 pm

    #154181

    I installed a Sql 2005 x64 default and named instance. The named instance starts when I use all defaults (i.e.dynamic ports) but not when I assign a static port to it. (Both instances use the same IP and the default instance uses the default port). I have read the Microsoft literature but obviously am missing something. Here's what I did to the second instance:

    1. Use netstat -an to look for an unused port < 5000 (read somewhere in the literature that 5000 is a desirable upper limit).

    2. SQL Server Config Manger >

    SQL Server 2005 Network Configuration>

    Double-click "Protocols for "

    Double-Click TCP/IP

    IP addresses tab

    Changed all IP address (and "IPAll") "TCP Dynamic Port" settings to a single

    blank and set all "TCP Port" setting to the instance port.

    Restarted SQL Server

    Tried to access is locally. on local

    machine...ERROR.. can't connect..server not found

    Any idea what I'm missing?

    TIA,

    Barkingdog

    P.S. Ultimately this server will be the database backend to our public web server Because of an intervening firewall, the default and named instances need to use static ports. Currently I'm just trying to get the config working internally.

  • March 7, 2008 at 3:19 pm

    #786952

    for ours, we clear out the TCP Dynamic Ports boxes for all the IP connections, and only fill in the TCP Port boxes, all with the same port. This configuration works for us.

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

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