Connect to SQL remotely

  • Hi all, I'm glad I registered on this forum, there is a lot of interesting information here. I also have a small question, I have SQL on my work computer in the office, now I am looking into a remote connection so I can work safely in the program from home. In this regard I have a question what is TCP-Port-135?

    I apologize in advance if the question is in the wrong category!

  • First question.  Why are you using SQL 2012?  End of life is July 12, 2022.  I recommend upgrading to a new version.

    This article describes the various ports and protocols that are required for SQL Server.  I suggest you start here.

    https://docs.microsoft.com/en-us/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access?view=sql-server-ver15

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/

  • To add to what Michael said though about ports - in practice, any port under 1024 (I think... been a while since I did networking stuff) is a "reserved port" that is USUALLY set aside for a specific purpose at the OS level.  For example, port 80 is for HTTP traffic and port 21 is for FTP traffic.

    Now, that being said, there is nothing stopping you from configuring your web server (for example) to listen on port 21 and your FTP server from listening on port 80.  So asking what TCP Port 135 is used for (which is what I THINK your question was) is that it could be used for anything.  Quick google brought me to this page which lists all of the common uses for port 135:

    https://www.speedguide.net/port.php?port=135

    Now, someone MAY have configured a SQL instance to listen on port 135.  If so, that is not a good practice.  BEST practice is to avoid re-using ports lower than 1024 to reduce the chance you are borrowing a port that is in use by some known protocol.

    Now, I do agree with Michael as SQL 2012 seems old, but I can't really say anything when I have older ones still up and running in my environment...

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

  • This port allows the system to access the target system seamlessly. If you want to explore the question in more detail, look I found this information https://www.helpwire.app/blog/tcp-port-135/

  • This was removed by the editor as SPAM

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

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