RE: Domain Auth to MS SQL - PHP/FreeTDS 0.61

I will retract what I said... I suspect it is more on my end than it not 
working. I have made a connection with tsql so I would believe, yes domain 
authentication was working.

The second part of what you wrote:
"Try to define TDSCONFIG to a file name and exec PHP code. Does PHP read your 
freetds.conf ?"

This is my current question, is PHP seeing freetds correctly. I have tried a 
TDSDUMPCONFIG in the past but I haven't see a file created. I found little on 
it in the Docs. Can you please tell how to do this.

-ch

-----Original Message-----
From: Frediano Ziglio [mailto:freddyz77@xxxxxx]
Sent: Tuesday, August 19, 2003 2:39 PM
To: FreeTDS Development Group
Subject: RE: [freetds] Domain Auth to MS SQL - PHP/FreeTDS 0.61


Il mar, 2003-08-19 alle 20:30, Chris Hettinger ha scritto:
> Thanks I did switch the $db_host to ENCPPP, know by freetds.
> 
> I did get rid of the errros I mentioned but only by switching the SQL 
> server's auth type to "SQL and Window" in the security tab.
> 
> As far as I can tell, though Domain Support has been added to freetds as of 
> 0.60, it doesn't seem to be working. But really, what do I know ... just what 
> I can gather, and it may be something I missed.
> 
> I really appreciate the help.
> 
> -ch

Mmm.. you are the first man who said so... I tried domain account with
NT4 domain, NT4 workgroup, and ActiveDirectory (no kerberos) always
successfully (I discovered recently that NTLM2 do not work but this is
another problem). 
If tsql work this mean that FreeTDS can use domain account. If PHP do
not work this mean that something in the script, in PHP code or in
configuration is wrong... Try to define TDSCONFIG to a file name and
exec PHP code. Does PHP read your freetds.conf ? 

freddy77


_______________________________________________
FreeTDS mailing list
FreeTDS@xxxxxxxxxxxxxxxxx
http://lists.ibiblio.org/mailman/listinfo/freetds


CONFIDENTIALITY NOTICE:  This communication, including any attachment, may 
contain confidential information and is intended only for the individual or 
entity to whom it is addressed.  Any review, dissemination, or copying of this 
communication by anyone other than the intended recipient is strictly 
prohibited.  If you are not the intended recipient, please contact the sender 
by reply email, delete and destroy all copies of the original message.'