On Tuesday 19 June 2007 13:29, Bill Witherspoon wrote: > > Yes please test Win Auth. Before we make changes to any of the code we > > need to insure Win Auth works. The code assoicated with 'port' in > > dbMsSQL.py (Dabo's side of the connection) is not used and I think > > everyone forgot to remove it. > > > > I don't have psmssql.py setup for windows. Can anyone explain what is > > replacing the Linux FreeTDS libs? What ever is replacing FreeTDS should > > contain the port information settings. > > Just finished testing and I cannot get Win Auth to work. I've tried all > the variations that I can think of: > > user='billw', user='Emcorp\billw', user='[EMAIL PROTECTED]', user='\:', > user='\\', etc. > > (Emcorp being our domain) along with appropriate passwords (and no > password, etc.) > > I tried these variations with the server set to Mixed and to Win Auth > only. The good news is that removing the port makes incorrect logins > fail in two seconds, where I was waiting for a time out before. ;-) > > I believe Carl suggested that using Win Auth, simply "knocking" on the > door should prompt Sql to check if the "knocker" has the appropriate > credentials. I agree with this, but suspect that pymssql is not set up > to accommodate this. If you supply no user it defaults to "sa" for > example. (I did override this behavior as well, no dice). It would seem > to me that if the capability existed it would be in the pymssql > connection parameters as well, ie: > > def connect(dsn = None, user = "sa", password = "", host = ".", database > = "master"): > > would be: > > def connect(dsn = None, user = "sa", password = "", host = ".", database > = "master", authtype = "SQL"): > > or something like that. > > Would it be worth trying to get in touch with the pymssql author? I > would do it if asked, but I suspect Ed or another Dabo developer might > get better traction. > > Thanks, > Bill.
Our earlier efforts to contact the author were successful but he asked us to fix the issues as he (the author) did not have time. OK so let go a little deeper. Turn on trace on the MS SQL engine and report what is being sent to the engine. I believe just turning on tracing the connections is all we need - but please make that determination. I have not received a reply on what replaces FreeTDS from anyone. So I guess I'll have to setup a windows environment. In your efforts I don't see where the database is being set in the connection string. Also the lashes may need to be escaped. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
