SQL Server will only allow remote TCP connections if port is specified.

  • Hi All,

    I hope someone can clarify a connection issue I am having.

    1.SQL Configuration Manager is setup to listen on port 1234 for TCP/IP connections on myhostname

    2.I can telnet to myhostname 1234 so TCP/IP traffic is reaching that port

    3. I can connect remotely from a client in SSMS tcp:myhostname, 1234

    I Cannot connect SSMS to tcp:myhostname (without specifying the port) from a client machine.

    Any remote SSMS connection to myhostname connects via NTLM named pipes by default.

    The SPN is set up but my guess is that the SPN is not set up correctly so any SQLServer TCP/IP traffic to myhostname is not reaching port 3719 by default.

    Please can I have some peer advice on this because I think I need to pass this issue on to our IT Systems Teams.

    Thanks in advance!

    Suresh

  • I vaguely remember having an issue like this a while back. It was a firewall issue. Got the networks team to sort it.

  • is this a default instance? SSMS as a client presumes port 1433, so if it is set to some other value you need to explicitly specify it.

    ---------------------------------------------------------------------

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

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