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

What's error message and how did you connect via tcp/ip? 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. 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.

Linchi

"Fabio Martins" wrote:

What's error message and how did you connect via tcp/ip? 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. 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.

Linchi

"Fabio Martins" wrote:

What's error message and how did you connect via tcp/ip? 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. 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.

Linchi

"Fabio Martins" wrote:

What's error message and how did you connect via tcp/ip? 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. 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.

Linchi

"Fabio Martins" wrote:

What's error message and how did you connect via tcp/ip? 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. 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.

Linchi

"Fabio Martins" wrote:

What's error message and how did you connect via tcp/ip? 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. 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.

Linchi

"Fabio Martins" wrote:

What's error message and how did you connect via tcp/ip? 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. 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.

Linchi

"Fabio Martins" wrote:

What's error message and how did you connect via tcp/ip? 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. 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.

Linchi

"Fabio Martins" wrote:

What's error message and how did you connect via tcp/ip? 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. 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.

Linchi

"Fabio Martins" wrote: