Client computer able to connect server by wan?

Question

Dear all
Client computer able to connect oracle Database Server by wan? (not in lan)
at client computer's tnsnames.ora
(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 203.222.222.222)(PORT = 1521))) (CONNECT_DATA = (SID = kennam) (SERVER = SHARED) (SERVICE_NAME = kennam)))
like this?
did anyone tried this?

Answer 1

Justin, doesn't basic client come without any EXE's?
As far as I recall, it is just the OCI DLLs and one
or two message files. SQL*Plus is a separate download
and I doubt that tnsping is part of it.Are you talking about the Instant Client? That's more for application installers to bundle with their apps. I'm talking about the full-blown Oracle client (which is a multi-hundred MB download) that is more commonly installed out there. Ideally, of course, Oracle would be able to come up with some sort of middle ground between the two, something that isn't hideously bloated but that doesn't contain every possible bell and/or whistle.
For me, tnsping is very much a piece of useless
software. The name implies "testing the TNS alias".
It does not. A tnsping on a TNS alias can work, and
that exact same alias can fail to work when used via
SQL*Plus or another client - simply because tnsping
only validates that there is a Listener on that IP
and port. It does not validate anything else in that
TNS alias.
So what's the point..? One can just as well use
SQL*Plus to "ping" a TNS alias (using dummy username
and password) as this will also confirm the rest of
the data in the TNS alias.While tnsping isn't the most useful tool on the face of the planet, it does identify problems where you have multiple tnsnames files (i.e. multiple Oracle Homes) and the tns alias you just added is in the wrong file or cases where the tnsnames file has some sort of non-obvious formatting defect. Most of the time, folks have problems with the server and port in the TNS alias, so it does catch (in my experience) the majority of configuration problems.
Of course, you could also use SQL*Plus with a dummy username & password. If you're trying to help someone else debug a problem, though, particularly over the phone/ in forums, telling them to use tnsping tends to generate a lot fewer questions than telling them to use SQL*Plus with a dummy username & password. Particularly since lots of people assume that they can substitute their GUI of choice for SQL*Plus because 99% of the time they can, but in this one case you really, really mean SQL*Plus. Particularly with SQL Developer out there that can bypass the tnsnames file entirely using JDBC.
Justin