Hey all I am in need of some help setting up TFS on my Azure windows server 2016 VM.
I think i have all my firewall rules set up but i'm not that sure if i do or not. I followed this site as an example.
However, I am not able to reach it outside of my server using my domain name like so:
http://mydomain.me:8080/tfs
I have also tested out my connecting outside of my server for my SQL 2017 and it seems i cannot connect to that either.
What am i missing in order for me to connect to both the SQL and TFS from outside the server?
Firmware rules are not enough to access TFS set up in Azure. The basic topology looks something like the illustration below:
In a virtual network, it establishes a new domain with two domain controllers and deploys a TFS server, a database, and a TFS agent. To access the virtual network, the pattern includes a jump box; another strategy would be to add a VPN gateway, but for simplicity we are going with the jump box.
You can check the blog below for more information:
https://blogs.msdn.microsoft.com/mihansen/2017/11/15/private-tfs-deployment-in-azure/
Or you could consider migrating to VSTS as #Daniel's mentioned.
Related
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 am developing a report in PowerBI Desktop based on data hosted in an Azure SQL Server VM.
When publishing a report, I get the below error:
Publishing succeeded, but the published report cannot connect to the
data source because we were unable to find a gateway. Please install
and configure an enterprise gateway
I believe this is because the enterprise gateway is installed locally on my azure VM, however I'm accessing it from my desktop by going over the web and through the firewall. Therefore I believe the issue is that my pc acceses the machine at
mymachine.cloudapp.net
Whilst the enterprise gateway knows the machine as
netbios-name
Is there any way that I can upload a desktop report to powerBI web using this configuration? The other solution would be to get the machine and sql server to identify itself as "mymachine.cloudapp.net" so that I can use this as the name to connect to through the enterprise gateway, but I'm not sure how to do that (adding the alias to SQL Server isn't enough).
It's a bit hacky, but I've got a work around.
Open the server and edit your hosts file and add the following line:
127.0.0.1 mymachine.cloudapp.net
Make sure that mymachine.cloudapp.net has been configured in SQL Server as an alias.
In PowerBI, add a new enterprise gateway data source, this time, use mymachine.cloudapp.net to connect rather than netbios-name. You will need to use SQL Authentication to connect.
Obviously connecting PowerBI to an Azure VM in this way is not ideal, as it could potentially be unencrypted, but this works around the issue of different host names between PowerBI Desktop and Web.
I have come to learn that we can push the source data file from our local machine to Azure VM to load the database of VM's SQL Server. I have activated my Azure trial account and have setup SQL Server in a VM. Now, I am really clueless how to load data from my local machine.
How it can be achieved by using SSIS flow? Trying to search over the internet, please share any references.
Thanks
You need to be able to connect from your local machine to the Azure VM. One way of doing this is give your VM a public IP and configure the right firewall rules. An VPN or other tunneling can also work. Your solution also depends on where your SSIS server lives.
I did it by following the steps mentioned in Connect to a SQL Server Virtual Machine on Azure (Resource Manager)
Currently our windows desktop applications run against a SQL Server instance that resides on our network. I'd like to remove the local instance and seamlessly assess the data from a remote SQL Server instance such as Azure. I could write a middle tier, such as WCF, but I'd rather not. It would be easiest just gain direct access to the SQL server. Can this be done?
Thanks.
Yes. - http://msdn.microsoft.com/en-us/library/windowsazure/ee336282.aspx
You'll need to ensure that the Azure SQL Database firewall rules are set up to allow traffic from your IP.
If you are running full SQL Server on a Windows Azure Virtual Machine you can open the port to the SQL Server. Be aware that you'd likely want to ACL the endpoints on a VM to restrict access to your IPs.
Remote SQL Server and Azure could be very different things.
First difference that you will found is the Connection String form. Azure SQL connection strings looks like:
Server=tcp:xxxxxxxx.database.windows.net;Database=xxxxxxxx;User ID=xxxxxxx#xxxxxxxxx;Password=xxxxxxxxxx;Trusted_Connection=False;Encrypt=True;
I'm newbie for Amazon EC2.
I'm given an assignment where I've to connect VS 2008 to Sql Express 2005.
VS and Sql Express are running on separate Amazon machine.
(I mean, I've to do 2 separate Remote Desktop Connection to access both).
I've no clue how to connect to the Sql Express.
I've been trying different options found in search on google, stackoverflow etc...
But no luck.
Any help is appreciated.
Assuming that you have a connection string (to server ec-xxxxxxx.xxx.amazon.com), your problem could be that the .Net instance (let's call it NET) and the SQL Server instance (SQL) don't have the rights to see each other.
Create two instances with the different security groups
On both groups, you'll like want to open RDP (you probably have that already as I can read)
On the SQL instance security group create an inbound rule for port 1433 and open it only for the security group of WEB. Otherwise, the whole world can access your SQL Server Express database. Like this, only the WEB instance can access it. You need to paste the security group id of WEB into the inbound rule for SQL to do that.
Good luck.