This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 93%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
My router failed and I have now rebuilt a new one, but one of the side effects was that the Drives I had created were now corrupted. I removed them using "net use /del", but I am now getting this error when trying to paste in the script from Azure portal. I have not changed any other setting and there is not "" at the end of the folder. I have even double checked to see if the Drives have really been removed, and they have. Any ideas welcome.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 51%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Hei James Pigott, Could you please post the error that you get after executing the powershell script from Azure portal.
On another note, have you tried
a. using another drive letter?
b. using another profile on the same computer?
c. trying to map the drive from another computer?
d. to check if there are any network restrictions on storage account (can be checked under Networking tab)?
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
Why would your post be considered the accepted answer? There's no explanation of why the OP is encountering the problem, nor does it offer any way to rectify the problem.
The error is here:
CMDKEY: Credential added successfully.
New-PSDrive:
Line |
5 | New-PSDrive -Name M -PSProvider FileSystem -Root "\\pigottstore.f …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| The network resource type is not correct.
To answer you other questions:
a) It failed
b) Don't have one except Admin. If I use this would I still see it using my profile afterwards?
c) It maps from another computer, and used to map from mine
d) I used to connect, my router corrupted the link, it would be a massive coincidence if other properties have changed
Thanks,
James
Is the correct IP address being used? Try these commands. Use the fully qualified name if needed.
Test-NetConnection pigottstore -CommonTCPPort SMB
net view \\pigottstore
Yes, the TCP connection is being made, the code I use is copy and pasted from Microsoft Azure portal, so I expect it to contain the right info! As I have said before, this used to work until router messed it up. Where can I find registry entries for this stuff to make sure nothing corrupted is still present? Thanks
A router change might change the network subnet that your PC is on. In that case you might need to update firewall rules. Did both of those commands work? Did net view list the shares?
Please share the output that those 2 commands produced.
It should look something like this.
That doesn't show the entire cmdlet and its parameters. That's why you need to post the CODE and not just something you think is enough to determine what is going wrong.
The "The network resource type is not correct" can have a few causes:
Correct, the term Test is not recognised.... is the error I get. There is also a fifth cause - my problem! All four of those listed issues are clear. I will look at the links, thank you.
I took out the -Persist and go this error:
The specified drive root "\pigottstore.file.core.windows.net\admin" either does not exist, or it is not a folder
My new router config is the same as the old one and my public IP is static and is the same. Back to the folder not existing, it is! I can get to it from another machine. What could be blocking this route?
Rich Matheisen, There is no reason to get impolite about my comment.
The image was obviously a mistake, i was updating a lot of tickets to followup and this one got through.
If i meant it as answer, i would have posted it as answer.
.....
Do you see the drive letter in the results from Get-PSDrive? Is there still a SMB mapping for the share in the results from Get-SMBMapping?
Use Remove-PSDrive to get rid of the drive letter, and Remove-SMBMapping to remove the mapping.
Hi, thanks for this. There is no mapping or drive under these commands (assuming M is what I would type, rather than M:). Still mapping not working.
I've even recreated M mapping it to a local shared folder, and then deleted it all using PSDrive cmds. No joy.
Post the code you're using to map the drive. Also, post the error you get when you try to map the drive.
None of my drive letters I want to setup appear in Get-PSDrive. No mapping either. Thank you.
Code:
$connectTestResult = Test-NetConnection -ComputerName pigottstore.file.core.windows.net -Port 445
if ($connectTestResult.TcpTestSucceeded) {
# Save the password so the drive will persist on reboot
cmd.exe /C "cmdkey /add:`"pigottstore.file.core.windows.net`" /user:`"localhost\pigottstore`" /pass:`"password`""
# Mount the drive
New-PSDrive -Name M -PSProvider FileSystem -Root "\\pigottstore.file.core.windows.net\admin" -Persist
} else {
Write-Error -Message "Unable to reach the Azure storage account via port 445. Check to make sure your organization or ISP is not blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Express Route to tunnel SMB traffic over a different port."
}
Hei James Pigott,
Thank you for the response to the questions.
Since you are able to map the drive from another computer, it is safe in my assumption that the command is correct.
Now this leaves us with 3 possibilities, either you have a network issue between your computer and the storage account or you have a profile issue or powershell issue.
Starting with the network restrictions,
On the computer that you want to use to connect the file share (important), goto Azure portal and find the target storage account.
On the storage account, the left menu has a section for help (last section), click on the sub item: "connectivity check" (screenshot attached below)
This will check the connectivity from your client computer to the various storage services.
Making sure in the process the that the router is not the issue and nor is any other restriction on storage account.
Moving to profile issue,
On the computer that you want to use to connect the file share (important), login with a different user
Then try to map the drive with the command from Azure portal.
If the command works and you have a share, then it may indicate a profile mis configuration.
Note: the share mapped on another user will NOT be available on your primary logon account.
If this is the case, the simplest way out is to create a new profile and copy your profile folders like documents and downloads to that profile, start using that profile as your own.
The not so simple way out is to repair the profile and do advanced profile troubleshooting.
Finally,
If the network drive does not map on a different profile (on the same computer), then it may be a Azure module or powershell issue.
Suggest you to then uninstall and install AZ module and then install (or repair or reinstall) the latest version of powershell. This followed by reinstall of azure powershell module.
Try the command again after this and hopefully it should work.
Install powershell on windows Uninstall module Install AZ module
Let me know how did it go.
Thanks for this detail.
The first test is passed - we have connection. The other 2 will take me longer. I will get back to you soon.
Thanks
Just run the script under another user account and got the same error. Are we now looking at a Powershell issue then?
One more thing; I do get a message that asks whether I wish to continue pasting in more than one line. The 1st line is the connect statement and then when run I need to press retn to get the next line run. When I paste this on other account or server I don't get this message. Can I turn it off somehow? Thanks
Hei James Pigott,
I am not sure how you execute your powershell query acquired from Azure portal.
May i suggested using powershell ISE, its inbuilt in windows and gives you a section to put the complete query at once along with one click execution.
I have put in the screenshot for you to try.
Nice try, but no cigar! Same result. Just don't know what is causing this, it is very annoying as I can't access any of my work files. Thanks for your help.
Ah! I took out -Persist and it worked. Of course I will have to run this every day so.... does that give you a clue as to what is wrong? Hope so.
No, no drive found... grrr
Nope, drives do not exist in File Explorer...
I knew it! Says drive already exists, then says can't find drive. How can I clear this drive please? Registry?
Ok, more confusion! I have Windows Powershell, Powershell 7, and Powershell ISE!! I have been using PS7. It had NO modules at all, so installed Az as you mentioned. I can now see it all using Get-InstalledModule. Nothing under PS either. But still no joy - should there be other modules?
The ISE has never worked correctly with PS7. There are pointers on how to modify the ISE to get it to work (sorta) with PS7, but the changes are pretty extensive. Also, ISE is no longer a supported product.
Switch to an up-to-date ISE. Visual Studio Code or Microsoft Visual Studio (the free version) both work with both PS5 and PS7. There are lots of add-ons to both of those ISEs that will make coding a lot easier.
Also, note that PS5 and PS7 store modules in different locations. Using a PS5 module in PS7 may require you to use the Import-Module with the -UseWindowsPowerShell switch.
Rich,
I don't code in PS, all I want is to map a drive to my Azure filestore and it only seems possible using this MS product. Do you have any ideas as to why this simple command which MS themselves have generated, FAILS?
Use the "net use" command then.
https://lazyadmin.nl/it/net-use-command/
Have you tried using the Windows explorer, like this. Type in the server name and hit enter.
Hei James Pigott,
This is no longer an Azure issue but something related to your machine specifically.
The powershell ISE was just to make sure you have a canvas to execute the complete command in one go, so don't read too much into it.
The powershell command essentially calls the same windows system that other tools do so if powershell executed without an error and you still do not have the drive then it is a good chance that some other things may eventually turn up to be wrong eventually, there may be other issues.
If you executed the powershell command with no error and still can not reach the drive through windows explorer or command prompt or powershell then every other solutions will just be going in circles.
My last suggestion is that you may want to give a try to "PC Reset", it is available under settings.
You can choose to keep your files and i would suggest take back up nevertheless.
Give you a fairly fresh settings to start with and that hopefully will fix the issue.
Woah! PC Reset! No thanks, I would have to reinstall all my progs again and I've just done this recently. There must be some registry settings I can wipe out instead, no?
We are in this mess because coding today is shit and no one code errors properly with a full range of messages for the user so they can actually fix things.
Hei James Pigott, explore reset with keep file, it does not wipe or remove programs/files just resets windows.
Dont take my word for it, research.
I dont mean to be insensitive but i think you will agree that this is no longer an Azure storage account issue.
It is not possible to troubleshoot a PC based on comments, you may need to contact your IT support for better options.