Mapping A Share Fails to Connect At Startup

We might have something that is workable here using UNC as sphardy suggested.

I opened windows explorer and typed "\\NAS-01-F0-3F\files" in the address bar without quotes. I hit enter and it prompted me for username and password. I entered them and checked "save credentials". The share opened up to the files. I created a shortcut to the share in my taskbar. Then I tried to reboot and open the shortcut to the NAS I created and it prompted me for a username and password again. I filled out the information again and checked save credentials. I opened up the credential manager and the username and pass I asked it to save were there but the Persistence was set to "Logon Session". I also noticed that the username was set to RAVEN\My_NAS_Username. I rebooted and sure enough the credentials were gone. So I opened up credential manager again and pressed "Add a Windows Credential"

For Internet or network address I used: NAS-01-F0-3F
User name: RAVEN\the username of the user I created on the NAS
Password: the password of the user I created on the NAS

I pressed ok and the Persistence was set to Logon Session. Strange...

So I removed the credential from the vault and tried again this time with the following (I omitted the name of my computer "RAVEN"):

For Internet or network address I used: NAS-01-F0-3F
User name: the username of the user I created on the NAS
Password: the password of the user I created on the NAS

After hitting ok I viewed the credentials, I received "Enterprise" as my persistence so I thought maybe this will work. I rebooted and tried to open the shortcut to my share drive. No dice, I got prompted for my username and password again.

Back to the credentials manager I go. This time I tried adding the name of the NAS to my username:

For Internet or network address I used: NAS-01-F0-3F
User name: NAS-01-F0-3F\the username of the user I created on the NAS
Password: the password of the user I created on the NAS

Hit ok and got "Enterprise" for persistence. Rebooted, clicked on shortcut and it opened without a prompt (albeit after a few seconds of the spinning blue circle). Now for the next test. I added a music file to itunes that exists on the share and played it. Rebooted the PC and first thing opened up itunes and tried to play the song. Waited a few seconds (I assume these are the same few seconds that I initially saw when trying to open the shortcut) and the song played! It appears that the right combination of credential manager username (adding the NAS name prior to the username) led to the correct "Enterprise" persistence and the ability for the NAS to connect without prompting for username and pass. I am going to try this method with mapping the drive as well. Stay tuned...