Looks like applying SQL Server SP3 did the trick. It was installed previously, but the SQL Server was *re*installed, and the SP was not applied.
MDAC *before* the SP was installed showed 2.8 - which is most current at the time. Perhaps something else in the SP fixed a connection error?! Oh well, Thanks again Dave. -- Alex >>Our IIS 6/CF server is on a "10 dot" network, and mapped to >>an external IP via our firewall appliance. >> >>When trying to set up a DSN to our MS SQL Server, I keep >>getting a "connection refused" error message. I am using the >>server name (UNC >>name) and the correct username/password. The SQL server is >>across the 'net on another network. The CF/Web server's >>public IP has open access through the firewall into the >>network where the SQL server is kept. >> >>What's strange, is that I created a system datasource in the >>ODBC control panel applet, and I connect to the SQL server >>just fine. I then used the CF Admin to create an ODBC socket >>DSN to connect to the local DSN on the web server. >> >>Any ideas on why I can connect to the remote SQL server via a >>Microsoft local system DSN, but not directly to the SQL box >>from CF Admin using the stock SQL server drivers? >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201597 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
