| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|  |  | |||
Home -> Community -> Usenet -> c.d.o.misc -> Re: database connectivity/tnsping problem
Thomas Hesse <thomas.hesse_at_team.xtra.co.nz.nospam> wrote in message news:<3E3F0A6B.2090904_at_team.xtra.co.nz.nospam>...
> B. Kloppt wrote:
> > Hi everyone,
> > 
> > i've got a problem which i haven't been able to solve.
> > 
> > my company has two domains, which are connected using a vpn router.
> > my domain (domain.ny) has the ip range 192.168.1.x and the second
> > domain (domain.la) has the ip range 192.168.2.x
> > in both domains we've got an oracle server running under linux.
> > in both domains workstations can connect to databases in their own
> > domain with sqlplus.
> > 
> > we cannot, however, cross-domain connect.
> > not even a tnsping works correctly.
> > this is the output of tnsping when pinging from a station in the first
> > domain (domain.ny):
> > 
> > ---8<-----------------------------------------------------------------------------
> > [oracle_at_dbserver:~]$ tnsping orcl.domain.la
> > 
> > TNS Ping Utility for Linux: Version 9.2.0.1.0 - Production on
> > 02-FEB-2003 20:53:53
> > 
> > Copyright (c) 1997 Oracle Corporation.  All rights reserved.
> > 
> > Used parameter files:
> > /opt/oracle/product/9.2.0/network/admin/sqlnet.ora
> > 
> > TNS-03505: Failed to resolve name
> > ---8<-----------------------------------------------------------------------------
> > 
> > 
> > a tnsping to the ip-address brings me the desired results, however:
> > 
> > ---8<-----------------------------------------------------------------------------
> > [oracle_at_dbserver:~]$ tnsping 192.168.2.25
> > 
> > 
> > TNS Ping Utility for Linux: Version 9.2.0.1.0 - Production on
> > 02-FEB-2003 20:54:37
> > 
> > Copyright (c) 1997 Oracle Corporation.  All rights reserved.
> > 
> > Used parameter files:
> > /opt/oracle/product/9.2.0/network/admin/sqlnet.ora
> > 
> > Used HOSTNAME adapter to resolve the alias
> > Attempting to contact
> > (DESCRIPTION=(CONNECT_DATA=(SID=*)(SERVICE_NAME=192.168.2.25))(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.2.25)(PORT=1521)))
> > OK (490 msec)
> > ---8<-----------------------------------------------------------------------------
> > 
> > trying to connect to our server from a workstation in the second
> > domain brings the same results.
> > i have double-checked my tnsname.ora file, which has the following
> > section defined:
> > 
> > ORCL.DOMAIN.LA
> >   (DESCRIPTION =
> >     (ADDRESS_LIST =
> >       (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.2.25)(PORT = 1521))
> >     )
> >     (CONNECT_DATA =
> >       (SERVICE_NAME = ORCL)
> >     )
> >   )
> > 
> > 
> > i have even set NAMES.DEFAULT_DOMAIN = world in the sqlnet.ora file as
> > well.
> > 
> > i must be missing something else.
> > can anyone help me?
> > 
> > thanks in advance.
> 
> 
> try that:
> 
> SQLNET.ORA:
>    names.directory_path = (TNSNAMES)
>    #NAMES.DEFAULT_DOMAIN = world
> 
> TNSNAMES.ORA:
>   ORCL
>    (DESCRIPTION =
>      (ADDRESS_LIST =
>        (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.2.25)(PORT = 1521))
>      )
>      (CONNECT_DATA =
>        (SERVICE_NAME = ORCL)
>      )
>    )
> 
> tnsping orcl
>    or/and
> tnsping orcl.world
hi thomas,
thanks for your reply.
i tried this, but to no avail. i'm still getting the same error
message.
i wanted to say, though, that i have found out something else that's
strange:
i can tnsping from either server to the other without errors!!
it's only when i tnsping from one workstation (where only the oracle
client is installed) of one domain to the server of another domain
that gives me errors.
to put it bluntly:
tnsping workstation.domain.ny -> dbserver.domain.ny : NO ERROR
tnsping workstation.domain.la -> dbserver.domain.la : NO ERROR
tnsping dbserver.domain.ny -> dbserver.domain.la : NO ERROR
tnsping dbserver.domain.la -> dbserver.domain.ny : NO ERROR
tnsping workstation.domain.ny -> dbserver.domain.la : TNS-03505:
Failed to resolve name
tnsping workstation.domain.la -> dbserver.domain.ny : TNS-03505:
Failed to resolve name
could this have something to do with the client software? Received on Wed Feb 05 2003 - 05:06:33 CST
|  |  |