I have deployed a NFS server on an Azure Ubuntu 14.04LTS VM using this tutorial.
The problem that I'm facing is this: While I am able to successfully mount the folder I want when the client is my laptop or another physical machine, I can't do the same with another VM posing as a client.
I have configured the required endpoints (ports 2049 both udp and tcp) and I have, followed the exact same steps. What I get is this:
azureuser#testNode2:~$ sudo mount public.Azure.IP.ofNode1:export/users /export
mount.nfs: Connection timed out
I have also tried to mount using internal IP addresses but the outcome is the same.
If anyone could tell me what causes this or help me with this issue I'd be grateful.
You also need to open TCP/UDP 111. If the two VMs are in Azure, you should make them part of the same cloud service, or connect them to a virtual network in which case given Ubuntu in Azure ships with no default software firewall you wouldn't need to open anything.
Related
I was able to connect to Azure VM through RDP earlier but now suddenly I'm unable to connect to VM through RDP.
I tried to connect through Powersell.
Even powershell script was able to connect earlier but not working now. Myself didn't changed anything in Azure VM.
I'm getting below errors.
But I'm able to connect to VM through Bastion.
WinRM is already enabled in Azure VM.
I tried by creating new Azure VM and enabled RDP port 3389 but still getting same connection issue.
How to resolve issue.
When debugging RDP issues one tool I use to test connectivity from a windows client is:
start
run
cmd
telnet ip port
e.g telnet 99.99.99.99 3389
noting you may need to install the telnet client from windows features tool
Try this from multiple locations with different public addresses (including from the VM itself in some circumstances but clearly not for your issue).
Does it connect to the RDP Server listening port ?
If the answer is yes then you know the server is listening.
If the answer is no then the port is likely blocked, service is not available or a routing issue could be the cause.
Thinking out loud review the resources you have sitting in front of the VM:
window firewall (Disabling all firewall profiles is a more foolproof way of troubleshooting than setting the RDP-specific firewall rule, see REF)
local network outbound traffic blocks
firewall in front of the vm
Ref:
https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshooting/enable-disable-firewall-rule-guest-os
i'm using the portal : https://portal.azure.com, and log in with your Azure account.
I made 2 VM one Windows and other Linux.
But when i want to open them with RDP (win2016) and SSH (linux) with the Key Public/Private made correctly (puttyGen, Putty) i can't run them.
What i have to understand.
I'm connected on public wireless (SSID MacDonald or SSID Airport), my VM IP are founded with :
Get-AzNetworkInterfaceIpConfig
i set a Static IP from the Configuration NetWorking of my VM (Linux and Windows).
But what i can do to resolde this issue that i can't connect on my VM, with RDP or SSH ?
thank you
I think more info will be needed for someone to be helpful here.
first wall, what error message did you get when you try to connect using RDP or SSH?
did you allow RDP or SSH port when you create these VMs? These can be checked in VM settings page on the Azure portal. below is a screenshot of my Linux VM, for your reference:
update:
I'm not allowed to comment at the moment, so I'm posting my response to the additional info here.
if you're able to connect to the VMs using another connection, it means things work as expected on these VMs. Most likely the wireless connection you mentioned blocks outgoing RDP or SSH traffic. check with its admin on that.
I currently need to run some windows-specific software for part of a workflow, and I can't run it on my personal computer.
I have got the free account at Azure, so I thought I would use the remote windows machine. I created the VM, and I can see the login screen on Boot Diagnostics.
However, I can't connect to RDP. Tried several issues and solutions (all provided on Azure docs), to no avail.
A few steps I already did:
Checked network configs. Tried different external ports for RDP (if somehow the RDP port could be blocked somewhere). I also tried basic configuration, advanced configuration.
Re-created the external IP's. The machine can't be pinged, and I don't seem to be able to trace routes for them.
Re-deployed the machine, deleted and created a new machine.
Switched and tried different Linux RDP connectors, and even used a friends Windows computer to try to connect, to no avail.
I could gladly use any help troubleshooting this.
My machine is currently running Linux Mint, on the eduroam Wifi networks.
Thanks in advance, and feel free to ask for any additional information or configuration.
Properly, you could check if the RDP port is blocked on NSG(vm nic level or subnet level NSG), you could follow this to open the port.
Also, you could verify if the networking connectivity issue from your local computer to Azure following by Using Telnet to Test Port 3389 Functionality. For example, run telnet VMpublicIP 3389 in CMD as the administrator account.
If the RDP port is already enabled in NSG, see Troubleshoot an RDP general error in Azure VM and Troubleshoot Azure VM RDP connection issues by Event ID
Tried on another network and it worked. It seems eduroam blocks RDP even when it is on other ports.
I have a azure cloud cluster with an sql availability (2 sql machines and one quorum) group and a listener on port 51101. The cluster also contains several other VMs, all on the same virtual network.
I'm having problem connecting to the listener, and the problem is not SQL specific, since I can't even telnet to the port. The weird thing is that this happens only when connecting from a machine on the same virtual network. If I try to connect from my local non-azure machine, everything works fine. It also works if it's an azure machine on a different network.
Here's what I have:
- Firewall rules for the port. I even tried disabling the firewall completely on all the machines
The port has a load balanced endpoint on the Azure portal. Note that the same problem applies to all the ports that were open by default by Azure (RDP and WinRmHttps) - I can telnet to those ports from my machine, but not from a machine on the Virtual Network.
I can reach the SQL intance directly (If I use the instance name instead of the listener)
Here's my virtual network configuration:
Any suggestions for the cause of the problem, or some ways to debug this are welcome.
Just in case anyone runs into this, I found the answer here:
Keep in mind that your application, in case is deployed in Azure,
cannot reside in the same Cloud Service with SQL Server VMs otherwise
routing in Azure will fail: it’s highly recommended to use a dedicated
Cloud Service containing only the SQL Server VM;
Once I put the connecting machine on a separate service, everything worked.
Try these standard techniques for debugging listeners: http://www.eraofdata.com/verifying-and-troubleshooting-sql-server-listener-connectivity/ Azure won't treat them any differently if you are using a Virtual Network and a single Cloud Service.
Have you don't a netstat on the machine the listener is on to see if anything is listening on that TCP port?
We are unable to connect to our created VM in the cloud from our company (RDP, Telnet and ping).
We can do it from the VM to our company... so the Azure Tunnel is up.
We also able to connect to this VM if we use the public address
We try several thing, stop the firewall, adding endpoint.
Can you help us?
Thanks
Steve
I had a similar issue with MySQL server installed on VM, and endpoint TCP on port 3306 was defined exactly according to the guides, however couldn't connect from remote places not by MySQL or telnet.
I look for day's until I've checked -
Control Panel\System and Security\Windows Firewall\Allowed Programs
in the VM, and saw that for the program MySQL56 the public check-box was unchecked.
checked it, and connection has open.