I tried deploying OpenStack (Xena version) using Kolla-ansible tool, All-in-one mode. My cloud server (Ubuntu-2004-server) has 2 NICs (I attached 2 public IPs to these NICs). After successful deployment, I create network: provider network and vxlan network. Then I create a VM, but my VM can't connect to the Internet. What can I do in my problem, about my server or configure anything in the network (OpenStack).
Many thanks!
Everything is fine but the VM created in OpenStack cannot connect to the Internet.
Related
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.
I try to integrate a web app to a VNET. this is a brand new subscription.
According to : Integrate your app with an Azure virtual network
In the first step I wanted to check if the web app could reach out to VNET. The second step I want to connect the web app to SQL database through a Service Endpoint
I created a VNET with 2 subnets:
Jumpbox-subnet
integration-subnet
integration-subnet setting
There is service endpoint pointing to the integration-subnet. Also I integrated the app to the VNet, It's delegated the integration subnet.
I tried to connect to VM from App using tcpping 172.16.1.0 (jumpbox VM private address) from app console, but it failed.
I also app cannot connect to the sql database.
What are the missing pieces here, is a DNS server required to make this work?
Update (Resolved):
The question above was the key, It needs away to resolve the name with some sort DNS server.
tcpping default port is 80 and nothing was listening to that port in that box.
You could use the tool tcpping to test for TCP connectivity to a host and port combination.
The syntax is: tcpping.exe hostname [optional: port]
For example, run tcpping 172.19.1.10:3389
See troubleshooting app service networking for more details.
For more references, Here is an ARM example to deploy an app service with VNet integration and enable service endpoint Microsoft.Storage.
I have a classic network setup in Azure, complete with VMs, vnets and site to site VPN.
I need to introduce a RM VM to integrate with this network. Are there any special considerations I need to make to ensure that the RM VM can integrate with the classic network?
Thanks
The only thing you have to do is to create a Vnet-Vnet connection between the ASM (Azure service manager or classic) and the ARM network. You can do this by creating a gateway and connect them . The only consideration is to use non overlapping subnets. The same consideration you have when creating a vpn between on-premise and Azure.
Has anybody tried out virtual machines in the UK area of bluemix?
I am able to start a vm but get an timeout when i try so connect to the vm via ssh.
I used the std Debian image that can be choosen on setup time and injected an ssh key for connecting. The security group I used was allow_all.
When trying to ping or to connect via ssh directly or the openstack cli the connection times out.
regards
Johannes
There was a bug in the setup of the vm, so I actually had no chance to access it.
I am trying to use Azure Files and I am getting the following System error 53. Any ideas?
There are two possible reasons for getting this error if you are trying to mount your Azure file shares from outside of Azure Datacenter via SMB 3.0.
Your client OS needs support SMB 3.0, for example use Windows 8, Windows 10, Windows Server 2012.
The port 445 (TCP Outbound) needs to be opened by your ISP or firewall. The SMB protocol is dependent on this port if you mount from outside of Azure Datacenter, and I do notice some ISP blocked this port (e.g. Comcast).
You can refer to the links below to do a self-check on the port by yourself.
http://poshcode.org/2514
http://powershell.com/cs/media/p/4063.aspx
There is another explanation for this error.
If you try to connect to that network share from your machine as opposed to connecting from an Azure VM (or role).
The network share is only visible to Azure VMs. There may even be one more restriction - the share and the VM must live in the same Azure region.
Sources:
My experience, hitting this problem on my laptop (and seeing it work, using the same cmd, in an Azure VM).
Also, this: https://blogs.msdn.microsoft.com/windowsazurestorage/2014/05/12/introducing-microsoft-azure-file-service/ :
Once your share is created, it can be accessed via the SMB or REST
protocol from any Azure node (VM/Worker/Web role) hosted in the same
region as the storage account hosting the share.
This is the only thing that worked for me:
Change this registry key to a value of 3
HKLM\SYSTEM\CurrentControlSet\Control\Lsa > LmCompatibilityLevel
For more information, see the LmCompatibilityLevel topic on TechNet.
Got this solution from this MS docs