Bill Witherspoon wrote: > Carl Karsten wrote: >> Bill Witherspoon wrote: >>> Carl Karsten wrote: >>>> Ed Leafe wrote: >>>>> On Jun 13, 2007, at 2:16 PM, Carl Karsten wrote: >>>>> >>>>>> -> We're using >> Windows >> Authentication currently, >>>>>> >>>>>> I think that is the 'problem.' >>>>> Why? All that means is that SqlServer will authenticate the username/ >>>>> pw through Windows authentication. If the username/pw is legit, it >>>> When using win, you don't need to pass a user/pw, and I think you need to >>>> tell >>>> it which method to use. so if anything, passing a user/pw may be the way >>>> to >>>> tell it to use SQL auth. >>>> >>>>> should be fine. In fact, when I helped test pymssql for Dabo, I used >>>>> Windows authentication to my SQL Server. >>>> Was your server set to win-only or mixed? >>>> >>>> Carl K >>>> >>> Carl, >>> It's set to mixed. Let me try to remove the user/pass right now. >> If it is set to mixed, then I would try to use SQL, not win. >> >>> Well, that's weird - if you leave the user/pass parameters it looks like >>> it defaults to user = "sa". No go there either. >> yeah, I think there is a parameter you need to pass that explicitly tells it >> to >> use Win. >> >>> I also just tried user='billw' with no password, and password=''. No go. >> Is that a user/pw that the server knows about, or a win user? >> >> If you /join #dabo on irc.freenode.net I'll setup a server setup you can hit. >> >> Carl K >> >> > > Thanks Carl, > That's a generous offer - I'll take you up on it if it comes to that!
I am around tonight and tomorrow morning. some time in the afternoon I will be out. it isn't that generous - I just need to tweak my firewall.conf, restart, give you a user/pw, wait for the test and tweak it back when we are done. that explanation probably just doubled the amount of work :) > Since I last posted, I tried changing the SQLDB to Windows > Authentication only from Mixed. That didn't seem to help. flip it back, make sure you know what your SA pw is and test with that. > > The user/pass I'm using is my own domain user/pass (it's not a local > machine user/pass if that's what you mean). As for the server knowing > about it, I guess I assumed that it was querying our Domain Controller > behind the scenes? I don't think it is that 'simple', where the use of simple is being stretched... win auth is something like: log into your work station using a user/pw that gets authenticated somewhere, somehow, and then when you try to connect to the sql server it uses a token (or something your work station was given) to identify yourself to sql. I don't think sql ever sends your user/pw anywhere, cuz I don't think it ever gets it. > > I've resisted trying to set up SQL authentication because I didn't want > the headache of managing another set of users in addition to our AD SQL auto is simple: you setup a user/pw on the server, and you use that user/pw when you log in. I have never had to deal with enough users for it to be a headache. > setup. Maybe I'll try it though. At least use it as a test. Carl K _______________________________________________ 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]
