I would edit the entry via Control Panel->ODBC to make sure that the initial
connection is made via TCP/IP and not Named Pipes, then verify the DSN via
CF Administrator.
Sometimes when the machines are not part of the same NT domain, they cannot
see each other until after the DSN is forced to an IP connection over port
1433.

Also make sure that the SQL server is listening on port 1433

Claudio.


-----Original Message-----
From: Phil Palmer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 13, 2000 5:08 PM
To: CF-Server
Subject: odbc drivers


Dear All

I just installed CF 4.5.1 Professional on a clean NT Server for a client.
They are
using IIS and everthing is pretty standard (whatever standard is !)

I created an ODBC Data Source to another machine to SQL Server using the
CF Administrator.  When I test the connection through CF it fails.  If I go
and
test it through Control Panel / ODBC the test is successful.  Now the client
is seriously doubting CF and I must admit - I am a bit worried.

Any ideas on what could be causing this.  I am getting them to install the
ODBC
driver that comes with SQLServer7 as they have a later version but I will
be concerned if that fixes it.  Surely if it works through Control Panel it
should
work through CF - arent they doing the same thing?

Any help appreciated.

Regards

Phil Palmer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with 
'unsubscribe' in the body or visit the list page at www.houseoffusion.com

Reply via email to