Can't get it to listen on TCP port 1433

Been having SQL Server 2000 running for some time now, but recently it stopped listening on TCP port 1433, the log reports its listening on shared memory, Named pipes and Rpc, but no sign of 127.0.0.1 port 1433 or any errors to say why it won't listen.

I've done a netstat -na and nothing else is listening on that port, tried restarting using the enterprise manager, gonna try restarting the entire Server when everyone has gone home, but I'm pretty sure its been restarted recently.

All the other archive logs going back a few days show its not listening.

Yes, I have used the Server network utility to make sure TCP/IP is enabled and set to 1433, even added a comma and 1434 to see if it will listen on multiple ports, no go.

Any help?
What service pack do you have installed?|||Have you told your firewall to allow connections to Microsoft SQL Server?|||SQL Server 2000 - 8.00.194 build 3790 Service pack 1

Mmmm, isn't SP3 out?
Lets hope it doesn't break it even more, as after the restart of the entire server last night, its now not responding to TCP connections locally 127.0.0.1

Not sure about the firewall, I'll have to check, its been fine with it for the past few years.

|||

SP4 has been out for quite some time. Here is a handy web site which lists all of the hot fix and service packs which have been released http://www.sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx.

Start by upgrading to SQL 2000 SP4. Odds are a Windows 2000 hot fix shuts down SQL from talking over the net if prior to SP3 as there is a major security flaw prior to SP3 which the SQL Slammer worm expliots.

Can't connect via Enterprise Manager

I had a similar problem that was due to the server not
using the proper TCP/IP port. I am guessing that one of
your servers is using a different port, (or none at all),
so it can't be seen by clients looking for the default
port number 1433, at least that was the problem in my case.
Check your Windows registry settings for the following
entries, (this is the key for a default instance, but
there are similar key paths for multiple instances):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServ
er\SuperSocketNetLib\Tcp\TcpPort
This value is the port that SQL Server will listen on. In
some cases it does not get set up correctly on the
install. The default is a decimal value of "1433" (if it
was blank then the server was only using shared memory
protocol)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\Su
perSocketNetLib\Tcp\DefaultPort
This value is the port that clients use to communicate
with the server. It normally will also be "1433" (decimal).
If you do change these values you should shut down the
server service first and check the registry again after
the server is running again... I had a heck of a time
getting my server to use port 1433, as it kept switching
to port 2433 after the server started up. (Not sure if
it's necessary, but I also put a "" in the TcpDynamicPorts
variable) to make sure dynamic port assignments is off.
Alternatively, if you do have different port settings and
need to keep them as they are, you can create alias
entries on your clients that will associate the proper
protocols and ports for each server.
HTH,
TK
>--Original Message--
>Hi All,
>We have a MSDE on a W2K server installed. It is running
fine and the
>application can access it without a problem. We have
another server on that
>same subnet that has an SQL 2000 server installed. When
trying to connect to
>the MSDE via the Enterprise Manager, only the local SQL
shows up and we
>cannot connect to the MSDE instance.
>When we go to the ODBC on the MSDE box we see both SQL -
the local and the
>remote one. On the ODBC on the other server we only see
the local one.
>Does anybody have an idea what is going on?
>Thanks,
>Claus
>
>.
>
Thanks for the reply. I finally was able to connect. I still don't have any
idea what the reason was. I rebooted both servers and it worked without
making any changes. No entries in the event logs.
MS never stops surprising me.
thanks again to all of you for your good advise,
Claus
"TK" <anonymous@.discussions.microsoft.com> wrote in message
news:3c9f01c4a58c$61560b90$a301280a@.phx.gbl...[vbcol=seagreen]
> I had a similar problem that was due to the server not
> using the proper TCP/IP port. I am guessing that one of
> your servers is using a different port, (or none at all),
> so it can't be seen by clients looking for the default
> port number 1433, at least that was the problem in my case.
> Check your Windows registry settings for the following
> entries, (this is the key for a default instance, but
> there are similar key paths for multiple instances):
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServ
> er\SuperSocketNetLib\Tcp\TcpPort
> This value is the port that SQL Server will listen on. In
> some cases it does not get set up correctly on the
> install. The default is a decimal value of "1433" (if it
> was blank then the server was only using shared memory
> protocol)
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\Su
> perSocketNetLib\Tcp\DefaultPort
> This value is the port that clients use to communicate
> with the server. It normally will also be "1433" (decimal).
> If you do change these values you should shut down the
> server service first and check the registry again after
> the server is running again... I had a heck of a time
> getting my server to use port 1433, as it kept switching
> to port 2433 after the server started up. (Not sure if
> it's necessary, but I also put a "" in the TcpDynamicPorts
> variable) to make sure dynamic port assignments is off.
> Alternatively, if you do have different port settings and
> need to keep them as they are, you can create alias
> entries on your clients that will associate the proper
> protocols and ports for each server.
> HTH,
> TK
> fine and the
> another server on that
> trying to connect to
> shows up and we
> the local and the
> the local one.

Can't connect to SQL server

Hi,
I'm having trouble connecting to the SQL server in a LAN. I can't even
telnet to the port 1433 of the server. Does anyone have any idea how to fix
this problem?
Shafiee.
Are you able to ping the SQL Server? What error are you getting when you try
connecting to the server using Query Analyzer?
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"shafiee" <mohamed.shafee@.gmail.com> wrote in message
news:Ov0k0dSrFHA.304@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I'm having trouble connecting to the SQL server in a LAN. I can't even
> telnet to the port 1433 of the server. Does anyone have any idea how to
fix
> this problem?
> Shafiee.
>
|||Hi Narayana,
Yes I am able to ping to the server. The server isn't listening to client
requests. The version of SQL server installed is SQL 2000. Any ideas?
Shafiee.
"Narayana Vyas Kondreddi" wrote:

> Are you able to ping the SQL Server? What error are you getting when you try
> connecting to the server using Query Analyzer?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "shafiee" <mohamed.shafee@.gmail.com> wrote in message
> news:Ov0k0dSrFHA.304@.TK2MSFTNGP11.phx.gbl...
> fix
>
>
|||If SQL Server is running and you can ping the server, one
possibility is that the server is listening on shared memory
only which means only local connections will be allowed. Use
the server network utility on the SQL Server box to make
sure you have protocols enabled. You can also check the SQL
Server error log from when the instance started to see what
protocols, ports SQL Server is listening on. If it's only
Shared Memory, enable TCP/IP on the server using the server
network utility.
-Sue
On Tue, 30 Aug 2005 19:59:04 -0700, "Shafiee"
<Shafiee@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Narayana,
>Yes I am able to ping to the server. The server isn't listening to client
>requests. The version of SQL server installed is SQL 2000. Any ideas?
>Shafiee.
>"Narayana Vyas Kondreddi" wrote:

Can't connect to SQL server

Hi,
I'm having trouble connecting to the SQL server in a LAN. I can't even
telnet to the port 1433 of the server. Does anyone have any idea how to fix
this problem?
Shafiee.Are you able to ping the SQL Server? What error are you getting when you try
connecting to the server using Query Analyzer?
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"shafiee" <mohamed.shafee@.gmail.com> wrote in message
news:Ov0k0dSrFHA.304@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I'm having trouble connecting to the SQL server in a LAN. I can't even
> telnet to the port 1433 of the server. Does anyone have any idea how to
fix
> this problem?
> Shafiee.
>|||Hi Narayana,
Yes I am able to ping to the server. The server isn't listening to client
requests. The version of SQL server installed is SQL 2000. Any ideas?
Shafiee.
"Narayana Vyas Kondreddi" wrote:

> Are you able to ping the SQL Server? What error are you getting when you t
ry
> connecting to the server using Query Analyzer?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "shafiee" <mohamed.shafee@.gmail.com> wrote in message
> news:Ov0k0dSrFHA.304@.TK2MSFTNGP11.phx.gbl...
> fix
>
>|||If SQL Server is running and you can ping the server, one
possibility is that the server is listening on shared memory
only which means only local connections will be allowed. Use
the server network utility on the SQL Server box to make
sure you have protocols enabled. You can also check the SQL
Server error log from when the instance started to see what
protocols, ports SQL Server is listening on. If it's only
Shared Memory, enable TCP/IP on the server using the server
network utility.
-Sue
On Tue, 30 Aug 2005 19:59:04 -0700, "Shafiee"
<Shafiee@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Narayana,
>Yes I am able to ping to the server. The server isn't listening to client
>requests. The version of SQL server installed is SQL 2000. Any ideas?
>Shafiee.
>"Narayana Vyas Kondreddi" wrote:
>

Cant connect to sql 2000 from client with all field available i.e server ip and port

cant connect to sql server 2000 from c# 2003

Hi,

Could you please post more information on the specific error and conditions? Please take a look at the following guideline:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

In addition, how are you providing the IP address and Port? As per Books Online the format should be:

tcp:<IP Address>[\instancename],<port>

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Can't connect to reporting server using SQL Server Management Studio

Dear all,

I can't connect to the reporting server using SQL Server Management Studio. Do I need to put any port number to the exception list of the firewall ?

Thanks.

Best regards,

Michael Wu

What error do you get? Try using the server name or report server url (the default is http://<servername>/reportserver).