I have subscription to Azure server running Windows 2008 Server r2 Datacentre, 64-Bit. I have shared a folder in the root of its C drive with full permission to 'Everyone' (along with default users/groups). Both Azure Windows firewall and my local system Firewall are OFF. No other changes have been made in Azure from the default settings. In Azure control panel, Site URL of Cloud service and DNS of Virtual Machine are showing same and the Public IP of both Cloud service and Virtual machine are same.
Now, when I am trying to map this shared folder remotely using the below command,
NET USE Z: \\<IPaddress>\<sharedfoldername> /USER:<username> <password> /PERSISTENT:NO
I am getting,
"System error 53 has occured.
The network path was not found"
But, I am able to connect to the machine through RDP with the same user!
So, what I am missing? Is there any other settings required in Azure to allow this?
Thanks in advance,
Rajesh Karunakaran
EDIT ON 08-Feb-2017 (Just to explain a bit more deeper)
In our Azure subscription, we have Storage account, Virtual Machine, Virtual Network & Cloud service. After setting up a Folder Share in Storage Account, I am able to map that folder within the Azure VM using
NET USE Z: \\<IPaddress>\<sharedfoldername> /USER:<username> <password> /PERSISTENT:NO
But, what I want to achieve is to be able to access the Share Folder in Azure from my local system (I am not in US) through mapping a drive the same way. But from my local system, when I issue the same command it says
"system error 5... Access Denied"
I have opened Port 445 (File sharing....) in Azure server by logging in through RDP. (Anyway, the Firewall is OFF and I assume then port opening is insignificant)
Interestingly, when we'd taken Azure trial account (for 30 days), I was able to connect to a normal windows Shared Folder through 'NET USE' command from my local system. Is there a way to do this?
Thanks in advance.
If you want to mount file between client and server. The port 445 could be communication.
According to your description, please check as the following steps:
1.Open port 445 on Azure NSG(Inbound rules)
2.Click here to see the summary of ISPs that allow or disallow access from port 445.
You could use Portquery to check whether port 445 is open.
PortQry.exe -n [storage account name].file.core.windows.net -p TCP -e 445
More information about how to troubleshoot this issue please refer to this link.
Related
I'm trying to find an answer to the fact that everytime I want to connect an organizations account in the Account settings in VM, I cannot RDP anymore.
During the creation of the VM, I enable the Azure AD join extension.
Does this has to do anything about user log -in conflict.
I log in to the VM with my Admninistrator credentials.
Any idea would be highly recommended.
The VM is Windows 10 OS.
To avoid these issues, you can use Windows 10 Fall Creators update (1709) is a separate app that provide updated version systems current and safer defense-in-depth features that prevent evolving malware and other vulnerabilities from impacting your device,
To connect RDP, you need to add inbound port rule
In azure portal -> virtual machine -> Networking -> Add inbound port rule -> Add
Note : if you are using port 3389 kindly update destination port ranges as 3389 and name as port_3389
If you already added inbound rule and still you are facing issue refer this Microsoft document for more information
I have created a sql server instance on an Azure VM and uploaded my sql server backup and the various reports that were previously running on a local box. This has all gone well and I can connect to the database via management studio from my remote client.
I can also run all my reports locally on the Azure VM using RDP. They all work fine.
The problem comes when I try to connect to my report server using Internet Explorer from my remote client. All I get is Page is not found messages.
I have opened Port 80 on the Azure firewall and added an inbound rule in my Azure Portal to allow connection on Port 80.
I have tried using the Public DNS name I have created something like AFDSQL.NorthEurope.cloudapp.azure.com/Reports_MSSQLSERVER/Pages/Folder.aspx and also tried the IP address directly but neither work.
What am I missing?
Roy
Just got mine working!
Yes, you have to open port 80 on the windows firewall in your azure vm.
You also have to open the port in the network security section of your azure portal.
Finally the address to use is http://servername/reports/browse not reports/folder.aspx like you are used.
I am trying out the Free Trial Microsoft Azure.
Basically I created an VM running Windows Server 2008 SP1.
There, I am running GeoServer, being able to access the geoserver from the local browser (eg: http://localhost:8080/geoserver/web)
Now, how to access this from a public browser? It has a public IP 13.93.154.109
which I can't even ping it, not to say to access it.
What did I miss out?
Note: I tried both classic/non-classic VM, result is the same.
Also, I am aware that there is an OpenGeo Suite out there for Azure. But it costs a lot. What I am trying to do is, to share the VM with the other existing product.
Thanks in advance.
localhost-from-vm
P.S: I am able to ping 13.93.154.109:3389 using PsPing instead of normal Ping.
You need to open the port 8080 to allow traffic on your VM.
Depending on how you have created the VM, it can be done in different ways:
If you have used the Classic workflow, you need to add an endpoint to your cloud service: https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-windows-classic-setup-endpoints/
If you have used the Azure Resource Manager workflow, you need to create an inbound rule in the network security group: https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-create-nsg-arm-pportal/#create-rules-in-an-existing-nsg
I have a VM-1 on Azure with windows server 2012. I have installed FTP server in this. (FileZilla)
Another VM-2 in different cloud, where a windows service will access a FTP server in VM-1.
Both VMs are in different cloud. In FTP , while listing directories I am getting '425 Cant open data connection for dir listing'
I am using active mode in FTP.
But If I install the windows service in local machine, it is running correctly without any issue in FTP.
I'll answer though this isn't a programming question, because I can help. :)
When a virtual machine is created, a default ACL is put in place to block all incoming traffic other than for RDP and Remote PowerShell connections.
http://azure.microsoft.com/blog/2014/03/28/network-isolation-options-for-machines-in-windows-azure-virtual-networks/
You need inbound ports other than 21 for active connections, typically high ports above 1024, if you have port 21 open inbound already then you should use passive (pasv) mode to let the server open a random outbound port first to solve the issue of needing an ACL for other inbound ports.
More info on Active vs Passive and ports: http://slacksite.com/other/ftp.html
I've setup Azure point to site and I'm able to connect from my computer to an Azure VM (file share). I'm also able to ping my computer IP address from the Azure VM. However, I'm not able to connect to any resource on my local computer. When trying to access a file share on my computer from the Azure VM I get the following error:
file and print sharing resource (169.254.108.240) is online but isn't responding to connection attempts.
The remote computer isn’t responding to connections on port 445, possibly due to firewall or security policy settings, or because it might be temporarily unavailable. Windows couldn’t find any problems with the firewall on your computer.
Port 445 is enabled on my local computer:
netsh firewall set portopening TCP 445 ENABLE
As an additional test If I issue a \169.254.108.240 from my local computer point to itself it works fine. The same try from the Azure VM gives me the error above.
Thanks,
Your IP address (169.254.*) is a non-routable address. You'll need to get a valid IP (say with DHCP, or set manually) and allow connections to your machine. If you have a firewall, this means adding a NAT rule to it.
If possible, try making the connection from another computer on your LAN to isolate any other firewall/Azure issues.
I think you have to consider several concepts while implementing azure network, first try to put point to site network on a different range of IPs (like 10.4.0.0) then try to disable firewall on your computer and try again, if you have proper routing device it should go through and get the feedback form the local machine.