Re: Changing Default SQL ports on SQL 2000 Server

Hi,

In your case you need to do nothing on the clients. Named Pipes on the client will be able to negotiate a connection with the server.

Jonathan




CP wrote:
Hi Jonathan,

Thank you for your response. Can I still do this (creating the TCP/IP based) if I am using Named Pipes as my connector on the client?

I have read a post somewhere that Named Pipes cannot dynamically determine destination SQL port numbers in SQL Server 2000.

Regards

CM

"JPD" wrote:

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: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)
  • 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: Changing Default SQL ports on SQL 2000 Server
    ... TCP/IP were two different connectivity mechanisms and that if Named Pipes are ... the connections will fail if the default port is changed as ... Named Pipes in SQL 2000 cannot dynamically determine destination port numbers. ... Just change the port via the SQL Server Network Utility. ...
    (microsoft.public.sqlserver.security)
  • 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: Access To SQL Server Behind Firewall
    ... Using the Client Network Utility on the SQL Client to ... you tell the client what port the "listening" SQL Server ...
    (microsoft.public.sqlserver.security)