Probably proxy server (or firewall). Typically proxy server because the ODBC driver is not proxy aware like your internet browser is. This is why others mentioned configure the proxy without explanation. The typical solution is to add an environmental variable that the ODBC driver can see. I would recommend testing it using the following process: At the command line (in Windows) enter setx http_proxy <proxy_ip>:<proxy_port> (example setx http_proxy 132.50.12.1:443) Restart your ODBC Program (ex, PowerBi) Retest your connection If it fails, add the https_proxy the same way. If it succeeds, add it the system permanently.  Ref# Configure the proxy server - Splunk Documentation # libcurl - programming tutorial # Set up proxy using http_proxy & https_proxy environment variable in Linux? | GoLinuxCloud # windows - Command line to remove an environment variable from the OS-level configuration - Stack Overflow   ... View more

I also need answer for this question, product team, please suggest ... View more

Another thing to look into is whether there's a proxy in the middle. Once we allowed SSLV3 to pass through the proxy server, it works as promised. ... View more

What do you mean by 'do telnet on port 8089'? Did you provision a telnet server on port 8089? ... View more

It's not made any log. But, I am trace the LOG with ODBC driver Trace log. I will email. Thank you. ... View more

@Andy: you said " For better performance and throughput, you may also using raw socket directly. That is also supported by the SDK. You attach a Stream object to an Index object or a Receiver object and then write data into stream directly. Refer to UnitTests.IndexTest.IndexEvents." Do you have example of posting using raw socket directly using C#? I cant find the mentioned test class. Im going to be indexing alot of data. And I'm trying to figure out the best method for doing this from my C# app in a threadsafe way. ... View more