|
|
|
date: Tue, 8 Jul 2008 11:58:39 -0300,
group: microsoft.public.sqlserver.clients
back
Re: tcp/ip vs named pipes
Thankyou for answering! Follow the answers above:
> What's error message
Error connecting to database.
Code 10004: Unable to connect: SQL Server is unavailable or does not exist.
Unable to connect: SQL Server does not exist or network access denied.
> and how did you connect via tcp/ip?
In SQL client utility, if it's enabled only TCP/IP, App2 doesn't work, only
App1.
If it's enabled only named pipes, both applications only runs if I am
authenticated to the domain.
> I'd start by trying
> to connect to a different server instance using tcp/ip from teh machine
> that
> runs App2 just to make sure there is no problem with the SQL client tcp/ip
> connectivity setup/conifguration.
I'll do that, but i affirm that there's no firewall between client and
server, network configurations have already been reviewd.
> Then, try to connect to the SQL Server
> instance using just its IP address (plus port number). If that works, you
> have a name resolution problem. If that doesn't work, you need to start
> troubleshoot the network layer.
Hummm. I'll review our dns sufix configurations, that's one thing I have not
checked yet.
Thankyou again!
>
> Linchi
>
> "Fabio Martins" wrote:
>
>> 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
>>
>>
>>
date: Tue, 8 Jul 2008 14:15:37 -0300
author: Fabio Martins
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" escreveu na mensagem
news:0D215A88-2D39-4915-98B4-DE62A87B8E67@microsoft.com...
> 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" escreveu na mensagem
>> news:7DFC1CD4-9B45-4CB0-81E7-EFC6F0F189F4@microsoft.com...
>> > 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" escreveu na
>> >> mensagem
>> >> news:OnAfXLS4IHA.2336@TK2MSFTNGP03.phx.gbl...
>> >> > telnet server1 1433 --> OK
>> >> >
>> >> > telnet server2 1433 --> failed
>> >> >
>> >> > ??? How can I fix that?
>> >> >
>> >> > "Fabio Martins" escreveu na
>> >> > mensagem news:uYOcdsQ4IHA.2064@TK2MSFTNGP02.phx.gbl...
>> >> >> 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
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>
date: Wed, 9 Jul 2008 08:49:36 -0300
author: Fabio Martins
Re: tcp/ip vs named pipes
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" wrote in message
news:eqC8fnb4IHA.1428@TK2MSFTNGP06.phx.gbl...
> Yes! It is, as i said before "In SQL Server Network Utility TCP is enabled on port 1433.".
>
> Thankyou very much!
>
> FM
>
> "Linchi Shea" escreveu na mensagem
> news:0D215A88-2D39-4915-98B4-DE62A87B8E67@microsoft.com...
>> 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" escreveu na mensagem
>>> news:7DFC1CD4-9B45-4CB0-81E7-EFC6F0F189F4@microsoft.com...
>>> > 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" escreveu na
>>> >> mensagem
>>> >> news:OnAfXLS4IHA.2336@TK2MSFTNGP03.phx.gbl...
>>> >> > telnet server1 1433 --> OK
>>> >> >
>>> >> > telnet server2 1433 --> failed
>>> >> >
>>> >> > ??? How can I fix that?
>>> >> >
>>> >> > "Fabio Martins" escreveu na
>>> >> > mensagem news:uYOcdsQ4IHA.2064@TK2MSFTNGP02.phx.gbl...
>>> >> >> 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
>>> >> >>
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >>
>>>
>>>
>>>
>
>
date: Thu, 10 Jul 2008 00:48:46 +0200
author: Tibor Karaszi
Re: tcp/ip vs named pipes
Yes! In the error log "server SQL server listening on Shared Memory,
Named Pipes" ... as u can see, no "Listen on TCP". We'll apply Sql2000SP4
and then I'll post the results here.
FM
"Tibor Karaszi" escreveu
na mensagem news:ECF42201-52CA-45EC-A11D-FB892FF73452@microsoft.com...
> 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" wrote in message
> news:eqC8fnb4IHA.1428@TK2MSFTNGP06.phx.gbl...
>> Yes! It is, as i said before "In SQL Server Network Utility TCP is
>> enabled on port 1433.".
>>
>> Thankyou very much!
>>
>> FM
>>
>> "Linchi Shea" escreveu na mensagem
>> news:0D215A88-2D39-4915-98B4-DE62A87B8E67@microsoft.com...
>>> 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" escreveu na
>>>> mensagem
>>>> news:7DFC1CD4-9B45-4CB0-81E7-EFC6F0F189F4@microsoft.com...
>>>> > 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" escreveu na
>>>> >> mensagem
>>>> >> news:OnAfXLS4IHA.2336@TK2MSFTNGP03.phx.gbl...
>>>> >> > telnet server1 1433 --> OK
>>>> >> >
>>>> >> > telnet server2 1433 --> failed
>>>> >> >
>>>> >> > ??? How can I fix that?
>>>> >> >
>>>> >> > "Fabio Martins" escreveu na
>>>> >> > mensagem news:uYOcdsQ4IHA.2064@TK2MSFTNGP02.phx.gbl...
>>>> >> >> 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
>>>> >> >>
>>>> >> >
>>>> >> >
>>>> >>
>>>> >>
>>>> >>
>>>>
>>>>
>>>>
>>
>>
>
date: Fri, 11 Jul 2008 17:42:24 -0300
author: Fabio Martins
|
|
