Skip to Content.
Sympa Menu

freetds - [freetds] Domain Login, MSSQL : James

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Chris Hettinger" <chettinger AT encompas.com>
  • To: "FreeTDS Development Group (E-mail)" <freetds AT lists.ibiblio.org>
  • Subject: [freetds] Domain Login, MSSQL : James
  • Date: Wed, 6 Aug 2003 09:13:59 -0500

James,

Thanks very much for the continued help. I do have some good news, I believe
I made a successful connection this morning.

I had worked yesterday on compiling the 08/05 snapshot, which initially I had
that issue with the "Check System Clock." I used:
$ touch -m * on the <DIR> which synced the modified dates, and then my
configure worked just fine. Guessing it was possibly a time zone difference
or something... Anyway.

This morning I was again trying to make a test connection with tsql, but
encountered the same "Not trusted..." message. I then took a look at the man
page on tsql and it struck me that the line option -S <servername> was really
the name I put for the server in the freetds.conf file ex: [ENCPPP] ... I
then edited the freetds.conf file to reflect:

[ENCPPP]
host = 192.168.1.245 <-- I originally this as:
encppp.encompass.enc, and was using -S encppp.encompass.enc
port = 1433
tds version = 7.0
try domain login = yes
try server login = no
nt domain = ENCOMPASS

Now when I made the test connection: $ tsql -S ENCPPP -U chettinger, I
connected successfully after entering my password.

.... NEXT... compiling php to include support for freetds... Anyone know of
good documentation on that? :)

-Chris Hettinger, Web Specialist
-IFMC/ENCOMPASS
-www.enompas.com
-(515) 223.2947




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.'





Archive powered by MHonArc 2.6.24.

Top of Page