Azure SQL Database Error

Home / Azure / Azure SQL Database Error

I was on SQL Cruise where I was scheduled to present a session on Azure SQL Database. I recorded all my demonstrations before we went to sea, but, I planned to attempt to try live demo’s. Yeah, yeah. Well, anyway, I got a unique error when I attempted to connect:

Forced connection closes from remote host

That’s a partial message from the whole error. I don’t have a good screen capture. I wasn’t able to find anything on it through Ging searches, but this week I was at Microsoft for a training course on Azure. I asked the room. The rough answer is (paraphrasing):

The IP address I was attempting to connect from is not is not on the approved list

Interesting. I didn’t realize there were blackout zones. The really interesting thing was, this only occurred when I attempted to connect through SQL Server Management Studio. I was able to connect through the Azure Portal. One more wrinkle in the interesting challenges offered by Azure and the Data Platform.

4 Comments

  • This tells me that the security layer screening IP addresses that are connecting is at the database server level and not higher than that. That would explain why SSMS from the boat couldn’t connect but the portal could, because SSMS was at sea but the portal was not. Interesting though. I wonder where the boat’s IP address says it is.

    • I think your description is an excellent way to put it. The portal is not on the boat, but SSMS is. I don’t have any other evidence to put forward. If I could get someone to fund another cruise, I’d be happy to gather metrics.

  • Rob

    If you connect through SSMS 2016 they’ve added a great feature that adds your current IP to the server whitelist – assuming you have access to it with your azure login of course.

  • Huh. I haven’t seen that and I’ve been using the new SSMS for a while. Cool. I’ll have to keep an eye out for it.

    Unfortunately, in this case, it wasn’t the firewall white list that was the issue. That would have been easy to address.

OK, fine, but what do you think?