Brian Snipes wrote:
> On Wed, 2007-06-13 at 15:52 -0400, Bill Witherspoon wrote:
> 
>> Ed Leafe wrote:
>>> On Jun 13, 2007, at 12:57 PM, Bill Witherspoon wrote:
>>>
>>>> Despite many different iterations on hostname, etc. I'm still getting
>>>> the "Unable to make connection" error when I test the connection.
>>>>
>>>> I've connected to the DB using ODBC and that works. We're using  
>>>> Windows
>>>> Authentication currently, and the DB box is inside our LAN so there
>>>> shouldn't be any firewall-type issues.
>>>     Try this at a command prompt:
>>>
>>> C:\> python
>>>  >>> import pymssql
>>>  >>> conn = pymssql.connect(host="myHost", user="myName",  
>>> password="myPassword",
>>>          database="myDatabase")
>>>
>>>     Of course, substitute the correct values for the parameters. Do you  
>>> get a connection? If not, try this at the command prompt:
>>>
>>> C:\> telnet hostName 1433
>>>
>>>     Again, substitute the actual host name or IP address for 'hostName'.  
>>> Are you able to connect to the server over that port (which is the  
>>> default for MSSQL)?
>>>
>> My apologies for top-posting my reply. Don't know what I was thinking.
>> Please see below:
>>
>> Tried both. The output of code is:
>>
>> con = _mssql.connect(dbhost, dbuser, dbpasswd)
>> error: SQL Server message 18456, severity 14, state 1, line 1:
>> Login failed for user 'billw'.
>> DB-Lib error message 10003, severity 2:
>> Login incorrect.
>>
>> I see a very similar error message in the SqlServer logs (which I log
>> into with the same user/pass that's failing above) noting that the
>> request is coming from my IP and that the login failed for user 'billw'.
>>
>> I can't seem to telnet as you describe, or at least there is no answer -
>> just a blank screen.
>>
>> It does seem that the request is getting there, just that it's being
>> rejected. I tried the Domain Admin user/pass as well, no dice.
>>
>> The server is setup to receive remote connections.
>>
>> Thanks for the help,
>> Bill.
>>
> 
> 
> Have you tried it in Domain/Username, Domain\\Username, or
> [EMAIL PROTECTED] format?  If it isn't a member of a Domain perhaps
> substituting the computername for Domain would work.
> 
> Brian
> 
> 

Brian,

Good thoughts - I did try "Emcorp\billw" and "Emcorp\\billw", but I
didn't try "Emcorp/billw" or "[EMAIL PROTECTED]". Unfortunately, these
don't work either. Emcorp is our domain and all our boxes are resident
in it.


I don't have much expertise with SQL Server, but I'm starting to suspect
that's where the problem lies.

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]

Reply via email to