you should also enter a value for SID and GLOBAL_NAME, otherwise you can't connect. If in doubt
login to METALINK and search for tnsnames.
Hi, sorry I have not read everythink but the problem do you have is , if I understood everythink correct:
1) server machine has OS unix
2) client machin has OS Windows
NEVER apply configuration files from UNIX to WINDOWs and forward as they have absolutly different coding, you can't see all characters in your file but they are here, for example you cant see chr(0), chr(10), chr(13).
So solution is: remove tnsnames.ora from your client and create new one. Using Windows tools or manualy, I had the same problem .
[Edited by kgb on 09-26-2001 at 12:35 PM]
Originally posted by gooftrap
i have set up my listener at client side and tnsnames.ora at client side. I am using oracle 8.1.5. Clients are installed on the client machines. When i try to connect on the server with the same instructions in tnsnames.ora as in client side, it connects. But from the client's machine, it refuses...
To better find the point of failure, could you check the following:
Check what was your
If you have the DOMAIN name set as world then you have to use the NAME.WORLD as a service name in your tnsnames.ora file (eg: SID.WORLD)
Sample tnsnames.ora file on the client machine:
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))
(SID = your_sid)
Then try connecting as from the command prompt/dos prompt:
Looking forward to hear from you...
Life is a journey, not a destination!
(1)if it is nt/w2k server there can be control characters which can cause problem and they are not seen. Look for them and
(2)the peranthesis are to be verified.. i doubt you have one right peranthesis extra.
(3)if you have multiple listener services stop all and start the correct one.
havent read whole thread but check you hosts file in windows
Click Here to Expand Forum to Full Width