No luck. 
 
It turns out that CF8 (The SQL Server native 3.6 driver) does not support ssl. 
 
We are just upgrading to CF9. 
 
Tests have confirmed encrypted communication with CF9 to the SQL Server 2008 
instance.
 
-Eddie
 
 
 

--- On Tue, 9/28/10, Ajas Mohammed <[email protected]> wrote:


From: Ajas Mohammed <[email protected]>
Subject: Re: [houcfug] SSL Hell
To: [email protected]
Date: Tuesday, September 28, 2010, 8:42 AM


Eddie,

Any luck on your SSL SQL Server stuff?

<Ajas Mohammed />
http://ajashadi.blogspot.com
We cannot become what we need to be, remaining what we are.
No matter what, find a way. Because thats what winners do.
You can't improve what you don't measure.
Quality is never an accident; it is always the result of high intention, 
sincere effort, intelligent direction and skillful execution; it represents the 
wise choice of many alternatives.



On Fri, Sep 24, 2010 at 10:51 AM, Ajas Mohammed <[email protected]> wrote:

Have you tested your client connection with Query Analyzer? I came across this 
http://support.microsoft.com/kb/316898



<Ajas Mohammed />
http://ajashadi.blogspot.com
We cannot become what we need to be, remaining what we are.
No matter what, find a way. Because thats what winners do.
You can't improve what you don't measure.
Quality is never an accident; it is always the result of high intention, 
sincere effort, intelligent direction and skillful execution; it represents the 
wise choice of many alternatives.






On Fri, Sep 24, 2010 at 10:14 AM, Eddie Pequeno <[email protected]> wrote:






Nope, unfortunately the problem still remains. 

Thanks for the info Charlie. I'll definitely keep 443 open when conducting the 
tests. 

The only other thing I can think of is the possible misconfiguration of the 
imported cert. 

I'll need to confirm that all the properties within my cert are exactly the 
same as the cert on the SQL Server box. Oh by the way, it's SQL Server 2008 
that I'm attempting to connect with. 

 
-Eddie Pequeno
 
 

 
 
 
 
 


--- On Thu, 9/23/10, charlie arehart <[email protected]> wrote:


From: charlie arehart <[email protected]>
Subject: RE: [houcfug] SSL Hell
To: [email protected]
Date: Thursday, September 23, 2010, 3:37 PM







Eddie, are you saying you did confirm that the port was not open? And/or that 
the problem is now solved? If not, here’s another resource that can help:

How do I open the firewall port for SQL Server
http://support.microsoft.com/kb/968872/en-us

Despite the title (which adds SQL Server 2008 as shown on the page), the 
“applies to” at the bottom says it applies to 2000 and 2005 as well. I don’t 
recall you saying which you have.

Notice that the article refers to port 443 also needing to be open. That may be 
for something else (like Reporting Services), and I do realize you’re naming 
1433, but in case somehow a handshake process does end up using that 443 port, 
you should see if opening it may help as well.

And of course, you need to do the test from the machine running CF (not your 
desktop, if different), for the results to be meaningful. 

Finally, you may also want to check the SQL Server configuration to ensure that 
it is indeed set to permit SSL communication into it. I don’t recall where that 
may be settable (if at all), whether in the Server Configuration Manager or via 
properties for the server in Management Studio.

Hope that helps.


/charlie arehart 
[email protected] 
Providing CF and CFBuilder troubleshooting services 
at http://www.carehart.org/consulting 
  



From: [email protected] [mailto:[email protected]] On Behalf Of 
Eddie Pequeno
Sent: Thursday, September 23, 2010 4:07 PM
To: [email protected]
Subject: Re: [houcfug] SSL Hell
  





Yes, I think I saw that in the jTDS site. 

 

Thanks for the suggestion though Ajas.

 

Usually I connect to SQL Server via the native driver with no problem it's the 
SSL factor that is throwing a wrench in the mix. 

 

I realize that not many people actually do this but I'm still surprised by how 
little info there is about it online. 

 

-Eddie
  
-- 
You received this message because you are subscribed to the "Houston ColdFusion 
Users' Group" discussion list.
To unsubscribe, send email to [email protected]
For more options, visit http://groups.google.com/group/houcfug?hl=en




-- 
You received this message because you are subscribed to the "Houston ColdFusion 
Users' Group" discussion list.
To unsubscribe, send email to [email protected]
For more options, visit http://groups.google.com/group/houcfug?hl=en


-- 
You received this message because you are subscribed to the "Houston ColdFusion 
Users' Group" discussion list.
To unsubscribe, send email to [email protected]
For more options, visit http://groups.google.com/group/houcfug?hl=en


      

-- 
You received this message because you are subscribed to the "Houston ColdFusion 
Users' Group" discussion list.
To unsubscribe, send email to [email protected]
For more options, visit http://groups.google.com/group/houcfug?hl=en

Reply via email to