Re: Changing Default SQL ports on SQL 2000 Server



Hi,

Just change the port via the SQL Server Network Utility. On the client open the Client Network Utility and create a TCP/IP based alias that dynamically determines the port. The client will then use port 1434 to determine which port it needs to use. Make sure that your firewall has both port 1434 and the port the SQL Server instance is listening on open.

Jonathan



CP wrote:
Hi Group,

As part of best practices we would like to change the default port number that SQL Server 2000 listens on.

Once this has been done, can the application client dynamically determine the new port number using the SQL Server Reporting Service listening on udp 1434?

Please note that Named Pipes are being used to establish the connections and that there is a firewall between the SQL Server and the applications clients.

Regards

CM

.



Relevant Pages

  • Re: thin client com ports
    ... I'm glad that you got at least one more client working! ... MCSE, CCEA, Microsoft MVP - Terminal Server ... the COM port settings? ... I am testing several thin clients. ...
    (microsoft.public.windows.terminal_services)
  • Re: network installation manager
    ... there is a firewall between master and client machines, ... NIM Communication within a Firewall Environment ... master via nimclient calls to the nimesis daemon. ... reserved port range of 1023-513. ...
    (comp.unix.aix)
  • Re: Mysterious Port of SQL Server not shown by netstat
    ... If this fails then yoru SQL Server is not listening on 1433. ... port, only ms-sql-s). ... > My query analyzer client from local machine and remote machine> successfully connects to my server. ... There is a jdbc client which wants> to connect at port 1433 that fails saying could not establish network> connection at port 1433. ...
    (microsoft.public.sqlserver.programming)
  • Re: Default protocols ..
    ... I checked the default port in the Client Utility on the ... "I checked the default port fort the TCP and it is the good ... And are you in a totally SQL Server 2000 environment? ... I set the TCP has the only one default client protocol with the CLICONFG ...
    (microsoft.public.sqlserver.connect)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... > I am also wondering if it has something to do with TCP port allocation. ... Once the client gets to port 5000 it seems to stop and then ... Normally I'd expect a different error from the SQL Server ...
    (microsoft.public.sqlserver.odbc)