Hi,
I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
it using telnet in port 1433, nothing happends.
I need to connect to this server via Internet.
How can I do?
Leo-Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
> Hi,
> I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I tes
t
> it using telnet in port 1433, nothing happends.
> I need to connect to this server via Internet.
> How can I do?
> Leo-
Have you enabled TCP on the Server? There should be a program "SQL Server
Client Configuration" on the server. If not, search for SVRNETCN.EXE on the
server. With this program you can check if TCP is enabled.
Second problem could be a firewall.
bye,
helmut|||I have enabled TCP port (1433). I can access to that port from any computer
in my intranet. But I cannot do this using my internet IP.
There's no router issue. I think it's due to Windows XP SP2 Firewall, but I
have open those ports to.
Leo-
"helmut woess" <hw@.iis.at> escribi en el mensaje
news:1nee56bcb93ir$.rpvg777x77c0.dlg@.40tude.net...
> Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
>
> Have you enabled TCP on the Server? There should be a program "SQL Server
> Client Configuration" on the server. If not, search for SVRNETCN.EXE on
> the
> server. With this program you can check if TCP is enabled.
> Second problem could be a firewall.
> bye,
> helmut
Showing posts with label port. Show all posts
Showing posts with label port. Show all posts
Saturday, February 25, 2012
cannot connect using tcp/ip
Hi,
I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
it using telnet in port 1433, nothing happends.
I need to connect to this server via Internet.
How can I do?
Leo-
Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
> Hi,
> I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
> it using telnet in port 1433, nothing happends.
> I need to connect to this server via Internet.
> How can I do?
> Leo-
Have you enabled TCP on the Server? There should be a program "SQL Server
Client Configuration" on the server. If not, search for SVRNETCN.EXE on the
server. With this program you can check if TCP is enabled.
Second problem could be a firewall.
bye,
helmut
|||I have enabled TCP port (1433). I can access to that port from any computer
in my intranet. But I cannot do this using my internet IP.
There's no router issue. I think it's due to Windows XP SP2 Firewall, but I
have open those ports to.
Leo-
"helmut woess" <hw@.iis.at> escribi en el mensaje
news:1nee56bcb93ir$.rpvg777x77c0.dlg@.40tude.net...
> Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
>
> Have you enabled TCP on the Server? There should be a program "SQL Server
> Client Configuration" on the server. If not, search for SVRNETCN.EXE on
> the
> server. With this program you can check if TCP is enabled.
> Second problem could be a firewall.
> bye,
> helmut
I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
it using telnet in port 1433, nothing happends.
I need to connect to this server via Internet.
How can I do?
Leo-
Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
> Hi,
> I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
> it using telnet in port 1433, nothing happends.
> I need to connect to this server via Internet.
> How can I do?
> Leo-
Have you enabled TCP on the Server? There should be a program "SQL Server
Client Configuration" on the server. If not, search for SVRNETCN.EXE on the
server. With this program you can check if TCP is enabled.
Second problem could be a firewall.
bye,
helmut
|||I have enabled TCP port (1433). I can access to that port from any computer
in my intranet. But I cannot do this using my internet IP.
There's no router issue. I think it's due to Windows XP SP2 Firewall, but I
have open those ports to.
Leo-
"helmut woess" <hw@.iis.at> escribi en el mensaje
news:1nee56bcb93ir$.rpvg777x77c0.dlg@.40tude.net...
> Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
>
> Have you enabled TCP on the Server? There should be a program "SQL Server
> Client Configuration" on the server. If not, search for SVRNETCN.EXE on
> the
> server. With this program you can check if TCP is enabled.
> Second problem could be a firewall.
> bye,
> helmut
Cannot Connect using IP to Clustered Named Instance
I am having trouble connecting when using the IP address to a named
instanced using dynamic port assignments and hosted on a 2K3 cluster (even
when at the console on the node hosting the SQL instance). I receive "SQL
Server does not exist or access denied". There are no entries created in
the event log. I am able to connect with no problems using the instance
name. I'm attempting to connect usingQuery Analyzer. Any ideas?
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
Hi Michael,
In order to connect to a Named Instance you need to either:
a. Supply the Servername\InstanceName
b. Supply the Servername, port
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||It seems that you have trouble connecting through TCP/IP. Verify in event log that SQL is listening on TCPIP and not only on Shared Memory / Named Pipes.
To verify that this is a problem from QueryAnalyzer try to connect with tcp:ServerName\InstanceName. If it isn't work then server is not listening on TCP at all...
post back after this and we will see what then...
Rgds
Sinisa Perovic
|||Thanks for the help.
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:51hmVwbIEHA.3636@.cpmsftngxa06.phx.gbl...
> Hi Michael,
> In order to connect to a Named Instance you need to either:
> a. Supply the Servername\InstanceName
> b. Supply the Servername, port
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
instanced using dynamic port assignments and hosted on a 2K3 cluster (even
when at the console on the node hosting the SQL instance). I receive "SQL
Server does not exist or access denied". There are no entries created in
the event log. I am able to connect with no problems using the instance
name. I'm attempting to connect usingQuery Analyzer. Any ideas?
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
Hi Michael,
In order to connect to a Named Instance you need to either:
a. Supply the Servername\InstanceName
b. Supply the Servername, port
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||It seems that you have trouble connecting through TCP/IP. Verify in event log that SQL is listening on TCPIP and not only on Shared Memory / Named Pipes.
To verify that this is a problem from QueryAnalyzer try to connect with tcp:ServerName\InstanceName. If it isn't work then server is not listening on TCP at all...
post back after this and we will see what then...
Rgds
Sinisa Perovic
|||Thanks for the help.
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:51hmVwbIEHA.3636@.cpmsftngxa06.phx.gbl...
> Hi Michael,
> In order to connect to a Named Instance you need to either:
> a. Supply the Servername\InstanceName
> b. Supply the Servername, port
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
Sunday, February 19, 2012
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
>
>
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
>
>
Cannot connect to SQL Server 2000.
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.
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 Pipes. How can I make SQL Se
rver 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.
"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 applied 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 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]
> "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\MSSQLServer\ 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[vbcol=seagreen]
> hth
> Vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:28229D3F-05BB-4354-A333-870335CDD1E4@.microsoft.com...
been
> 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[vbcol=seagreen]
> SQL Server is still only listening to Shared Memory and Named Pipes.
> 2000. I
> Windows
but
> I
>
|||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.
"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...
> 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
> I
>
>
|||And you missed my 3rd post
Did you check the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ 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 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\MSSQLServer\ 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...
> but
> But I think it cannot be true for MS to make such mistake.
> 1433.
> Memory,
> connections
> been
> 1433.
> before
> Memory
> but
> is
> but
>
>
|||Hi Vikram,
I will listen to the XP SP2 and SQL Server webcast to see whether there is anything about this.
"peter" wrote:
[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:
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 Pipes. How can I make SQL Se
rver 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.
"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 applied 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 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]
> "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\MSSQLServer\ 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[vbcol=seagreen]
> hth
> Vikram
> --
> Vikram Vamshi
> Eclipsys Corporation
> "peter" <peter@.discussions.microsoft.com> wrote in message
> news:28229D3F-05BB-4354-A333-870335CDD1E4@.microsoft.com...
been
> 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[vbcol=seagreen]
> SQL Server is still only listening to Shared Memory and Named Pipes.
> 2000. I
> Windows
but
> I
>
|||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.
"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...
> 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
> I
>
>
|||And you missed my 3rd post
Did you check the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ 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 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\MSSQLServer\ 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...
> but
> But I think it cannot be true for MS to make such mistake.
> 1433.
> Memory,
> connections
> been
> 1433.
> before
> Memory
> but
> is
> but
>
>
|||Hi Vikram,
I will listen to the XP SP2 and SQL Server webcast to see whether there is anything about this.
"peter" wrote:
[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:
Cannot connect to SQL instance without port information
Hi all,
More likely this is a change in your environment. You don't say which
version of SQL Server you are using, but with SQL 2005 I think the
requirement is that the Browser service is running. On SQL 2000, you
need to be able to access port 1434 on UDP.
>
More likely this is a change in your environment. You don't say which
version of SQL Server you are using, but with SQL 2005 I think the
requirement is that the Browser service is running. On SQL 2000, you
need to be able to access port 1434 on UDP.
>
In both cases, firewalls may get in the way.
>
>
Is there a reason you can't connect using Server\Instance type syntax?
I'm having some trouble with connecting to SQL server instance lately
without adding a port number. I used to be able to always connect to
instance without having to input SQLSERVER,portnumber. However now
this is not the case. I doing this through an ADO connection object,
and creating the connection string. Does anyone know if there was a
recent Microsoft update or patch that would've cause this to stop
allowing me to connect to a SQL instance without having to put in the
port information? Thanks.Flash08 (stuart.karp@.gmail.com) writes:
Quote:
Originally Posted by
I'm having some trouble with connecting to SQL server instance lately
without adding a port number. I used to be able to always connect to
instance without having to input SQLSERVER,portnumber. However now
this is not the case. I doing this through an ADO connection object,
and creating the connection string. Does anyone know if there was a
recent Microsoft update or patch that would've cause this to stop
allowing me to connect to a SQL instance without having to put in the
port information? Thanks.
More likely this is a change in your environment. You don't say which
version of SQL Server you are using, but with SQL 2005 I think the
requirement is that the Browser service is running. On SQL 2000, you
need to be able to access port 1434 on UDP.
In both cases, firewalls may get in the way.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland Sommarskog <esquel@.sommarskog.sewrote in
news:Xns996556346440Yazorman@.127.0.0.1:
Quote:
Originally Posted by
Flash08 (stuart.karp@.gmail.com) writes:
Quote:
Originally Posted by
>I'm having some trouble with connecting to SQL server instance lately
>without adding a port number. I used to be able to always connect to
>instance without having to input SQLSERVER,portnumber. However now
>this is not the case. I doing this through an ADO connection object,
>and creating the connection string. Does anyone know if there was a
>recent Microsoft update or patch that would've cause this to stop
>allowing me to connect to a SQL instance without having to put in the
>port information? Thanks.
>
More likely this is a change in your environment. You don't say which
version of SQL Server you are using, but with SQL 2005 I think the
requirement is that the Browser service is running. On SQL 2000, you
need to be able to access port 1434 on UDP.
>
In both cases, firewalls may get in the way.
>
>
Is there a reason you can't connect using Server\Instance type syntax?
Friday, February 10, 2012
cannot connect to a named instance via TCP/IP
Are you connecting to your office through VPN or is your
firewall just configured to allow you to access port 1433?
If it is the latter, you must configure your firewall to
allow you access on the port that the named instance is
listening on (each instance has its own port and only the
default instance will be listening on 1433). You can
find the port the named instance is using by looking at
the TCP/IP properties for the instance in the server
network utility.
Hope this helps.
Tim
office.
sql server, say SQL_instance1.
named instance from my home workstation. Therefore, I
have already set a portmapping (1433) on my company
firewall and use the IP address, say 61.88.17.3, to
connect the sql server at my home.
the EM and the error message is "SQL server not found or
access denied". I am sure the login name and password is
correct and the firewall setting is correct also (Since I
can use telnet to connect the server, the command is :
telnet 61.88.17.3 1433).
remote sql server in my workstation EM.
I use 1433 for my named instance and the I have configured the firewall to a
llow 1433.
I even try to configure the firewall to allow all TCP/IP, but I still cannot
connect to my SQL server.
-- Tim Richardson wrote: --
Are you connecting to your office through VPN or is your
firewall just configured to allow you to access port 1433?
If it is the latter, you must configure your firewall to
allow you access on the port that the named instance is
listening on (each instance has its own port and only the
default instance will be listening on 1433). You can
find the port the named instance is using by looking at
the TCP/IP properties for the instance in the server
network utility.
Hope this helps.
Tim
sql server, say SQL_instance1.
named instance from my home workstation. Therefore, I
have already set a portmapping (1433) on my company
firewall and use the IP address, say 61.88.17.3, to
connect the sql server at my home.
the EM and the error message is "SQL server not found or
access denied". I am sure the login name and password is
correct and the firewall setting is correct also (Since I
can use telnet to connect the server, the command is :
telnet 61.88.17.3 1433).
firewall just configured to allow you to access port 1433?
If it is the latter, you must configure your firewall to
allow you access on the port that the named instance is
listening on (each instance has its own port and only the
default instance will be listening on 1433). You can
find the port the named instance is using by looking at
the TCP/IP properties for the instance in the server
network utility.
Hope this helps.
Tim
quote:
>--Original Message--
>Hi all,
>I have a SQL server running on a WIN2k server at my
office.
quote:
>I have an application running on a named instance of the
sql server, say SQL_instance1.
quote:
>Due to some reason, I have to connect to the SQL server
named instance from my home workstation. Therefore, I
have already set a portmapping (1433) on my company
firewall and use the IP address, say 61.88.17.3, to
connect the sql server at my home.
quote:
>However, I find that I cannot register the sql server at
the EM and the error message is "SQL server not found or
access denied". I am sure the login name and password is
correct and the firewall setting is correct also (Since I
can use telnet to connect the server, the command is :
telnet 61.88.17.3 1433).
quote:
>Anyone know how to solve this problem '
>I use the following connection string to register the
remote sql server in my workstation EM.
quote:thx for your reply.
>61.88.17.3\SQL_instance1
>Thank in advance
>Regards,
>ong
>.
>
I use 1433 for my named instance and the I have configured the firewall to a
llow 1433.
I even try to configure the firewall to allow all TCP/IP, but I still cannot
connect to my SQL server.
-- Tim Richardson wrote: --
Are you connecting to your office through VPN or is your
firewall just configured to allow you to access port 1433?
If it is the latter, you must configure your firewall to
allow you access on the port that the named instance is
listening on (each instance has its own port and only the
default instance will be listening on 1433). You can
find the port the named instance is using by looking at
the TCP/IP properties for the instance in the server
network utility.
Hope this helps.
Tim
quote:
>--Original Message--
>Hi all,
office.[QUOTE]
>I have an application running on a named instance of the
sql server, say SQL_instance1.
quote:
>Due to some reason, I have to connect to the SQL server
named instance from my home workstation. Therefore, I
have already set a portmapping (1433) on my company
firewall and use the IP address, say 61.88.17.3, to
connect the sql server at my home.
quote:
>However, I find that I cannot register the sql server at
the EM and the error message is "SQL server not found or
access denied". I am sure the login name and password is
correct and the firewall setting is correct also (Since I
can use telnet to connect the server, the command is :
telnet 61.88.17.3 1433).
quote:
>Anyone know how to solve this problem '
remote sql server in my workstation EM.[QUOTE]
>61.88.17.3\SQL_instance1
>ong
>.
>
Subscribe to:
Posts (Atom)