tnsping resolves but ORA-12154

There is one NT workstation with oracle 9.8.0 on it.
This has been added to a local tnsnames file and you can connect
locally.
When I try to connect externally I recieve

ORA-12154: TNS:could not resolve service name Tnsping works just fine
....


Your input here will be highly appreciated


Massa

What do you mean by 'When I try to connect externally' ?
Are you doing the tnsping on the same computer were the connection
fails?
If you are using another computer, then that is where the tnsnames.ora
file must be updated (the client) and possibly the sqlnet.ora file.
Otherwise, what you are describing should work.

Please provide more info.

What do you mean by 'When I try to connect externally' ?
Are you doing the tnsping on the same computer were the connection
fails?
If you are using another computer, then that is where the tnsnames.ora
file must be updated (the client) and possibly the sqlnet.ora file.
Otherwise, what you are describing should work.

Please provide more info.

I thought it should work too.

External Server is the remote Server .

And yes tnsnames is updated on the remote serve


Thanks a milion for your time

I thought it should work too.

External Server is the remote Server .

And yes tnsnames is updated on the remote serve


Thanks a milion for your time

It's not that I don't believe you, but ...

Can you do a screen capture of the following ... replacing abc1 with
your service name, and feel free to remove specific server name
information - both from the server with the problem:

tnsping abc1

sqlplus /nolog
set instance abc1

sorry to be so doubting, but ...

It's not that I don't believe you, but ...

Can you do a screen capture of the following ... replacing abc1 with
your service name, and feel free to remove specific server name
information - both from the server with the problem:

tnsping abc1

sqlplus /nolog
set instance abc1

sorry to be so doubting, but ...

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (COMMUNITY =
tcpnbo.world)(PROTO
COL = TCP)(Host = nb009984)(Port = 1521)) (CONNECT_DATA = (SID =
lwcrown) (GLOBA
L_NAME = lwcrown.world)))
OK (1030 msec)


SQL> set instance lwcrown
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL>

My passwords had been messed with .This is a classic example of make no
assumptions where a problem pops up...




G Quesnel wrote:
> It's not that I don't believe you, but ...
>
> Can you do a screen capture of the following ... replacing abc1 with
> your service name, and feel free to remove specific server name
> information - both from the server with the problem:
>
> tnsping abc1
>
> sqlplus /nolog
> set instance abc1
>
> sorry to be so doubting, but ...

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (COMMUNITY =
tcpnbo.world)(PROTO
COL = TCP)(Host = nb009984)(Port = 1521)) (CONNECT_DATA = (SID =
lwcrown) (GLOBA
L_NAME = lwcrown.world)))
OK (1030 msec)


SQL> set instance lwcrown
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL>

My passwords had been messed with .This is a classic example of make no
assumptions where a problem pops up...




G Quesnel wrote:
> It's not that I don't believe you, but ...
>
> Can you do a screen capture of the following ... replacing abc1 with
> your service name, and feel free to remove specific server name
> information - both from the server with the problem:
>
> tnsping abc1
>
> sqlplus /nolog
> set instance abc1
>
> sorry to be so doubting, but ...