tcp/ip vs named pipes

From: "Fabio Martins" <support.msNOSPAMPLZ@xxxxxxxxxxxxxxxx>
Date: Tue, 8 Jul 2008 11:58:39 -0300

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
  - From: Roy Harvey (SQL Server MVP)

Prev by Date: Re: uninstall SQL Server Enterprise Manager Client
Next by Date: Re: tcp/ip vs named pipes
Previous by thread: Re: uninstall SQL Server Enterprise Manager Client
Next by thread: Re: tcp/ip vs named pipes
Index(es):
- Date
- Thread

Relevant Pages

Re: Change in Software Distribution Path
... Could you pull the network cable ... statically find server1 at 1.1.1.1 instead of 1.1.1.2 ... >What a pain! ... >over TCP/IP, WINS and several other solutions in a test ...
(microsoft.public.win2000.group_policy)
Re: tcp/ip vs named pipes
... telnet server1 1433 --> OK ... How can I fix that? ... Access Config on Server1 and Server2 are identical. ...
(microsoft.public.sqlserver.clients)