I have an public Azure VM instance running Windows 10 . I changed the DNS to Google DNS and I loose RDP connection. Why?
While changing the DNS servers, please follow below steps:
Changing the DNS servers to Google DNS servers can be done via Azure portal or PowerShell.
From Azure Portal, Navigate to your VNET, click on DNS servers and enter the DNS server IPs.
After doing changes to DNS, Virtual Machine need a reboot. Make sure to reboot the VM.
This change can be done on the NIC of Virtual Machine not on the OS level.
Resize the Virtual Machine, if reboot doesn't restore connectivity. This should return the RDP and the DNS entry you defined.
Try redeploying the Virtual machine.
Otherwise, Try resetting the Remote Desktop configuration.
Try Checking the Network Security Group rules.
Try Resetting the NIC for the VM.
To know more in detail, please refer below links:
Lost connectivity to Azure VM after changing DNS to automatically obtain DNS - Microsoft Q&A.
Cannot connect with RDP to a Windows VM in Azure - Virtual Machines | Microsoft Docs
VM getting disconnected after changing preferred DNS IP (microsoft.com).
Change VM DNS Servers - Microsoft Q&A.
Related
i get this error for installation script that worked perfect on EC2 vm but now seems that i can't reach the site , should i add some inbound rule or something to enable apache2 server ? the error in the chrome is
This site can’t be reached *.*.*.*.com’s server IP address could not be found.
Try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
Network Security Group
Azure VMs do not have any ports open firewall ports by default unless you open them when you provision your VM. When you created your Azure VM in the Azure Portal, you likely created a Network Security Group for the VM. If you didn't specify any ports to open during the VM's creation, you'll need to open up the VM's firewall.
To Open Ports
To open up the ports on the firewall, head out to the Azure Portal (where you set up the VM). Find the VM in the list of resources. It should take you to a page for your VM where the name, status, location, size, IP address, etc will be displayed. On the left side, you'll have a vertical menu > Select Networking. From there, you'll be able to see currently active firewall rules for the VM. Since you're likely missing HTTP (80) and HTTPS, select add inbound port rule. From the dropdown for service, select HTTP and assign a name/priority. Perform the same options, except this time selecting HTTPS (443). Press save and test. You should be able to access Apache running on the VM.
Additional Troubleshooting
The script you used may have inadvertently set up the VM's iptables. You can view Linux's firewall with sudo iptables -L to verify that no firewall rules have been enabled. Since Azure handles the firewall, you shouldn't need any iptables rules, but they could always be added for additional security.
This answer assumes that you do not have Azure's Load Balancing servers installed in front of the VM.
I have ServiceControl setup on it's own VM and configured to use SQL Transport which I have pointed at the SQL database that's currently being used for NServiceBus. I've opened up port 33333 in the firewall on both the VM and in Azure NSG. I also installed OpenSSH and opened those ports.
On my local machine, I've opened a tunnel to the ServiceControl VM and forwarded port 33333. The tunnel opens without issue. I am running ServiceInsight on my local machine and have it connect to localhost:33333 which is forwarded to the remote VM. It connects without any reported error.
That's it. There is no data displayed in ServiceInsight. No endpoints in the endpoint explorer or anything.
Did I miss something? I'm not sure how to troubleshoot this.
In Azure, I created a virtual network and then associated an Ubuntu Server virtual machine, created with Azure Resource Manager Deployment method, with the network. I then updated the associated Network Security Group and added an inbound security rule for port 80 (Source:Any, Destination:Any, Service:TCP/80). After installing Apache on the VM, I tried to access the server from my browser, but have run into a wall. I can SSH into the VM just fine, but web is a no-go, and I cannot figure out why. Any help would be appreciated.
It sometimes happen to me too because I forgot to RESTART the VM, yes just restart it. At least this works for me. and also dont forget to add outbound rule too
It worked for me with this inbound rule.
Note that when a VM is created from the portal (in ARM model), it gets automatically associated to a virtual network (vnet), a specific subnet within the vnet and a network security group.
When creating the inbound security rule, make sure to:
identify the correct network security group associated to the VM
use a priority number lower than 65500
set the source port range as *
You also need open port 80 on the VM to allow web access.
I dont think that creating your Network Security Group opens the desired port on the VM automatically.
By default in Azure Resource Manager (ARM), all ports are open; there is no need to make Network Security Groups (NSGs) to open ports, only to close them. Here is an example of an ARM template that deploys an ubuntu VM with apache:
https://github.com/Azure/azure-quickstart-templates/tree/master/apache2-on-ubuntu-vm
Alternatively, if you want an auto-scaling LAP stack using VM Scale Sets (in public preview), you can find the ARM template for that here:
https://github.com/Azure/azure-quickstart-templates/tree/master/201-vmss-lapstack-autoscale
Hope this helps! :)
I am trying to access the url localhost:8088/openbravo from the network. The local IP of the system is 192.168.1.101/openbravo. But when i try it from other system in the network, it doesn't work. Is there any setting that i need to do.
i added the ip address in the hosts file of the local system. But it didn't work too.
System is windows 2008 server 64bit.
--
Thanks
With it being Server 2008, have you disabled the Windows Firewall to see if it will work. It may be blocking incoming connections from that port from the other local networked machine. After the test, then you can reenable and add a firewall exception for the tomcat port of 8088.
http://technet.microsoft.com/en-us/library/cc766337(v=ws.10).aspx
try with this 192.168.1.101:8088/openbravo.
Yesterday I created an Azure Virtual Machine using the simple Win2008r2 + SQL2008r2 image.
I have deployed a website to the VM via an RDP session.
I am able to browse the website locally (via RDP) using
"http://localhost"
I understand that I need to add an Azure endpoint for port 80 to enable me to browse to the site from an external machine.
I have configured the Windows Firewall on the Azure VM to allow traffic on Port 80 inbound and outbound.
Could anyone please advise what I've missed or what I can do to troubleshoot?
---Update-----
I have learned a little more this morning. The website that I'm trying to host on the VM is an installation of Interwoven Teamsite v7.3.x. When I looked in IIS I could see that the "Default Web Site" was stopped. Another website called "TeamSiteSitePubPreview" had been created but was only bound to port 81.
So, what was presenting the website I could see when I browsed to
http://localhost locally?
I ran netstat -ano and this showed me that PID 1604 what listening on port 80. I then ran Process Explorer which told me that PID 1604 was allocated to "Appache HTTP Server".
I know nothing about About Appache, can anyone tell me if there's some Apache config that will be preventing connections from outside of the local server?
For reference, I just tested this sequence and it gives you a website accessible over the Internet:
Create a new Windows Azure virtual machine with the Windows Server 2008 R2 SP1 image.
Add an endpoint on public port 80, private port 80.
While the endpoint is being created, start setting the server up.
Remote Desktop in.
Add the Web Server (IIS) role with default settings.
Test the connection. You should get a HTTP 200 OK status.
If you want to troubleshoot your server, start checking for errors in the event log. Check also the website bindings in IIS (Port 80, IP Address *).
Also consider the connection issue might be on the client (your) side. For instance, DNS caching. Try connecting from another machine with direct Internet connection (such as another cloud server) or from a service such as isup.me.
Additionally, if all you want is to host websites in IIS, the Web Sites service has a more streamlined experience.
You will need to create an endpoint on port 80 thru Windows Azure Management portal as well. This endpoint opens a port in the Windows Azure Load-balancer.
Navigate to your VM within the portal and create a new Endpoint under the Endpoints screen of VM configuration within Azure management portal.