Open TonyWildish-BH opened 1 month ago
Update: This appears to be related to having had the luck to have a storage key which begins with a '/'. This is interpreted by the net use
command as an option, and the command fails.
Trying manually with the second key in the storage account, which does not start with a '/', succeeds.
Rotating the key and starting a new VM doesn't help, the key seems to be baked into the service or something.
Describe the bug I have a workspace with several Windows and Linux VMs. The Linux VMs are able to see the shared storage at
/fileshares/vm-shared-storage
, but the Windows machines cannot see it.I have enabled public network sharing/discovery, that doesn't help any.
Steps to reproduce
Screenshots showing the process of opening network drives on new VM:
On entering the VM for the first time, I get this prompt. I select 'Yes'
Then I open File Explorer, and go to the Network tab. It scans, finds nothing interesting, and shows the message about file sharing being off. I turn it on, as shown. It rescans the network, but nothing changes.
Azure TRE release version (e.g. v0.14.0 or main): commit ea63ebf, on 09/04.
Deployed Azure TRE components - click the (i) in the UI: UI Version: 0.5.21 API Version: 0.18.5