Windows 10: Can't connect to Azure Storage SFTP server when IP enabled from selected virtual networks...

Can't connect to Azure Storage SFTP server when IP enabled from selected virtual networks and IP addresses in Azure Logic Apps

:)

 

Azure Storage disables local network drives

I used the Mount Azure with Powershell. the script was copied from the Azure File connect portal and other than the error trap and comments is the same as the Page Above

I also tried to mount using Windows explorer but it didn't work.

I suspect the PS script changed something that disconnected my local network shares and now cannot be located.

Its local only as others have no issue and i can still RDP and web access the server. Something changed in the file access that that script ran. I have looked in all the normal locations and all seems right.

Some of the steps i have already done.

I can ping the server via name (DNS) or IP address

I can TraceRT to the server via name or IP address

I cannot Net Use Name or IP address\share.

I have disconnected the Azure drive and removed the credential created by PS, but not sure how that could change local drive access

I don't see anything in the PS script that could alter local drive access, it just creates a credential for Azure storage and the PS drive. I am quite baffled how this occurred.

 

VS2017 message: publishing to the selected azure virtual machine has not been enabled

I am looking for help on how to resolve the following informational message when creating a publish profile in visual studio 2017: "publishing to the selected azure virtual machine has not been enabled".

I'm trying to set up a new publish profile for my production server. I have already successfully set one up for my development server. Both servers are Azure VMs. They use different network security groups.

I get this message when selecting New Profile->Azure Virtual Machines (click browse), selecting my production server and clicking OK.





I have already triple checked my firewall settings on both the VMs and Azure Portal. I don't think these are the cause though because I do not get this message when I choose my db server which doesn't even
have IIS set up. My db and production server share an Azure network security resource group.

I'm using VS Community 2017 15.9.2 with an Azure VM and WebDeploy 3.5

C:\inetpub\logs\wmsvc has no logs on my production server but DOES have logs on my development server which makes sense since it's working there.

I tried the "Import Profile" button which seemed promising but get the following message when I click the, "Validate Connection" button:

"Could not connect to the remote computer......ERROR_DESTINATION_NOT_REACHABLE".

I've tried the following references:

Tooling/docs/create-asp-net-vm-with-webdeploy.md at AspNetVMs · aspnet/Tooling

Installing and Configuring Web Deploy erty=

Deploy apps to an IIS server on a Windows VM (Classic) - Azure Pipelines

https://blogs.msdn.microsoft.com/we...-a-web-app-to-an-azure-vm-from-visual-studio/

https://blog.tallan.com/2017/05/02/deploying-a-site-to-an-azure-vm-using-web-deploy/

Troubleshoot common Azure deployment e <meta proper<meta propertcrosoft.com/eoubleshootingeta property=ot common Azuhat are deplo <meta proprn.microsoft.

https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-deployment-operations

 

Azure Storage disables local network drives

I have been experimenting with setting up our network storage on Azure. So I created a storage account, file and mapped a local drive to that folder. However that disabled all my local domain network drives and i cannot figure out what the connect PS script
changed here that makes the domain drives inaccessible.

First they came up with the Red X and would not connect or map. But later the had a blue question mark which i have never seen before.

I am able to ping the server via name and IP address, connect by RDP and access web pages. I can also access DNS off the server and internet access is unaffected. Only drives and network locations are affected.

Now it would appear that network discovery is off because i cannot see any computers on the network, but i checked and its on. I ran the troubleshooter and got could not identify the problem.

So not sure how the azure connection changed my system to not allow local connections.