Re: tcp/ip vs named pipes

Yes! It is, as i said before "In SQL Server Network Utility TCP is enabled
on port 1433.".

Thankyou very much!

FM

"Linchi Shea" <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx> escreveu na mensagem
news:0D215A88-2D39-4915-98B4-DE62A87B8E67@xxxxxxxxxxxxxxxx
For SQL2000, try Start -> Programs -> Microsoft SQL Server -> Server
Network
Utility, and check if TCP/IP is among the enabled protocols.

Linchi

"Fabio Martins" wrote:

No.. it's Sqlserver std 2000 SP3 on Windows Server 2003.

I think that's a bug on Sqlserver std 2000 SP3 over Windows Server 2003
(some other foruns reported that). We will apply SP4 on SQLServer and
then
I'll post the results.

Thankyou!

FM

"Linchi Shea" <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx> escreveu na mensagem
news:7DFC1CD4-9B45-4CB0-81E7-EFC6F0F189F4@xxxxxxxxxxxxxxxx
If this is SQL2005, on the server, go to Start -> Programs -> Microsoft
SQL
Server 2005 -> Configuration Tools -> SQL Server Configuration Manager.
Under
Protocol for MSSQLSERVER, you can choose to enable TCP/IP.

Linchi

"Fabio Martins" wrote:

little by little I am learning sqlserver!!

Log on server1:
"server SQL server listening on TCP, Shared Memory, Named Pipes."

Log on server2:
"server SQL server listening on Shared Memory, Named Pipes."

How can I enable server2 to listen on TCP too?

In SQL Server Network Utility TCP is enabled on port 1433.

Thankyou in advance!

"Fabio Martins" <support.msNOSPAMPLZ@xxxxxxxxxxxxxxxx> escreveu na
mensagem
news:OnAfXLS4IHA.2336@xxxxxxxxxxxxxxxxxxxxxxx
telnet server1 1433 --> OK

telnet server2 1433 --> failed

??? How can I fix that?

"Fabio Martins" <support.msNOSPAMPLZ@xxxxxxxxxxxxxxxx> escreveu na
mensagem news:uYOcdsQ4IHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
Hi Guys... I have 2 aplications App1 and App2.

App1 access Server1 (Sqlserver ent 2000 SP4) through tcp/ip OK!
App1 access Server1 (Sqlserver ent 2000 SP4) through named pipes
OK!

App2 access Server2 (Sqlserver std 2000 SP3) can't access through
tcp/ip
:(
App2 access Server2 (Sqlserver std 2000 SP3) through named pipes
OK!

Access Config on Server1 and Server2 are identical.
I'd like app2 access server 2 through tcp/ip.
How can I solve that?

FM











.

Relevant Pages

  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... I also checked the individual patch levels for the .NET drivers, SQL Server ... The SQL Server is fully patched, however Windows Update reported that the OS ... Lock pages in memory -- I guess you might have taken care of it as well. ...
    (microsoft.public.sqlserver.clustering)
  • RE: migrating from wmsde to sql server
    ... Click Start, point to All Programs\Microsoft SQL Server, and then click ... then click New SQL Server Registration. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Best replication architecture?
    ... Looking for a SQL Server replication book? ... So if it is subscribing to Publisher 1, ...
    (microsoft.public.sqlserver.replication)
Loading