Any one have a idea about setup visual svn on microsft azure and access it through different macine?
I just add Azure VM and Inbound and Outbound port set to 8443 and same port i used for visualsvn.but i cannot access it through different macine.
I cannot use Classic VM on My Azure.
My Previous azure had classic vm but new portal i doesn't have classic vm it redirect to normal vm as below image.
According to your description, you need open port 8443 on Azure NSG(Inbound rule). By default, it only creates port 3389, you need add a new rule.
Related
Set up is:
Windows 10 Pro 64 bit
All Hyper-V and Container features turned on
Full Sql Server, standard port 1433
Visual Studio 2017
Docker Community Edition Version 18.03.1-ce-win65 (17513)
Stock Windows 10 Firewall rules and security Polices
No additional anti-virus or security
I built a POC .net core 2.1 service in VS2017, added docker support. For test purposes I am trying to connect to the Sql Server from the service. I understand it runs in its own private network. When I run the service as a standalone outside of docker, it connects to Sql fine, so all that is working. Inside of the container it can't connect. I'm specifying the IP of vEthernet (nat).
If I turn off Windows Firewall, then it can connect. When I turn on firewall logging, I can see the packets are being dropped.
In network and sharing, my PC appears in the Network / Private Network group and the vEthernet (default switch) and vEthernet (nat) appear in the Unidentified / Private network group. Access type is No network access.
My PC is connected to the internet via a wi-fi router, so I don't want to open up a big fat security hole, but I'd like the container to be able to connect.
I can't specify the IP of the container since that is dynamic.
How should I set things up to let the containers connect to the Sql?
Maybe, Hyper-V is not connected to the local sever. Open Hyper-V Manager and connect to server...
I have a VMSS which is not connected to a load balancer running windows 2016 server edition operating system. How can I RDP into this setup? Is port 3389 open by default?
If you use Azure image to create VMSS, you can create a windows VM work as a jumpbox in that same Vnet.
If you use image which upload from your local, please make sure you have enable RDP first, then you can use another VM to RDP it via internal IP address.
If you image does not enable RDP, please re-prepare your image and enable RDP, then upload to Azure to create a new VMSS.
Another way to do this is to go to your vnet, search for your vm scale set and you should be able to see the IP.
I'm running Windows Server 2012 w/ vmWare Workstation. I've built a GitLab VM on Centos 7 that's totally setup and accessible on my local network. It's configured using Bridged Mode so it has it's own IP from the DHCP Server.
I use No-IP to connect to my Network externally which has been working great for several years now. I have port-forwarding setup within my router to forward traffic for the GitLab webUI to the GitLab VM, but it's not accessible externally. I even tried setting up the port forwarding to direct the traffic to the Windows Server and then setup internal port forwarding w/ netsh on the Windows Server to forward the traffic to the GitLab VM, making sure I opened the port on the Windows Firewall (even tried disabling it), but I still can't get to the GitLab VM externally. AFAIK running a VM w/ a Bridged adapter should essentially be like it is just another physical machine on the network.
Now, I am running IIS on the Windows Server, but when I specify a specific port using my public No-IP Domain, the router should detect the traffic on that port and forward it according to the rules that I have setup, correct? IIS shouldn't be interfering with any traffic on other ports with the external Domain.
I'm totally stumped on this on and searching around the web really hasn't helped much.
So it turns out that I did everything 100% correctly with setting up port forwarding right to the IP of the VM, but my workplace blocks just about every port except for 80 and 443. Tested connectivity from an AWS box and everything is accessible exactly as designed.
Now I just feel like an idiot, but hey, I figured it out.
this is the first time I am trying to host at Iaas level using microsoft azure. I have created a VM, microsoft server 2012. But I cannot access the VM using the DNS name.
Based on the content of the comments, I see three things that could be wrong
1) Apache is not listening on the external IP of the VM
2) Firewall is not configured to allow for access
3) Since you mentioned DNS, is that the *.cloudapp.net hostname or a custom DNS? If it's the latter, maybe it isn't distributed yet or misconfigured?
Which of these did you check already? Then we can guide you through the remaining ones.
When create a VM on Windows Azure, and set up an IIS server I can access by dns provided by Azure.
There is a way, for set my domain to an asp.net application?
Like, mysite.com on iis of my VM.
Use your own domain/DNS management and setup a CNAME alias for the Azure generated DNS entry.