Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 1 year ago.
Improve this question
i m trying to create new linked service in azure data factory, where i have created sql db already. attach the error message in the link
enter image description here
You are trying to connect to a SQL Database that is behind a firewall. If you allow the IP address (in your case it is 20.42.2.58 as per the screenshot) your linked service should work. Navigate to Firewall and Virtual Networks blade of your SQL Server and add IP address, the start IP and the end IP should be the same.
A second option would be to use "Allow Azure services and resources to access this server" - set this option to Yes.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 months ago.
Improve this question
I am trying to setup a private AKS cluster which I want to manage from a user laptop using kubectl. I have tried to create a simple setup with one vNET, Azure VPN gateway with OpenVPN configuration, where the VPN Gateway is attached to one subnet of the vNET and AKS is configured via Azure CNI to live in another subnet of the same vNET. I have expected that this is all I would need to get manage the cluster as long as I am connected to the VPN (I understood that all subnets on a vNET are routed by default). But when I try to use kubectl I get Unable to connect to the server: dial tcp: lookup : no such host My network knowledge does not go too deep unfortunately, but should this just work? I mean it all lives within the same vNET. Thank you.
My setup is very similar and I ran into the same situation. This was a DNS issue for me.
If you have a private DNS zone with your private AKS cluster (should be in the resource group which was created for the AKS private cluster), go find the DNS record and IP address for the API server. Put that IP address into your hosts file (/etc/hosts if on linux or WSL) with the fully qualified domain name, then try your kubectl commands again.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Simple question: supposing I have several backend microservices, which are only ever accessed by application software, is it best practice to:
point the application software directly to an IP address? or
Assign a subdomain to the services?
My assumptions are that (1) avoids DNS lookup latency whereas (2) makes it easier to update the system if the IP ever changes. Is there anything else that affects this?
Assigning a subdomain or directly accessing with IP address is not a scalable approach.
I would suggest, point your client application software to an API gateway, which would be the single entry point to these microservices and there should be a service discovery mechanism so that the API gateway can reach to these individual Microservices.
please refer to the following sample diagram.
Client application requesting for data from a specific service and it reaches API gateway
API gateway requests discovery server for the latest reachable address for that specific service
Discovery Service is giving back the latest reachable address
API gateway using that address which it got from the Discovery server to reach the specific service for the resource requested by the client.
All the microservices should be registered with the Discovery server when it spins up.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Can you confirm if the connection between a Azure Web App and Azure SQL DB needs to cross the internet if both the Azure Web App and Azure SQL DB would be hosted in the same Azure Region ( such as West US)? I understand that each region is covered by multiple data centers.
Is there some internal network connectivity within the data centers?
I know that we need to use Encrypt=True and TrustServerCertificate=False in the connection string to keep the data encrypted in transit.
Is there any documentation available on the network security between data centers within a region?
The traffic between different data centers within a region is done over a private Microsoft network. In fact, even if both services were hosted in completely different regions, the connection does not go over the public Internet:
Source: https://azure.microsoft.com/en-us/blog/how-microsoft-builds-its-fast-and-reliable-global-network/
Azure traffic between our datacenters stays on our network and
does not flow over the Internet. This includes all traffic between
Microsoft services anywhere in the world. For example, within Azure,
traffic between virtual machines, storage, and SQL communication
traverses only the Microsoft network, regardless of the source and
destination region. Intra-region VNet-to-VNet traffic, as well as
cross-region VNet-to-VNet traffic, stays on the Microsoft network.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've created a Windows VM from the Gallery as a standalone VM
I then created a second VM from the same image and in the Virtual Machive Mode of the creation wizard I select to 'Connect to Existing Virtual Machine' and select my first machine.
All is well.
However - I can't figure out how to RDP to that second machine.
As the two are load balanced they both share the same DNS entry and public IP. I can see two ports assigned for RDP, one for each machine, but I can't connect to the second one.
What am I missing?
You should be able to connect to any instance without any problems (I just tested and it works). This is how it should go:
Create your first VM, Name=vm001, Dns=vm001.cloudapp.net. This VM should contain 1 endpoint by default, port 3389 (both public & private port) for RDP.
Create your second VM and choose to connect to an existing virtual machine. Name=vm002, but you won't be able to choose the Dns. By connecting to an existing VM (vm001 in this case), you'll reuse the same Dns. In this case it would be vm001.cloudapp.net. Check the endpoints for this new virtual machine. You'll see an endpoint for RemoteDesktop with private port 3389, but the public port will be something different (like 62295 for example). Note that this enpdoint is not load balanced.
The fact that each VM has its own public port for RDP and that the endpoint is not load balanced should be enough to connect to the instances without any issues. This means:
vm001.cloudapp.net:3389 > vm001:3389
vm001.cloudapp.net:62295 > vm002:3398
If you still have issues connecting, go to the portal, select the VM and choose the connect button. Also check if your firewall allows you to connecton this random port (maybe your firewall allows connections to 3389 but not to 62295 for example).
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
When we spin a new ubuntu block in azure, we get a public IP address for that block. I am working off a trial account. Does anyone know how many public IP addresses can Azure provide? Is there a limit. I believe there is a limit on AWS and then they want us to use some VPN like solution. Does this limit exist on Azure or not ?
I don't think there is a limit. You get a public IP address for every active deployment in a Cloud Service. Creating a Virtual Machine creates a Cloud Service behind the scene and puts an active deployment on it. That public IP address is guaranteed to not be changed while your deployment is there (not deleted). Whether that public IP address is shared with other deployment - I don't know (but my guess is - yes). By default there is a limit for the number of cloud services one can create. This limit depends on the type of subscription you have. So this is the kind of limitation there is in Azure.