all groups > sql server connect > december 2006 >
You're in the

sql server connect

group:

Why SQL Server 2000 default port is not 1433?


Why SQL Server 2000 default port is not 1433? Michael
12/13/2006 9:06:18 AM
sql server connect:
I installed MS SQL Server 2000 and sp4.
The operation system is Windows 2003 server.
On server machine,
I open server network utility, and checked.
found that the default TCP port at server end is not 1433. Why?
But then I open Client Network Utility, the default port is 1433.

On my machine. (not the same one as server)
I cannot connect to that database server using SQL Query Analyzer.
What can I do now?
Thanks.
Re: Why SQL Server 2000 default port is not 1433? Rick Byham, MS
12/13/2006 1:56:49 PM
The most likely reason SQL Server is not listening on port 1433 is =
because something else is taking the port, such as another instance of =
SQL Server. If you know the port is available, use the SQL Server 2000 =
Server Network Utiltity to specify the port.
If, like me, you have SQL Server 2005 on port 1433, and SQL Server 2000 =
on port 2061, then as long as the SQL Server Browser Service is started =
(on the SQL Server computer) then the client should still be able to =
connect by name.

If you can't move your SQL Server 2000 to port 1433, change the client =
to connent to the correct port number using the Client Network Utility.
Or use the Client Network Utility to create an alias to the correct port =
number.
Or connect from the client directly specifying the port such as =
tcp:<computer_name>, <port_number> such as tcp:accounting, 2061

--=20
Rick Byham, MS
This posting is provided "AS IS" with no warranties, and confers no =
rights.

[quoted text, click to view]
Re: Why SQL Server 2000 default port is not 1433? Michael
12/15/2006 1:45:53 AM
THanks Rick.
I changed the port to be 1433 on server using Server network utility.
And I am sure the port number is 1433 too on client PC.
But still I cannot connect to server on client server.
And there is only one instance of SQL Server. And 1433 port is not
being used by any other applications.
I run netstat -anb on that server, and got TCP: 0.0.0.0:1433. Is this
normal?
Thanks.

"Rick Byham, MS =D0=B4=B5=C0=A3=BA
"
[quoted text, click to view]
e something else is taking the port, such as another instance of SQL Server=
.. If you know the port is available, use the SQL Server 2000 Server Network=
Utiltity to specify the port.
[quoted text, click to view]
n port 2061, then as long as the SQL Server Browser Service is started (on =
the SQL Server computer) then the client should still be able to connect by=
name.
[quoted text, click to view]
AddThis Social Bookmark Button