I am following the information in this documentation to access azure storage emulator (locally)
http://msdn.microsoft.com/en-us/library/azure/hh403989.aspx
In the storage emulator, because the local computer does not perform
domain name resolution, the account name is part of the URI path. The
URI scheme for a resource running in the storage emulator follows this
format:
http://<local-machine-address>:<port>/<account-name>/<resource-path>
The following format is used for addressing resources running in the
storage emulator:
Blob Service:
http://127.0.0.1:10000/<account-name>/<resource-path>
Queue Service:
http://127.0.0.1:10001/<account-name>/<resource-path>
Table Service:
http://127.0.0.1:10002/<account-name>/<resource-path>
For example, the
following address might be used for accessing a blob in the storage
emulator:
http://127.0.0.1:10000/myaccount/mycontainer/myblob.txt
It works fine if I try to access it from anything running on my computer, for example a local IIS server etc, that's because it has access to 127.0.0.1 on the pc
But what if I try to access it from an mobile device on the same wifi network ?
I can access local IIS servers from a mobile device by going to applicationhost.config and binding the local IIS server to the computer LAN IP for example 192.168.1.5 etc
Any idea how can I do this binding for the azure storage emulator ? i.e. how do I expose it to the LAN ?
Thanks
The local emulation services were not intended for remote access. I do recall reports of folks setting up "loop back" connections to help enable this. But IMHO, in most cases its almost easier and more cost affective to simply run the services in the cloud. This also helps avoid any issues with differences between cloud and on-premises.
If we look at doing mobile device development... You could easily spend several hours trying to properly set up the loopback. If we put a price on this... say $25/hr.. and we spent 3 hours setting it up. So we just spent $75 to build that out. By comparison, we likely could have used that same $75 to do our dev against a cloud storage account for the better part of a year.
I also faced similar issue where I wanted to access the azure storage emulator from another linux host for development. I ended up installing a local proxy server on the windows host which forwards request to the emulator instance.
Related
I've a nodejs app using this npm package (https://github.com/ancasicolica/node-wifi-scanner ) which basically use netsh wlan command to list all surrounding wifi. when I run this locally, everything fine but when /I deploy this to Azure Web App, it will only return the connected WiFi but bit surrounding. Any idea of what might have been wrong on Azure?
As the Technical background describes:
The module uses command line tools for gathering the network information:
netsh on Windows: netsh wlan show networks mode=Bssid
And we do not have sufficient permission to run this command on Azure Web Apps.
And secondly, As #astaykov said, Azure is a cloud compute platform, all the services and resources are in the Azure Data Centers, which cannot detect your WiFi environment on your local.
You cannot approach your requirement on any cloud compute platforms. You need to to the detection operations on your client side or devices.
There is nothing wrong on Azure!
Do you really expect to scan for WiFi networks inside an Azure Data Center (the chance that there is a WiFi network inside Azure Data Center is close zero) ?!
Do you believe that servers running inside Azure Data Center do have WiFi adapters (I don't) ?!
And what exactly are you trying to achieve - a server based application running on server somewhere on Internet, using netsch on the server to scan for WiFi networks available on your laptop? No, this is not possible. And this is not Azure limitation, and has nothing to do with Azure.
We have a setup where we have both VMs and Web Apps in Azure connected to our on-premise resources via a point-to-site virtual network.
We have an folder on premise with access to Everyone open (both on the share and NTFS) and the Azure VMs that are on that virtual network are able to browse to the share without difficulty.
The web apps are not able to access them however.
I'm assuming the following line in this article explains the reason, but I'm looking to confirm this is not possible:
The work required to secure your networks to only the web apps that need access prevents being able to create SMB connections. While you can access remote resources this does not include being able to mount a remote drive.
Coming out of the logs from the attempt from the website to access it:
Taking the C# code out of the picture, trying to get the directory listing from the powershell console on the web app:
I've also tried this with Hybrid Connections, and am getting closer - once it's setup and attached to the Web App, I'm able to tcping the SMB port from the powershell console (which is further than I can get when using the VNET), but it's still unable to list a directory:
Any thoughts? Anyone doing anything similar?
The tcping result is actually misleading - you are really pinging a local port hosted on your web app (hence why the tcping has results of ~1ms). Tcping doesn't actually test the full tunnel for Hybrid Connections because the tunnel is a TCP level data relay only (that is, it does not send TCP headers, etc., over the tunnel, only payload) and tcping does not send any data, only simply verifies that the TCP handshake succeeded.
Unfortunately, the article is correct - SMB will not work at all in your Web App. There are security layers in place that will block the attempt.
Previously i have asked question to choose service from windows azure which is best suitable for my application and based on answer # Can we run windowservice or EXE in Azure website or in Virtual Machine? I am going to use Virtual Machine
Regarding WAVM i have below queries
1)Can i implement SSL in same manner as we can do in dedicated server through IIS settings?
2)Also for stroing files/image i am not going to use storage account, so would be there any issue regarding this?
Thanks in advance!
You can use SSL the same way as on any Windows server. Dont forget to add the endpoints for internet (80) and SSL (443). The best way is to have the same port numbers externaly.
I have used this in a training for WIF where the Domain controler and ADFS were on a virtual machine in Azure.
For the second awnser. the C:\drive (OS disk) has a differnt backup senario than the disks you ad to the VM. So for storage of data add a Datadisk to your VM. The disk have a max size of 999GB. Depending on the VM size you can mout up to 16 disks. See image for instructions
The vhd file for the disk is in Azurestorage and therfore replictated 3 times localy and 3 times due to georeplication.
S.Y.
Michiel van Buuren
Do you know the way how to set azure webrole as NTP Server ?
I'd like to synchronize my computer's time with my azure webrole's time exactly instead of 'time.windows.com' or other ntp servers.
Because I need to synchronize my computer's time as accurate as possible with my webrole's time, and I'm thinking of the only way is setting my azure webrole as my local computer's NTP Server.
I tried to command (like 'w32/tm ...~~~' and etc..) on my azure webrole to make it as NTP Server, and it didn't work, although it worked on my different computer which is in my office.
How can I do ?
Windows Azure roles (Web, Worker etc.) do not support hosting of UDP endpoints currently so I'm not sure what you are attempting to do is feasible. Windows Azure Virtual Machines (Preview) can host UDP Endpoints so this might be one workaround (albeit expensive).
Check out this great blog post for a detailed explanation of Azure VM's and NTP Server details.
How frequently is the clock on my Windows Azure VM synchronized? : http://blog.codingoutloud.com/2011/08/25/azure-faq-how-frequently-is-the-clock-on-my-windows-azure-vm-synchronized/
It would be good to know why you want to synchronize with the web/worker roles directly instead of with time.windows.com. The web/worker role VMs are synchronized with time.windows.com by default anyway. Also, Windows Azure does support UDP protocol with their latest June 2012 update.
Recentely, I deploy a worker role that it will connect to internet and attemp to access some websites (For example: http://somewebsite.redmond.corp.microsoft.com/en-us/library/).
It successfully access the websites on my development machine running on emulator. But on the Azure virual machine that I deploy my worker role to, it is not able to access the websites. I try to open the websites on VM browering in IE, it is also not able to.
Have u emcounter similar issues? How do u deal with it?
This has nothing to do with accessing the Internet. The URL you provided isn't publicly visible (at least I can't access it from my machine). This means you're attempting to visit a URL behind a firewall, possibly requiring a VPN to access.
Windows Azure VM's, whether worker roles, web roles, or Virtual Machines, are in a public cloud and not behind any firewall. If you wanted to access it from a Windows Azure VM, you'd need to set up a Virtual Network, introduced in the Spring 2012 update. More information here.
Try using Elevated premissions for this. Once,I tried to access internet through RDP of a Role, It was working at that time hence it should be possible for you to access internet. But if are trying to download exes and execute, I Think that isn't possible.Please post you Results here.
Regards,
Vijay.