RE: Oracle Client not passing Windows Domain portion of connect info ?
Date: Thu, 18 Feb 2010 12:39:03 -0600
Message-ID: <C5533BD628A9524496D63801704AE56D379D1A1D86_at_SPOBMEXC14.adprod.directory>
Thanks, but no it's not locked. See my reply previous to this one. This is to a remote db.
If I type the same command in twice, the second attempt works, the first attempt fails.
SQL> connect /_at_db_name
ERROR:
ORA-01017: invalid username/password; logon denied
SQL> connect /_at_db_name
Connected.
SQL>
DBA_AUDIT_SESSION shows:
OS_USERNAME = taylorcd
RETURNCODE = 1017
OS_USERNAME = DOMAIN\taylorcd
RETURNCODE = 0
Very strange.
Chris Taylor
Sr. Oracle DBA
Ingram Barge Company
Nashville, TN 37205
Office: 615-517-3355
Cell: 615-354-4799
Email: chris.taylor_at_ingrambarge.com
CONFIDENTIALITY NOTICE: This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and delete the contents of this message without disclosing the contents to anyone, using them for any purpose, or storing or copying the information on any medium.
-----Original Message-----
From: Peter Nedeljkovich [mailto:pnedeljkovich_at_georgianc.on.ca]
Sent: Thursday, February 18, 2010 11:35 AM
To: 'wbfergus_at_gmail.com'; Taylor, Chris David
Cc: 'oracle-l-freelists'
Subject: RE: Oracle Client not passing Windows Domain portion of connect info ?
Your culprit could be in sqlnet.ora. Look for a string called NAMES.DEFAULT_DOMAIN Also, with all the testing that you've done, is it possible that your account status is locked?
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Bill Ferguson
Sent: Thursday, February 18, 2010 12:29 PM
To: ChrisDavid.Taylor_at_ingrambarge.com
Cc: oracle-l-freelists
Subject: Re: Oracle Client not passing Windows Domain portion of connect info ?
I had some major problems with my Oracle servers under AD, but that was primarily due to a very poorly designed Active Directory. During the install, Oracle would automatically grab the AD domain and append that to the SID, and in our case, AD was the only thing that knew about the AD domin name, so the normal IP/DNS things would never resolve the SID.doamin to the actual machine. Removing the servers from AD before the install solved my problems (and I haven't re-added them to AD since).
My own PC's (and those of my users) though don't seem to having any problems connecting to the servers, so it doesn't appear that the clients add any AD credentials to the connect string.
--
- Bill Ferguson
--
http://www.freelists.org/webpage/oracle-l
--
This message was scanned by the Georgian College ESVA and is believed to be clean.
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Feb 18 2010 - 12:39:03 CST