Re: Why SQL Server 2000 default port is not 1433?
- From: "Michael" <michaellm@xxxxxxxxx>
- Date: 15 Dec 2006 01:45:53 -0800
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 写道：
"
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
--
Rick Byham, MS
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael" <michaellm@xxxxxxxxx> wrote in message news:1166029578.047335.4360@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I installed MS SQL Server 2000 and sp4.------=_NextPart_000_000A_01C71EBE.891012E0
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.
Content-Type: text/html; charset=gb2312
Content-Transfer-Encoding: quoted-printable
X-Google-AttachSize: 2709
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.5536.16385" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=Arial size=2>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.</FONT></DIV>
<DIV><FONT face=Arial size=2>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.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>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.</FONT></DIV>
<DIV><FONT face=Arial size=2>Or use the Client Network Utility to create an
alias to the correct port number.</FONT></DIV>
<DIV><FONT face=Arial size=2>Or connect from the client directly specifying the
port such as tcp:<computer_name>, <port_number> such as
tcp:accounting, 2061</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>-- <BR>Rick Byham, MS<BR>This posting is provided
"AS IS" with no warranties, and confers no rights.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>"Michael" <</FONT><A
href="mailto:michaellm@xxxxxxxxx";><FONT face=Arial
size=2>michaellm@xxxxxxxxx</FONT></A><FONT face=Arial size=2>> wrote in
message </FONT><A
href="news:1166029578.047335.4360@xxxxxxxxxxxxxxxxxxxxxxxxxxx";><FONT face=Arial
size=2>news:1166029578.047335.4360@xxxxxxxxxxxxxxxxxxxxxxxxxxx</FONT></A><FONT
face=Arial size=2>...</FONT></DIV><FONT face=Arial size=2>>I installed MS SQL
Server 2000 and sp4.<BR>> The operation system is Windows 2003
server.<BR>> On server machine,<BR>> I open server network utility, and
checked.<BR>> found that the default TCP port at server end is not 1433.
Why?<BR>> But then I open Client Network Utility, the default port is
1433.<BR>> <BR>> On my machine. (not the same one as server)<BR>> I
cannot connect to that database server using SQL Query Analyzer.<BR>> What
can I do now?<BR>> Thanks.<BR>></FONT></BODY></HTML>
------=_NextPart_000_000A_01C71EBE.891012E0--
.
- References:
- Why SQL Server 2000 default port is not 1433?
- From: Michael
- Re: Why SQL Server 2000 default port is not 1433?
- From: Rick Byham, MS
- Why SQL Server 2000 default port is not 1433?
- Prev by Date: Re: Connecting to Sql Server 2005 on Win2K3 Server
- Next by Date: when I try to connect to to sql from my computer I get [Microsoft][ODBC SQL Serv
- Previous by thread: Re: Why SQL Server 2000 default port is not 1433?
- Next by thread: Connecting to SQL Server Express
- Index(es):
Relevant Pages
|
Loading
