Ross;
You saved my day. Named Pipes was not enabled. I got it working now.
Thanks a million.
Bill
"Ross Culver" wrote in message
> Bill,
>
> Did you set SQL to accept both TCP/IP and Named Pipes remote connections
> in SQL Surface Area Configuration?
>
> Ross
>
>
> "Bill Nguyen" wrote in message
>
>> I'm getting the following error trying to use 32-bit client on a Win2003
>> 64-bit server to connect to an SQLserver 2005 on a 32-bit remote Win 2003
>> server.
>> IF I use the 64-bit ODBC manager (SQL Native client or ODBC DSN), I got
>> connected without any problem. The problem is the application (Great
>> Plains Dynamics 10) only recognized 32-bit ODBC client.
>>
>> Any help is greatly appreciated.
>>
>> Bill
>>
>> -----------------------
>>
>>
>>
>> ---------------------------
>> Microsoft SQL Server Login
>> ---------------------------
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 233
>> [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a
>> connection to SQL Server [233].
>> Connection failed:
>> SQLState: 'HYT00'
>> SQL Server Error: 0
>> [Microsoft][SQL Native Client]Login timeout expired
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 233
>> [Microsoft][SQL Native Client]An error has occurred while establishing a
>> connection to the server. When connecting to SQL Server 2005, this
>> failure may be caused by the fact that under the default settings SQL
>> Server does not allow remote connections.
>>
>> ---------------------------
>> OK
>> ---------------------------
>>
>>
>
> >> Stay informed about: [Microsoft][SQL Native Client]Named Pipes Provider: Could ..