Product Documentation


Previous Topic

Next Topic

Configuring 32-bit ODBC Drivers on 64-bit Windows Versions

With 64-bit versions of Windows, the previous 32-bit ODBC Driver Manager is now located in a different location, and is not used by default. To configure a 32-bit driver on these systems, use the following steps:

  • Execute: %WINDIR%\syswow64\odbcad32.exe
  • Create a DSN using the 32-bit version of the Administrator

See Also

Previous Topic

Next Topic

Connect Microsoft 64-bit SQL Server 2005 to FairCom DB SQL

  • First configure your 32-bit driver as described in this article:

    Configuring 32-bit ODBC Drivers on 64-bit Windows Versions

  • Using the SQL Server Import and Export Wizard, you will get a pop-up screen that is asking for a Data Source.
  • You will not see the 32-bit DSN in the drop down menu. Select ".Net Framework Data Provider for ODBC". On most systems it's probably the top one in the list, however, you need to scroll up to see it as the list usually displays in the middle.
  • Enter further connection information on the resulting dialog screens.
  • Under NamedConnection String there is a field for "dsn". In this field put the name of the DSN created in Step 1.
  • Click on Next and follow the rest of the instructions to copy the desired data.

Previous Topic

Next Topic

Slow Windows Network Traffic

Communication with a server on a local network can be substantially slower than expected when newer Windows computers (Windows Vista and later) attempt to access older Windows computers. Although the communication works eventually, you may experience slow response times.

The problem may be due changes in the was the system handles Link Local Multicast Name Resolution (LLMNR) protocol. LLMNR is based on the Domain Name System (DNS) protocol. It provides name resolution for addresses on the same local network without the need for a DNS server.

The multicast used by LLMNR is not supported by all systems. If your network contains a mix of old and new systems, some systems may be attempting to use a protocol that others do not support. After a timeout, the computer will use other means to perform the operation, so the process works...slowly.


  1. Disable LLMNR on the newer computers.
  2. Avoid a DNS lookup be doing either of the following:
    • Specify an IP address in the connection string instead of a domain name.
    • Edit the hosts file on the newer machine to include the name and IP address of the older machine.
  3. And, of course, if you can replace the older computers you will eliminate this problem and possibly improve performance in other areas at the same time.

To turn off LLMNR on a server:

  1. From the Windows Start menu, type GPEdit.msc in the search box and press Enter. The Local Group Policy Editor will appear:

    LLMNR in the Local Group Policy Editor

  2. Using the Console Tree on the left, navigate to:
    Local Computer Policy > Computer Configuration > Administrative Templates > Network > DNS Client
  3. In the DNS Client folder, double-click Turn off Multicast Name Resolution and set State to Enabled.