> 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.
Oh yeah, I forgot to mention that. That fixes a lot of problems, such as
using named instances.
> MDAC *before* the SP was installed showed 2.8
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 wel
Thanks for the reply Dave. You always have great suggestions.
At this point, I cannot even connect to a local SQL Server, on the same
"10 dot" network as the CF box. I verified that both TCP/IP and Named
Pipes are enabled in the Server Network Utility, and that both Windows
and SQL Server login
> 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. Th
;
>-Original Message-
>From: Alex Sherwood [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, April 05, 2005 10:30 AM
>To: CF-Talk
>Subject: Help with NAT and DSN setups in CF Admin
>
>Greetings.
>
>Our IIS 6/CF server is on a "10 dot" network, and mapped to an externa
Make sure you have the correct port open.
-Original Message-
From: Alex Sherwood [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 10:30 AM
To: CF-Talk
Subject: Help with NAT and DSN setups in CF Admin
Greetings.
Our IIS 6/CF server is on a "10 dot" network, and ma
Greetings.
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
7 matches
Mail list logo
