Post reply

Connecting to non-default port with Enterprise Manager

  • August 22, 2005 at 12:04 am

    #102721

    Ok,

    Quick question from a newbe.

    If I change the SQL port from the default 1433. How do I then connect remotly to this server with Enterprise Manager. Currently it's x-over connected to the IIS Server with a second NIC for the Internet. I'm getting "Login failed for user: sa" about 2 per second so I need some obscurity.  

    I haven't found where to tell EM what port to connect to during the DB development. 

    Thanks in advance.

    Mack

  • August 22, 2005 at 12:43 am

    #583807

    I haven't been able to try this, but see if it helps.

    On the server registration in EM, right-mouse-click and select properties.

    Then click on the Network Configuration bar at the bottom. Under the Enabled Protocols, highlight TCP/IP and click Properties. Change the Port number and see if that resolves the problem.

    Another option to try would be to use Client Network Utility and create an Alias with the manually set port address.

  • August 22, 2005 at 12:49 am

    #583809

    Use a comma to specify the port, such as 123.123.123.123,2433. Or you could create an alias in Client Network Utility and register the server using that name.

    --
    Chris Hedgate http://www.hedgate.net/
    Contributor to the Best of SQL Server Central volumes
    Articles: http://www.sqlservercentral.com/columnists/chedgate/

  • August 22, 2005 at 11:10 am

    #583979

    Thanks guys.

    Simply adding the comma and the port address acomplished exactly what I needed to do. The EM connects without complaining now.

    And, the "Login failed for user: sa"  @ 2 times per second has quit.

    For now.....

    Mack

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

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