Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I can connect with "Encrypt connection" if I'm connecting locally, I can connect without "Encrypt connection" remotely, but I can't connect remotely with "Encrypt connection" checked.

The error that I get from ssms: "A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - No such host is known.) (Microsoft SQL Server, Error: 11001)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=11001&LinkId=20476"

My host just sent me a certificate, I added the certificate both to the Trusted root CA and Trusted publishes.

Any help will be appreciated, thank you.

share|improve this question
    
11001 = WSAHOST_NOT_FOUND which matches your error message. Are you sure you've got the hostname correct? The full host name? Not sure why that would vary between encrypted and not, though (unless it's failing trying to find a server for CRL lookup or something). –  Rup Apr 7 '11 at 15:49
    
Hi Rup, the only possible thought I have is that I explicitly provide the port (SERVER\INSTANCENAME,1433) and not relying on the Browser, not sure if it is relevant, It is the only "exception" i can think of. For the server I use the IP Address –  Esh Apr 7 '11 at 15:56

1 Answer 1

In case it will save someone else some pain, using the server name instead of the IP Address solved the problem.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.