Post reply

Dynamic port needed to remotely manage SQL Server Instance

  • September 1, 2009 at 3:06 pm

    #210272

    I have two subnets with a third party firewall between them. I have set up an instance of SQL Server Express on one subnet (for reference, this is the ".8 network") and have SQL Server 2005 (full version) installed on the other (".1 network"). I set the SS Express instance to use a fixed port (1433, since it is the only instance) and have opened up all ports need to access that instance remotely including those needed for Windows authentication.

    I can do almost everything from the .1 network against the SS Express instance, e.g.:

    Connect to the instance from SQL Server Management Studio on the .1 network.

    Run queries, including DDL

    View the logs and activity monitor

    I can not, however, configure or start/stop/restart the instance remotely because it is using a dynamic port that changes when the computer reboots. In SSMS the icon indicator which indicates the state of the instance is empty and the options to control the instance are disabled. Trying to connect remotely with SQL Server Surface Area Configuration remotely times out. If I open up that dynamic port on the firewall, all is well - until the next reboot.

    I can not figure out where to set that port. I even tried setting the DAC port, but it is not the DAC port. Everything I have seen that mentions setting a static port is referring to the general SS comm port (1433).

    Any ideas on this would be greatly appreciated.

    Thanks.

  • September 1, 2009 at 3:13 pm

    #1047860

    Here's an article that might be of use. Once the port has been statically set - this issue should go away.

    Set Static Port

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • September 1, 2009 at 3:43 pm

    #1047881

    Thanks for the quick reply!

    I had previously set up the port in the manner outlined in the link and it _does_ work, except for the administration of the instance itself. I can connect using SQLCMD and specifying the port number (1433), as noted in the link. I can see in the firewall log that 1433 is being used.

    The oddity is that it is using an additional port, which is dynamic. (Right now it is 1261, previously it was 1237, etc.) It tries to use this port when I connect to the instance in SSMS, run the Surface Area Configuration, or try to get into the Configuration Manager.

    Thanks again.

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

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