What is your exact connection string? Do you have "Network=dbmssocn" as Sergey (sp?) suggested included in the string?

If not, then no matter what you use for a name (e.g. IP address), then the DSN-less connection will makes its attempt using the default protocol configured under Client Network Utility. By default, this is Named Pipes.

BTW, if you can't ping the target, it means its unavailable. Either it's completely down or there is a TCPIP problem on your end or its preventing you from getting to it.

>I did this very same setup however :
>
>Scenario #1
>1. I've setup SQL Server to listen on the default port 1433
>2. I can ping from the client
>3. ODBC does not connect using TCP/IP
>
>
>Scenario #2
>1. I've setup SQL Server to listen on the default port 1433
>2. I can ping from the client
>3. ODBC connects using TCP/IP
>4. I cannot make a connection when I use a DSN less connection. I've replaced the server name with the ip address of the SQL Server in the connection string i published in my earlier threads.
>
>
>
>In all the cases however where I cannot ping ODBC/My DSN less connection will not connect.