Re: tcp/ip vs named pipes
- From: "Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 10 Jul 2008 00:48:46 +0200
Anything in the errorlog file?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fabio Martins" <support.msNOSPAMPLZ@xxxxxxxxxxxxxxxx> wrote in message news:eqC8fnb4IHA.1428@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxFor 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
>> >>
>> >
>> >
>>
>>
>>
.
- Follow-Ups:
- Re: tcp/ip vs named pipes
- From: Fabio Martins
- Re: tcp/ip vs named pipes
- References:
- tcp/ip vs named pipes
- From: Fabio Martins
- Re: tcp/ip vs named pipes
- From: Fabio Martins
- Re: tcp/ip vs named pipes
- From: Fabio Martins
- Re: tcp/ip vs named pipes
- From: Linchi Shea
- Re: tcp/ip vs named pipes
- From: Fabio Martins
- Re: tcp/ip vs named pipes
- From: Linchi Shea
- Re: tcp/ip vs named pipes
- From: Fabio Martins
- tcp/ip vs named pipes
- Prev by Date: Re: tcp/ip vs named pipes
- Next by Date: Re:Timeout expired. The timeout period elapsed prior to completion o
- Previous by thread: Re: tcp/ip vs named pipes
- Next by thread: Re: tcp/ip vs named pipes
- Index(es):
Relevant Pages
|
Loading