How to map NAS drive to Hyper-V?

I have a Hyper-V Manager in a workgroup on 192.168.5.254 and a Freecom NAS drive on 192.168.5.30. Both are in a workgroup called JGL.
When creating a new VM I point the .iso location to \\192.168.5.30\Software\server2016.iso which it accepts but when I click finish I get the error:
Error.png
From Windows Explorer I can map to \\192.168.5.30\Software and I'm prompted for a username and password and I click "remember" (subsequent connects don't require credentials)
I can't see anywhere in Hyper-V where I can enter credentials.
ClintonKAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

joinaunionCommented:
Windows version?
David Johnson, CD, MVPOwnerCommented:
different user accounts bing used as hyper-v services are not using your user account.. try first logging into the drives as an administrator (cmd prompt run as administrator)
ArneLoviusCommented:
By default the Hyper-V services run as "Local System", this is not the same account that you are using in Explorer.

I would suggest copying the ISO to local storage on the Hyper-V server, or alternatively if you do not want to use local storage for ISOs, if your NAS supports it, create an iSCSI LUN which you then attach to the Hyper-V server and format as normal for ISO storage.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ClintonKAuthor Commented:
Created an iSCSI LUN on the Synology NAS and mounted that on the Hyper-V server.
I can now access the Software share using S:
Thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.