This was a problem from the second version of the ODBC/DBLib drivers on. It
seems that the OS or other applications would install one part of the
driver/LAN interface pair but not the other. I expect that's what has
happened in your case. I have an idea though. Setup a VPC with Windows X (a
version that works) and access it from there. I would also plan to upgrade
the server ASAP... ;)
> Thanks William
>
[quoted text clipped - 53 lines]
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> ____________________________________________________________________________________________

Signature
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
FoxHill - 19 Jul 2008 04:57 GMT
Hi William
For my situation, upgrading is not an option for me.
Anyway, I found out something and don't know if it can help:
1. On those 2003 servers unable to connect to sql 6.5, I checked the
network library version of TCP/IP is
"SSNETLIB.dll, 8.0.2039, 3/5/2005"
2. On those 2003 server able to connect to sql 6.5, the version info is:
"SSNETLIB.dll, 8.0.311, 5/8/2003"
I'm just wondering if there're some ways to restore the old driver.
Any idea?
> This was a problem from the second version of the ODBC/DBLib drivers on. It
> seems that the OS or other applications would install one part of the
[quoted text clipped - 70 lines]
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> ____________________________________________________________________________________________