Home » RDBMS Server » Networking and Gateways » Windows 2000 connectivity problem
Windows 2000 connectivity problem [message #66170] Tue, 08 January 2002 01:28 Go to next message
Mahendra Navarange
Messages: 5
Registered: January 2002
Junior Member
I have installed Oracle 8i personal edition on my desktop which is Win2K client. How can my colleague who is using another Win2K client connect to my database via Net8?

I am getting unable to connect 12203 message on my colleague's machine even though my listener.log shows 0 return code for the connection.
Re: Windows 2000 connectivity problem [message #66175 is a reply to message #66170] Tue, 08 January 2002 02:39 Go to previous message
Farid
Messages: 5
Registered: January 2002
Junior Member
When troubleshooting ORA/TNS-12203 errors on Windows 95, 98, or NT, it will be
helpful to have a copy of the TNSNAMES.ORA file located in front of you. This
file is normally located in the ORACLE_HOMENETWORKADMIN directory (or NET80ADMIN).
If the file is not there, go to section 6.

2.1. Go to, or log on to, the server where Oracle resides.

2.2. Open a DOS window and type 'ipconfig' at the operating system prompt.
Your DOS window will show information similar to the following:

+-----------------------------------------------------------------------+
| Command Prompt [[_]][[-]][[X]]
+-----------------------------------------------------------------------+
| Microsoft(R) Windows NT(TM)
| (C) Copyright 1985-1996 Microsoft Corp.
|
| C:>ipconfig
|
| Windows NT IP Configuration
|
| Ethernet adapter El90x1:
|
| IP Address. . . . . . . . . : 138.2.121.221
| Subnet Mask . . . . . . . . : 255.255.255.0
| Default Gateway . . . . . . : 138.2.121.1
|
| C:> _
+-----------------------------------------------------------------------+

You will be referring to this IP address throughout the paper so you
may want to jot it down. Continue to section 2.4.

You will be referring to this IP address throughout the paper so you
may want to jot it down. Continue to section 2.4.

2.4. Open your listener.ora file in a text editor. If you do not have a
listener.ora, skip to section 6. Replace the HOST name with the IP address
in your TCP address block.

If you are already using the IP address, and it matches the IP address you
found earlier, go to section 2.5. If not, make the change and save the
listener.ora file. Continue to section 2.5.

2.5. At the command prompt, restart the listener by typing 'lsnrctl stop' (if
you are on Windows NT running Oracle 8, type 'lsnrctl80 stop') followed by
the command 'lsnrctl start' (if you are on Windows NT running Oracle 8,
type 'lsnrctl80 start').

2.6. On the client, go to the command prompt and type 'ping <IP address>'
using the IP address of server you found earlier in this section. For
example:

> ping 138.2.158.34

You should get some response back stating that the ping was successful or
that the server is alive. If this is the case, continue to section 2.7. If
you get any errors, or messages stating that there was a timeout problem, or
that the host was unreachable, or the IP address was bad, contact your
network administrator and find out why you can't ping the server. This is
cause of your TNS-12203 error.

2.7. You have verified that you can physically contact the server and that the
listener is running. The next thing to do is verify the correctness of the
TNSNAMES.ORA file. Locate the TNSNAMES.ORA file. This file is usually in the
ORACLE_HOMEnetworkadmin (or net80admin) directory. Open the file in a text
editor. Make sure the HOST parameter for the alias you are trying to connect
with is set to the IP address of the server - rather than using the host name.
You also need to make sure the value of the PORT parameter in the tnsnames.ora
file matches the value of the PORT parameter in the listener.ora file. After
you've verified these two items, try a connection. If the connection still
fails, continue to section 2.8.

2.8. A lot of times, a person will unknowingly use an application designed for
SQLNet 2.3, but only have Net8 installed or vice versa. For example, if you
are executing PLUS33W.EXE, then make sure the TNSNAMES.ORA file is in the
networkadmin directory. If you are using PLUS80W.EXE, make sure the
tnsnames.ora file is in the net80admin directory. If you have a 3rd party
application and are not sure which directory the configuration files go in,
just place the tnsnames.ora file and sqlnet.ora file in both the networkadmin
and net80admin directories.

2.9. We need to verify the file size of your WSOCK32.DLL. This DLL is the 32
bit Winsock driver for the operating system. Use the table below to determine
if you are using the correct file:

Filename OS Location Size
------------+-------+---------------------------+--------------------
wsock32.dll Win98 windowssystem 40k (40,960 bytes)
wsock32.dll Win95 windows 65k (66,560 bytes)
wsock32.dll WinNT winntsystem32 20k (20,240 bytes)

If your wsock32.dll does not match the appropriate file as listed above,
then reinstall your operating system's TCP/IP stack. If your DLLs are okay,
continue to section 2.10.

2.10 There may be a syntactical problem with the configuration files.
Please check the syntax as described in section 6.
Previous Topic: TNS Ping Over VPN
Next Topic: Re: Please give a sample file for tnsnames.ora and listener.ora
Goto Forum:
  


Current Time: Sun Mar 03 22:29:48 CST 2024