I am on VPN and trying to connect Azure SQL server from SQL Management Studio
I get this popup, but IP on it keep changes.
Because of this, I see a lot of IP's getting added in Firewall settings of SQL Server in Azure portal
What is the solution here?
Is it expected behaviour?
I have the same environment that connect to the Azure SQL database via VPN connection. The client IP may changes every some days, I need to manually add the new IP to the firewall again manually. Just for now. I think that's caused by the VPN servers.Some suggestions are that keep your VPN address fixed. There isn't a good solution for now.
HTH.
Related
I work remotely and travel a lot for work. When I am at home, I have no problem accessing my instance of SQL Server hosted by my company on AWS. The SQL Server instance is currently configured to only accept connections from ONE IP address and as it changes I lose my connection. Whenever I travel I cannot access SQL Server and when I come home, sometimes my IP address changes and I also cannot access from home.
I am sure this is an issue others have had. Can anyone suggest a solution? Whether it is from the DB side or client side?
Thank you,
dave
I’m having a very specific issue with Azure and I couldn’t find any solution on the web.
So, we are little by little migrating our client’s infrastructure to Azure and we are starting with our Workers (webjobs).
These webjobs need to consume data present on a AWS SQL Server instance.
We already have checked that the App Service Plan’s Outbound IPs are whitelisted and that the SQL server is listening on TCP port 1433.
An evidence of that is the fact that we are able to communicate with the SQL Server instance through the Azure Debug Console:
But when we run the WebApp, the worker cannot find and connect to the same DB:
Does anyone have a clue of how I can solve this issue? It would be very appreciated!
Well, as you demonstrated by the first image, the SQL Server instance is configured correctly.
The worker Outbound IP address is definetely the same as the App Service Plan's machine.
Based on that, can you then please check if the Connection string you are setting have 'tcp:' before the IP Address?
Sometimes you need to force it, otherwise IIS can choose other ways to connect to your SQL server (like UDP for instance).
I am working with azure based application. In which, I need to get connected with azure sql server. I had already configured firewall setting on azure portal for my IP address. But still even when I tried to get connected to azure sql server, it never gets connect at the very first time. When I try to connect it more than two times then it gets connected.
This problem is also with application level connectivity, when i try to run the application on visual studio same happens.
I had researched a lot regarding this specific problem but didn't get any solution yet. I always get network related error Error Code : 53.
Any help will be appreciated.
This looks a lot like a local network issue.
When your application is deployed onto an Azure resource (App service, VM, etc.) does it get a similar connection error?
Every Azure SQL Server has a firewall, you need to create a client IP rule but also to allow access to the Azure service.
I actually have a remote database acess via TCP/IP
I've searched the web, but I only get results regarding remote SQL by IP.
So, is there a way to make my IP acessible from a sub-domain (e.q. bd.domain.com) ?
Thanks
Agreed, this is a DNS resolution issue, you need to make sure that your client can resolve the server.bd.domain.com name to the correct IP. You need an A record in the bd domain's DNS in order for this to work properly.
we are using the window Azure first time and we have deplyed our SQL server databases on the window Sql Azure server. using the connection string from the SQL Azure server, we are able to successfully connect with the Web aapplication while at the same time when we are trying to connect with the Desktop application it always throw "General Network Error"?
In order to resolve the issue we have check the firewall and all seems to be fine.
Any help highly appreciated.
Thanks,
Rupesh
May I ask where your web application is running? It seems it is running in Windows Azure and connected to SQL Azure without any problem. Isnt it? I am always interested to know what tool you are using to connect? SSMS or SQLCMD or something else?
IF you want to connect SQL Azure from on premise (from your desktop) you really need to add your IP address in SQL Azure firewall exception list first. Even when you checked it that could be the main reason. Here is the guideline connecting SQL Azure DB and please follow first 3 points when you are trying to connect from your desktop. Those 3 points are:
Add your IP address in SQL Azure Exception List and add 1433 Port exception in your own firewall exception list
Verify you have setup firewall exception correctly
Always use login1#servername when connecting to SQL Azure DB nane XXXX.database.windows.net
After that try using SqlCmd as described here.