>> Carl, >> >> The only thing I've gotten to work so far is SQL Auth (using the >> user/pass above which definitely isn't a Windows domain user). The only >> reason I tried SQL Auth was to see if I could get anything working - >> like you say, it's a step backward and I would prefer not to go that way. >> > > OK, thats good to know. I kinda thought so. > >> Your osql.exe lines all work provided I've got Mixed Mode turned on >> (with the user/pass above-makes sense). Turning off Mixed Mode and >> trying to use my domain user/pass results in the same failure messages >> as below. Trying it with no user/pass results in a request to use a >> user/pass. > > If this doesn't work: > > c:\>osql -S 192.168.51.26 -E > > That means your windows login does not have rights to use the SQL server, and > so > you will never get win auth to work in python. > >> None of the suggested pymssql lines work though. >> For example for user="\\:" it returns: Login failed for user '\:'. >> For user="\\", it returns Login failed for user '\'. I've also tried >> every conceivable option of "Domain\User", "Domain\\User", >> "[EMAIL PROTECTED]", etc. > > No surprise, given the osql -E didn't work. Once you get it working, then > you > will get to try these again :) > >
Both of osql lines did work. c:\>osql -S 192.168.51.26 -E returns the 1> prompt like you described. c:\>osql -S 192.168.51.26 -U plant_user -P emseal01 also returns the 1> prompt. I assume that fact that the first works means that Win Auth works, and that the second works means that SQL Auth works. There seems to be some kind of inconsistency here, but I can't seem to put my finger on it. Bill. _______________________________________________ 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]
