From: Ellen K. 

Yes, netware client running on the fat client which can't connect but also
on my desktop and "my" servers, which can.

I did find one error in the log on the target box, also observed that it is
running the original version of SQL Server.  Will apply the service pack
once I get access to the machine.  Did not look up the error message,
decided to try making an ODBC connection instead... since that worked, as
far as I'm concerned I'm done since this isn't my database, I only have to
connect Hyperion to it because I'm the Hyperion administrator.  I'm not
supposed to be a systems guy, and frankly resent getting stuck doing their
work when my own plate is already overflowing.

On Fri, 14 Oct 2005 18:07:13 -0400, "Geo" 
wrote in message :

>I don't know the answers to these questions but something should be getting
>logged on the sql server so you might check that. Also, do you have any
>netware client stuff running or anything like that on the machine you are
>trying to connect from?
>
>Geo.
>
>"Ellen K."  wrote in message
>news:qpmvk11ta2v4jpulq3dif0vpb1ihdhd32e{at}4ax.com...
>> I'm using the same SQL Server username and password that can connect
>> successfully from the other two boxes.   In this scenario, which user
>> (if any) needs to be recognized by the outlaw SQL Server box:  me, or
>> the user under which the SQL Server service is running on the box from
>> which I'm trying to connect?  (Assuming there is even a SS service on
>> the fat client, since it only has the SS client tools.)
>>
>> I noticed that the fat client has the .Net framework service running,
>> which neither of the boxes that aren't having problems connecting has.
>> Is there any chance this could be the problem?
>
>

--- BBBS/NT v4.01 Flag-5