Ask a question

Search Forums:

• Search Configuration Manager Documentation Forum
• Search All System Center Configuration Manager Forums
• Search All Microsoft TechNet Forums

 

Configuring custom SQL port in SCCM

Locked

• Tuesday, September 22, 2009 12:47 PMBruce Hethcote

   
  

  0

  Sign In to Vote
  I'm working on a fairly straightforward SCCM implementation
  1 SCCM/SQL server (Server 2008 SP1 x64 Std w/ SQL 2008 SP1+CU3) inside the LAN
  1 Internet-facing MP/DP/SUP (Server 2008 SP1 x64 Std) in the perimeter network (no SQL Replica)
  
  It is desired to have SQL listen on an alternate port.
  
  ===========================
  I have seen references to an SMS SQL System DSN that must be configured for this to work.
  
  http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/cf3db93e-6b1b-43cf-9828-c32eb1fa3986/
  
  Ports Used by Configuration Manager
  http://technet.microsoft.com/en-us/library/bb632618.aspx
  Quote from this link:
  

  "By default, SQL Server uses TCP (not UDP) port 1433 to listen on TCP/IP. To change the port, run SQL Server Setup on the server, and then click Change Network Support. If SQL Server uses port 1433, the client Net-Library works. If SQL Server uses a custom port number, the client must specify that port in the Data Source Name (DSN)."
  
  That is the total documentation on using an alternate port and it does not even address SQL 2008
  ===========================
  
  There is no SMS SQL System DSN on either server (or any System DSN for that matter)
  Making the change in SQL 2008 itself is easy enough, but
  
  <QUESTION>
   what must be done (especially on the internet-facing server or any remote system that must communicate with SQL) to make sure it can communicate with SQL?
  </QUESTION>
  
  It is my experience that nothing is required to be done on the SCCM site server with local SQL as I have changed the port and everything continues to work without error - including remote SCCM Admin consoles.
  
  Thanks - BH