locked
Connecting to Azure Virtual Machine with local SSMS RRS feed

  • Question

  • There is a lot of info out there about this and how to troubleshoot.  I am still not able to do this.  When I try to connect on port 1433 I get a "filtered" response (no connection).

    I have verified all the setup and had someone else also verify it.

    I have a Server 2012 VM that I installed SQL on myself (SQL Server 2012 Standard)

    By the way, I can RDP just fine, I can do a Web Publish just fine.  It is just being about to connect SSMS that I am having issues with.

    Confirmed according to several online resources including MS Azure docs.:

    1) Azure Endpoint is set up 1433

    2) Firewall on the VM has an inbound rule for 1433.  ** Note, I even tried to connect with the VM firewall turned off.

    3) SQL Server network configuration is set up correctly (listening on port 1433 is confirmed)

    4) SQL server is set to mix mode authentication

    5) I can connect locally on the VM with SSMS using a the same SQL account.

    6) SQL Server has "Allow remote connections to this server" turned on.

    I have tried to connect from 2 different local networks.  Both of these have access to multiple other VM's (not Azure) and connect fine.  It is not my local firewalls blocking this.  It is not the VM firewall (turned it off!), so my only guess is that it is the Azure Endpoint.

    I did find references to Azure blocking 1433, but that seems to have been reversed.  I did try a different public port and that did not help.

    Again, I have found several different help guides for this, every detail I have checked seems to be set up correctly.

    Any thoughts?

    Tuesday, February 24, 2015 5:39 PM

Answers

  • Update as promised.

    I just went ahead and created a new VM.  All is good!!!!

    Server 2012 (Datacenter)

    Downloaded and installed SQL Server 2012 Standard (Basic install only need the DB engine)

    Configured for mixed mode, etc.  (I did not need to change anything after the install was done)

    Opened endpoints and VM firewall ports

    Tested and worked as expected

    Then went ahead and installed IIS, Web Deploy and updates.

    All is working as expected.  Not sure what I messed up the first go around.

    If anyone comes across this and the docs don't help, just try to set up a new VM (either SQL or Server and install SQL).


    • Marked as answer by Susie Long Monday, March 9, 2015 3:07 AM
    Wednesday, February 25, 2015 3:10 AM

All replies

  • Based on your notes, I see that you have done pretty much everything that could be done.

    I assume that you have enabled endpoint 1433 (as public port) for the 1433 (private port). Did you try to connect to 1433 using a telnet client?

    I assume you do not have any ACL's configured for endpoint access.

    Tuesday, February 24, 2015 7:12 PM
  • Yes to the port.  Telnet to IP, 1433 gives me.

    ...Could not open connection to the host, on port 1433: Connect failed

    So, I guess I could just start over.  Will kill hours of work, but no other choice.  would like to re-use the same VM name though.  Afraid that if I delete it, the name will not be available

    Tuesday, February 24, 2015 7:59 PM
  • I can quickly check over Skype if you would like (its sad to see you loose so much hours of work).
    Tuesday, February 24, 2015 9:08 PM
  • So I went ahead and created a SQL Server VM.  Did the same things and all works great.  The offer to help is really great.  I am going to try to go though and check all the differences between the 2 VM's and see if I can see anything different.  May try to re-install SQL and see if that helps.  If all that fails, just rebuilding the VM will probably be the best thing for me.

    I do know that the process as documented out there is correct and will work for me, there is some sort of config somewhere that is messed up.

    Again, thank you so much for the offer to help.  Will post any updates to my issue.

    Tuesday, February 24, 2015 9:54 PM
  • Update as promised.

    I just went ahead and created a new VM.  All is good!!!!

    Server 2012 (Datacenter)

    Downloaded and installed SQL Server 2012 Standard (Basic install only need the DB engine)

    Configured for mixed mode, etc.  (I did not need to change anything after the install was done)

    Opened endpoints and VM firewall ports

    Tested and worked as expected

    Then went ahead and installed IIS, Web Deploy and updates.

    All is working as expected.  Not sure what I messed up the first go around.

    If anyone comes across this and the docs don't help, just try to set up a new VM (either SQL or Server and install SQL).


    • Marked as answer by Susie Long Monday, March 9, 2015 3:07 AM
    Wednesday, February 25, 2015 3:10 AM
  • Thanks. Not sure what the root cause was. Please mark the post as resolved.
    Wednesday, February 25, 2015 3:21 AM