tcp/ip vs named pipes

#41

telnet server1 1433 --> OK

telnet server2 1433 --> failed

??? How can I fix that?

"Fabio Martins" <support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> escreveu na mensagem
news:uYOcdsQ4IHA.2064 (AT) TK2MSFTNGP02 (DOT) phx.gbl...

Quote:

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

#42

I think I found the problem, but don't know how to solve.
I have never had contact with sql server before.

I can ping, but can't telnet on port 1433.
On server1 telnet on port 1433 is OK.

The same sql services are running on both.

FM

"Roy Harvey (SQL Server MVP)" <roy_harvey (AT) snet (DOT) net> escreveu na mensagem
news:dq9774t57s12sl53gbggddou7avvfl5gh6 (AT) 4ax (DOT) com...

Quote:

The first question is whether App2 can find Server2. The first thing
to check is that the client running App2 can ping the IP address of
Server2. If it can not you have a network routing issue. The second
test is can it ping Server2 by name. If it can not you have a DNS
name resolution problem. At least if you get that far you have
eliminated some of the potential problems.

Note that some installations block PING at the routers.

Roy Harvey
Beacon Falls, CT

On Tue, 8 Jul 2008 11:58:39 -0300, "Fabio Martins"
support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> 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

#43

I think I found the problem, but don't know how to solve.
I have never had contact with sql server before.

I can ping, but can't telnet on port 1433.
On server1 telnet on port 1433 is OK.

The same sql services are running on both.

FM

"Roy Harvey (SQL Server MVP)" <roy_harvey (AT) snet (DOT) net> escreveu na mensagem
news:dq9774t57s12sl53gbggddou7avvfl5gh6 (AT) 4ax (DOT) com...

Quote:

The first question is whether App2 can find Server2. The first thing
to check is that the client running App2 can ping the IP address of
Server2. If it can not you have a network routing issue. The second
test is can it ping Server2 by name. If it can not you have a DNS
name resolution problem. At least if you get that far you have
eliminated some of the potential problems.

Note that some installations block PING at the routers.

Roy Harvey
Beacon Falls, CT

On Tue, 8 Jul 2008 11:58:39 -0300, "Fabio Martins"
support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> 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

#44

I think I found the problem, but don't know how to solve.
I have never had contact with sql server before.

I can ping, but can't telnet on port 1433.
On server1 telnet on port 1433 is OK.

The same sql services are running on both.

FM

"Roy Harvey (SQL Server MVP)" <roy_harvey (AT) snet (DOT) net> escreveu na mensagem
news:dq9774t57s12sl53gbggddou7avvfl5gh6 (AT) 4ax (DOT) com...

Quote:

The first question is whether App2 can find Server2. The first thing
to check is that the client running App2 can ping the IP address of
Server2. If it can not you have a network routing issue. The second
test is can it ping Server2 by name. If it can not you have a DNS
name resolution problem. At least if you get that far you have
eliminated some of the potential problems.

Note that some installations block PING at the routers.

Roy Harvey
Beacon Falls, CT

On Tue, 8 Jul 2008 11:58:39 -0300, "Fabio Martins"
support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> 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

#45

I think I found the problem, but don't know how to solve.
I have never had contact with sql server before.

I can ping, but can't telnet on port 1433.
On server1 telnet on port 1433 is OK.

The same sql services are running on both.

FM

"Roy Harvey (SQL Server MVP)" <roy_harvey (AT) snet (DOT) net> escreveu na mensagem
news:dq9774t57s12sl53gbggddou7avvfl5gh6 (AT) 4ax (DOT) com...

Quote:

The first question is whether App2 can find Server2. The first thing
to check is that the client running App2 can ping the IP address of
Server2. If it can not you have a network routing issue. The second
test is can it ping Server2 by name. If it can not you have a DNS
name resolution problem. At least if you get that far you have
eliminated some of the potential problems.

Note that some installations block PING at the routers.

Roy Harvey
Beacon Falls, CT

On Tue, 8 Jul 2008 11:58:39 -0300, "Fabio Martins"
support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> 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

#46

I think I found the problem, but don't know how to solve.
I have never had contact with sql server before.

I can ping, but can't telnet on port 1433.
On server1 telnet on port 1433 is OK.

The same sql services are running on both.

FM

"Roy Harvey (SQL Server MVP)" <roy_harvey (AT) snet (DOT) net> escreveu na mensagem
news:dq9774t57s12sl53gbggddou7avvfl5gh6 (AT) 4ax (DOT) com...

Quote:

The first question is whether App2 can find Server2. The first thing
to check is that the client running App2 can ping the IP address of
Server2. If it can not you have a network routing issue. The second
test is can it ping Server2 by name. If it can not you have a DNS
name resolution problem. At least if you get that far you have
eliminated some of the potential problems.

Note that some installations block PING at the routers.

Roy Harvey
Beacon Falls, CT

On Tue, 8 Jul 2008 11:58:39 -0300, "Fabio Martins"
support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> 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

#47

I think I found the problem, but don't know how to solve.
I have never had contact with sql server before.

I can ping, but can't telnet on port 1433.
On server1 telnet on port 1433 is OK.

The same sql services are running on both.

FM

"Roy Harvey (SQL Server MVP)" <roy_harvey (AT) snet (DOT) net> escreveu na mensagem
news:dq9774t57s12sl53gbggddou7avvfl5gh6 (AT) 4ax (DOT) com...

Quote:

The first question is whether App2 can find Server2. The first thing
to check is that the client running App2 can ping the IP address of
Server2. If it can not you have a network routing issue. The second
test is can it ping Server2 by name. If it can not you have a DNS
name resolution problem. At least if you get that far you have
eliminated some of the potential problems.

Note that some installations block PING at the routers.

Roy Harvey
Beacon Falls, CT

On Tue, 8 Jul 2008 11:58:39 -0300, "Fabio Martins"
support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> 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

#48

I think I found the problem, but don't know how to solve.
I have never had contact with sql server before.

I can ping, but can't telnet on port 1433.
On server1 telnet on port 1433 is OK.

The same sql services are running on both.

FM

"Roy Harvey (SQL Server MVP)" <roy_harvey (AT) snet (DOT) net> escreveu na mensagem
news:dq9774t57s12sl53gbggddou7avvfl5gh6 (AT) 4ax (DOT) com...

Quote:

The first question is whether App2 can find Server2. The first thing
to check is that the client running App2 can ping the IP address of
Server2. If it can not you have a network routing issue. The second
test is can it ping Server2 by name. If it can not you have a DNS
name resolution problem. At least if you get that far you have
eliminated some of the potential problems.

Note that some installations block PING at the routers.

Roy Harvey
Beacon Falls, CT

On Tue, 8 Jul 2008 11:58:39 -0300, "Fabio Martins"
support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> 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

#49

I think I found the problem, but don't know how to solve.
I have never had contact with sql server before.

I can ping, but can't telnet on port 1433.
On server1 telnet on port 1433 is OK.

The same sql services are running on both.

FM

"Roy Harvey (SQL Server MVP)" <roy_harvey (AT) snet (DOT) net> escreveu na mensagem
news:dq9774t57s12sl53gbggddou7avvfl5gh6 (AT) 4ax (DOT) com...

Quote:

The first question is whether App2 can find Server2. The first thing
to check is that the client running App2 can ping the IP address of
Server2. If it can not you have a network routing issue. The second
test is can it ping Server2 by name. If it can not you have a DNS
name resolution problem. At least if you get that far you have
eliminated some of the potential problems.

Note that some installations block PING at the routers.

Roy Harvey
Beacon Falls, CT

On Tue, 8 Jul 2008 11:58:39 -0300, "Fabio Martins"
support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> 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

#50

I think I found the problem, but don't know how to solve.
I have never had contact with sql server before.

I can ping, but can't telnet on port 1433.
On server1 telnet on port 1433 is OK.

The same sql services are running on both.

FM

"Roy Harvey (SQL Server MVP)" <roy_harvey (AT) snet (DOT) net> escreveu na mensagem
news:dq9774t57s12sl53gbggddou7avvfl5gh6 (AT) 4ax (DOT) com...

Quote:

The first question is whether App2 can find Server2. The first thing
to check is that the client running App2 can ping the IP address of
Server2. If it can not you have a network routing issue. The second
test is can it ping Server2 by name. If it can not you have a DNS
name resolution problem. At least if you get that far you have
eliminated some of the potential problems.

Note that some installations block PING at the routers.

Roy Harvey
Beacon Falls, CT

On Tue, 8 Jul 2008 11:58:39 -0300, "Fabio Martins"
support.msNOSPAMPLZ (AT) fabiomartins (DOT) net> 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