I have been trying to connect to Azure SQL Database with SQL Server Managerment Studio 2014 without succeeding:

TITLE: Connect to Server
------------------------------ Cannot connect to agvxmnll6p.database.windows.net. ------------------------------
ADDITIONAL INFORMATION: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476 ------------------------------ A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ------------------------------
BUTTONS: OK
------------------------------

Then I followed this guide to troubleshoot:

http://social.technet.microsoft.com/wiki/contents/articles/1719.aspx#section2

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved. C:\Users\tomty>ping agvxmnll6p.database.windows.net Pinging eastasia1-a.control.database.windows.net [191.234.2.139] with 32 bytes of data:
Request timed out. Ping statistics for 191.234.2.139:
    Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
^C
C:\Users\tomty>telnet 191.234.2.139 1433
Connecting To 191.234.2.139...Could not open connection to the host, on port 1433: Connect failed C:\Users\tomty>tracert 191.234.2.139 Tracing route to 191.234.2.139 over a maximum of 30 hops   1    <1 ms    <1 ms    <1 ms  buffalo.setup [192.168.11.1]
  2     7 ms     1 ms     1 ms  014199148001.ctinets.com [14.199.148.1]
  3     1 ms     1 ms     1 ms  061093141081.ctinets.com [61.93.141.81]
  4    12 ms     9 ms    10 ms  014199252237.ctinets.com [14.199.252.237]
  5     1 ms     1 ms     1 ms  014136128130.ctinets.com [14.136.128.130]
  6     1 ms     1 ms     1 ms  198.200.130.193
  7     1 ms     1 ms     1 ms  ae0-0.hkb-96cbe-1a.ntwk.msn.net [191.234.80.230]
  8     2 ms     1 ms     1 ms  104.44.224.6
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out. Trace complete.

I already added my IP to the azure firewall rule, disabled Windows Firewall, Added port forwarding for all protocol and enabled DMZ on my router, using Named Pipes / TCP/IP protocol with / without Encrypted connection checked, increased timeout to 30s. What else can I do? Does the tracert result mean that Microsoft blocked my ISP or something?

• Edited by tom.ty89 18 hours 53 minutes ago

Hi Tom,

Ignore the traceroute, thats normal for some hops to timeout. 

Few points.

Make sure you are connecting to the right port, this is the public mssql port which is visible in the azure portal, hence the server name could be something like tcp:agvxmnll6p.database.windows.net,87000    where 87000 is the port.  TCP: just forces TCP connection however you should'nt need this. 

Double check your IP is the one you've entered in the azure firewall rule, use some like whatsmyip.com for this. 

Failing that, maybe spin up a SQL Web virtual and try connecting from there given this will have the management tools installed and rule out your router/firewall, etc.