In my development shop, we deploy code on virtual servers that sit on a remote network.
We access the machines on that network by first opening an SSH connection to
For Authentication type Azure Active Directory - Universal with MFA
(Mutli-Factor Authentication), in addition to specifying the port correctly (127.0.0.1,3398
), I also had to point the host to localhost
.
On Windows, I had to edit my hosts
file to include the server host:
127.0.0.1 server.example.com
Then, in SSMS, I could connect to server.example.com,3398
, which would perform the MFA correctly.
I could have performed this redirection at a higher DNS level as well.
The issue is probably that SSMS is trying to access the SQL Server Browser Service, which is UDP port 1434. Take a look at http://technet.microsoft.com/en-us/library/cc646023.aspx for an overview of the additional ports you may need to forward to get this to work.
Instead of connecting to localhost:3398 Use 127.0.0.1,3398
I'm pretty sure I figured out the answer to this, actually.
On the remote network (which we don't control), for security purposes, it appears that the database servers are set up to ignore database requests coming from the gateway machine. So I guess there's just no good solution short of convincing them to give us full VPN access. Thanks everyone for your help.