Cannot connect to SQL Server 2000.

I have installed Windows XP SP2 RC2 on a machine with SQL Server 2000. I ca
nnot connect to that machine's port 1433. I have disabled the Windows Firew
all. I have run netstat -a to check what ports are listening but I don't se
e port 1433 and port 1434.
I have not tried telnet to that port yet.Is this a default instance or a named instance.
A named instance need not listen on the 1433 port.
You can use the server network utility to find out what port sql is
listening on.
Then you can try telneting to that port.
hth
Vikram
"peter" <peter@.discussions.microsoft.com> wrote in message
news:1D686B59-EDFD-493D-A34C-72F68BE9D8CB@.microsoft.com...
> I have installed Windows XP SP2 RC2 on a machine with SQL Server 2000. I
cannot connect to that machine's port 1433. I have disabled the Windows
Firewall. I have run netstat -a to check what ports are listening but I
don't see port 1433 and port 1434.
> I have not tried telnet to that port yet.|||Hi Vikram,
This is a default instance and Server Network Utility is showing 1433.
I have tried telnet ip address 1433 on that Windows XP SP2 RC2 and cannot be
connected.
I have checked SQL Server Logs and noticed that SQL Server is only listening
on Shared Memory and Named Pipes. I have checked the log before XP SP2 RC2
is applied, the SQL Server was listening on TCP, Shared Memory and Named Pi
pes. How can I make SQL Se
rver listening on TCP? My understanding is that it should be based on what h
as been setup in the Server Network Utility. I have tried to disable and th
en enable TCP/IP but SQL Server is still only listening to Shared Memory and
Named Pipes.
"Vikram Vamshi" wrote:

> Is this a default instance or a named instance.
> A named instance need not listen on the 1433 port.
> You can use the server network utility to find out what port sql is
> listening on.
> Then you can try telneting to that port.
> hth
> Vikram
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:1D686B59-EDFD-493D-A34C-72F68BE9D8CB@.microsoft.com...
> cannot connect to that machine's port 1433. I have disabled the Windows
> Firewall. I have run netstat -a to check what ports are listening but I
> don't see port 1433 and port 1434.
>
>|||Hi Vikram,
I forget to mention in my last post that the SQL Server 2000 has only been a
pplied with SP2 not SP3a.
"peter" wrote:

> Hi Vikram,
> This is a default instance and Server Network Utility is showing 1433.
> I have tried telnet ip address 1433 on that Windows XP SP2 RC2 and cannot
be connected.
> I have checked SQL Server Logs and noticed that SQL Server is only listening on Sh
ared Memory and Named Pipes. I have checked the log before XP SP2 RC2 is applied, t
he SQL Server was listening on TCP, Shared Memory and Named Pipes. How can I make S
QL
Server listening on TCP? My understanding is that it should be based on what has been setup
in the Server Network Utility. I have tried to disable and then enable TCP/IP but SQL Serve
r is still only listening to Shared Memory and Named Pipes.[vbcol=seagreen]
> "Vikram Vamshi" wrote:
>|||Did you look at your sql server log?
If it is listening on tcp/ip it should have something like:
2004-06-18 20:01:46.93 server Using 'SSNETLIB.DLL' version '8.0.818'.
2004-06-18 20:01:46.95 server SQL server listening on 192.168.0.101:
1433.
2004-06-18 20:01:46.95 server SQL server listening on 127.0.0.1: 1433.
2004-06-18 20:01:46.96 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-06-18 20:01:46.96 server SQL Server is ready for client connections
hth
Vikram
Vikram Vamshi
Eclipsys Corporation
"peter" <peter@.discussions.microsoft.com> wrote in message
news:28229D3F-05BB-4354-A333-870335CDD1E4@.microsoft.com...
> Hi Vikram,
> I forget to mention in my last post that the SQL Server 2000 has only been
applied with SP2 not SP3a.[vbcol=seagreen]
> "peter" wrote:
>
cannot be connected.[vbcol=seagreen]
listening on Shared Memory and Named Pipes. I have checked the log before
XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
and Named Pipes. How can I make SQL Server listening on TCP? My
understanding is that it should be based on what has been setup in the
Server Network Utility. I have tried to disable and then enable TCP/IP but
SQL Server is still only listening to Shared Memory and Named Pipes.[vbcol=seagreen]
2000. I[vbcol=seagreen]
Windows[vbcol=seagreen]
I[vbcol=seagreen]|||Sorry,
I did not read your post completely.
You may want to check the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketNet
Lib\Tcp
tcpport should be 1433
Vikram
--
Vikram Vamshi
Eclipsys Corporation
"Vikram Vamshi" <vikram.vamshi@.nospam.com> wrote in message
news:eQMqdyyVEHA.384@.TK2MSFTNGP10.phx.gbl...
> Did you look at your sql server log?
> If it is listening on tcp/ip it should have something like:
> 2004-06-18 20:01:46.93 server Using 'SSNETLIB.DLL' version '8.0.818'.
> 2004-06-18 20:01:46.95 server SQL server listening on 192.168.0.101:
> 1433.
> 2004-06-18 20:01:46.95 server SQL server listening on 127.0.0.1: 1433.
> 2004-06-18 20:01:46.96 server SQL server listening on TCP, Shared
Memory,
> Named Pipes.
> 2004-06-18 20:01:46.96 server SQL Server is ready for client
connections
> hth
> Vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:28229D3F-05BB-4354-A333-870335CDD1E4@.microsoft.com...
been[vbcol=seagreen]
> applied with SP2 not SP3a.
> cannot be connected.
> listening on Shared Memory and Named Pipes. I have checked the log before
> XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
> and Named Pipes. How can I make SQL Server listening on TCP? My
> understanding is that it should be based on what has been setup in the
> Server Network Utility. I have tried to disable and then enable TCP/IP
but
> SQL Server is still only listening to Shared Memory and Named Pipes.
> 2000. I
> Windows
but[vbcol=seagreen]
> I
>|||And you missed my 3rd post
Did you check the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketNet
Lib\Tcp
tcpport should be 1433
vikram
Vikram Vamshi
Eclipsys Corporation
"peter" <peter@.discussions.microsoft.com> wrote in message
news:F3928A71-8F08-4C0A-AD09-D2CB6297BEC6@.microsoft.com...
> Hi Vikram,
> I guess you missed my 2nd post. I repost part of 2nd post here:
> I have checked SQL Server Logs and noticed that SQL Server is only
> listening on Shared Memory and Named Pipes. I have checked the log before
> XP SP2 RC2 is applied, the SQL Server was listening on TCP, Shared Memory
> and Named Pipes. How can I make SQL Server listening on TCP? My
> understanding is that it should be based on what has been setup in the
> Server Network Utility. I have tried to disable and then enable TCP/IP
but
> SQL Server is still only listening to Shared Memory and Named Pipes.
> It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433).
But I think it cannot be true for MS to make such mistake.[vbcol=seagreen]
> "Vikram Vamshi" wrote:
>
1433.[vbcol=seagreen]
Memory,[vbcol=seagreen]
connections[vbcol=seagreen]
been[vbcol=seagreen]
1433.[vbcol=seagreen]
before[vbcol=seagreen]
Memory[vbcol=seagreen]
but[vbcol=seagreen]
is[vbcol=seagreen]
but[vbcol=seagreen]|||Hi Vikram,
I checked that registry and it has 1433.
It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433). But
I think it cannot be true for MS to make such mistake.
"Vikram Vamshi" wrote:

> Sorry,
> I did not read your post completely.
> You may want to check the following registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketN
et
> Lib\Tcp
> tcpport should be 1433
> Vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "Vikram Vamshi" <vikram.vamshi@.nospam.com> wrote in message
> news:eQMqdyyVEHA.384@.TK2MSFTNGP10.phx.gbl...
> Memory,
> connections
> been
> but
> but
>
>|||I very much doubt that (of course you can never be sure with M$ )
I heard that sp2 was a major security overhaul, but that should not change
the applications (like sql server).
Can you post your sql server errorlog?
also make sure that tcp is listed in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketNet
Lib
Vikram
Vikram Vamshi
Eclipsys Corporation
"peter" <peter@.discussions.microsoft.com> wrote in message
news:C40DF985-F005-4766-AE43-D06AFF9F6499@.microsoft.com...
> Hi Vikram,
> I checked that registry and it has 1433.
> It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433).
But I think it cannot be true for MS to make such mistake.[vbcol=seagreen]
> "Vikram Vamshi" wrote:
>
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketNet[vbc
ol=seagreen]
'8.0.818'.[vbcol=seagreen]
192.168.0.101:[vbcol=seagreen]
1433.[vbcol=seagreen]
only[vbcol=seagreen]
1433.[vbcol=seagreen]
before[vbcol=seagreen]
Memory[vbcol=seagreen]
TCP/IP[vbcol=seagreen]
is[vbcol=seagreen]
Server[vbcol=seagreen]
listening[vbcol=seagreen]|||Hi Vikram,
I did not miss your 3rd post, but I guess I'm posting my reply when you post
this one. Anyway, here is the reply:
Hi Vikram,
I checked that registry and it has 1433.
It seems that XP SP2 RC2 stops SQL Server from listening to TCP (1433). But
I think it cannot be true for MS to make such mistake.
"Vikram Vamshi" wrote:

> And you missed my 3rd post
> Did you check the registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketN
et
> Lib\Tcp
> tcpport should be 1433
> vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:F3928A71-8F08-4C0A-AD09-D2CB6297BEC6@.microsoft.com...
> but
> But I think it cannot be true for MS to make such mistake.
> 1433.
> Memory,
> connections
> been
> 1433.
> before
> Memory
> but
> is
> but
>
>