Microsoft sql 2000 odbc driver

Either enable SQL authentication and add a login specifically for this connection or add login credentials for X on Y through computer management. If I didn't guess the solution right off let's do this methodically. There's a lot of connectivity software layers here.

Let's start at the bottom. Can you ping X from Y? Can you ping Y from X? Can you connect with DN? Can you connect with IP? To answere your first question, no I do not connect through windows authentication but SQL authentication. I can ping X from Y no problem.

I can ping Y from X no problem. I can connect with DN from my PC no problem. I can connect with IP from my PC no problem. This server though is win SP 4.

MS SQL server version 8. What error is the ODBC driver throwing? I'm asking all this because I'm trying to coordinate your software versions with the right MDAC version s.

No major feature enhancements have been made since MDAC 2. This Provider has been deprecated. Also, it uses Oracle 7 emulation to provide limited support for Oracle 8 databases. Oracle no longer supports applications that use OCI version 7 calls. These technologies are deprecated. If you're using Oracle data sources, you should migrate to Oracle-supplied driver and provider. Microsoft has released the.

All RDS server components will be removed from the operating system after Windows 7. MDAC 2. JRO won't be available on the bit Windows operating system. JRO isn't supported in the Microsoft Access file format. For more information, see Knowledge base article ODBC Cursor Library has been deprecated; your application can use server-side cursor implementations as a replacement.

MDAC 1. These versions of MDAC are no longer supported. Service packs of MDAC 2. This version of MDAC no longer is supported.

You can install this version on the Windows XP platform only through the operating system or its services packs. WDAC is included as part of the operating system and isn't available separately for redistribution.

Serviceability for WDAC is subject to the life cycle of the operating system. Obsolete technologies are technologies that have not been enhanced or updated in several product releases and that will be excluded from future product releases.

Don't use these technologies when you write new applications. When you modify existing applications that are written by using these technologies, consider migrating those applications to ADO. NET or another current technology.

Did you know that you can edit SQL content yourself? If you do so, not only do you help improve our documentation, but you also get credited as a contributor to the page. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Note If you are accessing this page from a non-English language version, and want to see the most up-to-date content, please select Read in English at the top of this page.

Submit and view feedback for This product This page. View all page feedback. In this article.