| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle SQLNET through DSL connection
Yet more info. I re-installed oracle client; still no luck. I found
a post somewhere that suggested entering 'use_shared_socket' in
hklm\software\oracle\<home> and setting value to true would solve it,
but that a) didn't solve it and b) caused my other working remote
connections to encounter an ora-12537 TNS: connection closed error.
So to recap - I have two laptops side by side, both have oracle 8.1.7 db and 6i forms loaded. Both have same vpn software loaded (checkpoint securemote). Both can connect via RAS (private network connection) and access the db, but only one can connect via public network (dialup+VPN, or DSL+VPN). Since one can connect remotely, this tends to rule out server-side issues. Also, since a dialup works on one, timeouts don't seem to be the issue (DSL is failing on the other, and my dsl connection is fast). The 'failing' computer has generally great connectivity to network via vpn (can use all other services I can think of).
The error in the trace file that matters is, I believe, 'nsopen: unable to open transport'.
I've tried using both 'clients' - eg, sqlplus from the ora 8i home, and sqlplus from fhe ora dev 6i home. Both fail with the same error in the trace, but ... the ora 8i home version gives me a TNS 12535 at the user-interface level, while the ora dev 6i home gives me a slightly different error - 12203.
I've also done a 'ping -f -l <packetsize> <dbserver ip> and used packetsize of 1470, 1472,and 1774 - 1472 is the max size that works without fragmentation. This applies equally to both working and non-working connections (both machines, ras and vpn).
On Sun, 03 Nov 2002 19:29:17 GMT, Chris S <seebelow_at_nowhere.com> wrote:
>Not a silly question; I tried both, as that can be problematic. I
>can ping the host by both name and ip. I used ip in tnsnames.ora just
>to eliminate that. Also not mentioned is the fact that I've verified
>that I'm using the correct tnsnames.ora file, since I have multiple
>ora homes on the problem machine.
>
>Time to be more specific - I just tested dialup on private network
>(our RAS dialin), dialup on public network (using vpn), and DSL
>(public network, using vpn). Both VPN flavors fail, while dialin over
>RAS (private network, no vpn involved) works. So VPN is clearly the
>common factor in the problem, not DSL (as I first thought).
>
>I turned on trace and log in my sqlnet.ora file. Here's the log of a
>failed sqlplus connect: (took out ip and userid for security):
>
>================================================
>Fatal NI connect error 12535, connecting to:
> (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host's
>ip>)(PORT=1521))(CONNECT_DATA=(SID=TRAX)(CID=(PROGRAM=C:\oracle\ora81\bin\SQLPLUSW.EXE)(HOST=CHRIS-C610)(USER=<my
>userid>))))
>
> VERSION INFORMATION:
> TNS for 32-bit Windows: Version 8.1.7.0.0 - Production
> Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows:
>Version 8.1.7.0.0 - Production
> Time: 03-NOV-2002 11:11:37
> Tracing to file: c:\temp\oratrace\sqlnet.trc
> Tns error struct:
> nr err code: 0
> ns main err code: 12535
> TNS-12535: TNS:operation timed out
> ns secondary err code: 12560
> nt main err code: 505
> TNS-00505: Operation timed out
> nt secondary err code: 60
> nt OS err code: 0
>===================================================
>and here's the trace file:
>===================================================
>nncpldf_load_addrfile: failure, error stack follows
>nncpldf_load_addrfile: NL-00405: cannot open parameter file
>
>nncpldf_load_addrfile: NOTE: FILE CONTAINS ERRORS, SOME NAMES MAY BE
>MISSING
>
>ntt2err: soc 284 error - operation=1, ntresnt[0]=505, ntresnt[1]=60,
>ntresnt[2]=0
>nserror: nsres: id=0, op=65, ns=12535, ns2=12560; nt[0]=505, nt[1]=60,
>nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
>nsopen: unable to open transport
>nioqper: error from nscall
>nioqper: nr err code: 0
>nioqper: ns main err code: 12535
>nioqper: ns (2) err code: 12560
>nioqper: nt main err code: 505
>nioqper: nt (2) err code: 60
>nioqper: nt OS err code: 0
>niqme: reporting NS-12535 error as ORA-12535
>niotns: Couldn't connect, returning 12535
>===============================================
>Not sure why I'm getting the 'cannot open parameter file ...' errors,
>but that occurs in the trace when I get a good connect also, I think.
>
>The relevant error, I think, is the 'nsopen: unable to open
>transport'. My guess is that, while I can ping, and access all my
>corporate network resources on the target network (i.e., vpn is
>working fine), somehow sqlnet is not getting a connection.
>
>This could indicate (maybe) that our firewall/vpn host is blocking
>this traffic, but ... as mentioned, I can fire up an adjacent laptop
>here at home and repeat the test with success - so this is definitely
>a client side problem. The two laptops are very similarly configured;
>both have local forms and local databases; both use same version of
>vpn; use same uerid/pwd to get into vpn (and into private network).
>
>I did a 'rebind adapters' command in the vpn software; no change.
>
>Any thoughts? Thanks, Chris
>
>
>
>On Tue, 3 Dec 2002 21:42:44 -0000, "David Sharples"
><david.sharples3_at_ntlworld.com> wrote:
>
>>silly question, but are you using hostnames in your tnsnames.ora file or ip
>>addresses
>>if you are using hostnames do you have dns set up?
>>
>>
>>"Chris S" <seebelow_at_nowhere.com> wrote in message
>>news:p9f8sugpcdvh1qh65lhf4m9f2dg577vr2p_at_4ax.com...
>>> I install and config all our oracle databases at work, and have become
>>> pretty adept at solving sqlnet connectivity issues. I also personally
>>> have 3 computers at home which connect to our work network, via vpn,
>>> and which run SQLNET connections successfully (oracle forms, sql*plus,
>>> etc).
>>>
>>> I've recently built a new laptop 'image' for use by all our sales
>>> guys, which has loaded on it Oracle 8.1.7 db, and 6i forms. Works
>>> great. But ... if I take this particular laptop home, and configure
>>> it to work over my DSL modem, it won't work. Neither SQL*Plus,
>>> TNSPING, nor ODBC will work. I can 'ping' the remote server, and I
>>> can run various other 'stuff' like outlook/exchange connections, etc -
>>> so the network is clearly visible.
>>>
>>> I even took an older laptop (different image but similar config with
>>> 8.1.7, forms, etc) and tested it, and it works. I then loaded 'oracle
>>> client' on a home machine, one that had never seen Oracle software
>>> before, and got it to talk sqlnet to my work servers via DSL no
>>> problem (sql plus, odbc, etc).
>>>
>>> This new, problematic image can connect to any office-network database
>>> when directly connected to the network via ethernet. And it can
>>> connect to the local database at all times.
>>>
>>> I've read posts where users can get 'simple' queries to work but not
>>> complex ones, and it was due to MTU settings; but in my case,
>>> 'nothing' is working. There's no firewall on this laptop. We use
>>> Checkpoint VPN (but that's common to all environments, working and
>>> non-working). My DSL is from PacBell, using Enternet 300 software
>>> v1.5.
>>>
>>> Any ideas where to start looking? Thanks, Chris
>>> ===========
>>> Reply to cschofie at domain dot com
>>> Change domain to attbi - Thanks
>>
>
>===========
>Reply to cschofie at domain dot com
>Change domain to attbi - Thanks
 |
 |