Amahi Forums

I just got a new (to me) Surface - it's running a fresh install of Windows 10 Pro, all up-to-date. I can pull up my shares in Explorer with no problem by typing \\HDA - they are all listed. But when I try to log into the shares my credentials are rejected.

I've tried with just my username and with \\WORKGROUPNAME\username as the username, then my password for the HDA. I tried going through some of the troubleshooting steps here: https://wiki.amahi.org/index.php/Shares_troubleshooting but nothing seems to be working.

When I try the "net use..." command to mount the shares as a network drive, Powershell tells me "the specified network password is not correct." But I know that I'm using the correct password because I can log into the HDA web interface and tunnel in via Putty on my desktop using my username and password.

I have my shares mapped as network drives on my desktop but really don't remember at this point if I had to do anything special to get them to work.

Any ideas on what to do next?

Did you try removing shared network password guidance.

Hi Bigfoot - sorry for the delay, my school semester began and it has been intense from the get-go.

When I look at Windows Credential Manager, I don't see anything that looks like it needs to be removed (there's nothing at all in Windows Credentials and Certificate-based credentials).

So I'm not sure what to try next

Okay I'm not sure this was my favorite solution, but I did figure something out... this post gave me a possible clue:

https://askubuntu.com/questions/1093290 ... tory-locat

I tried the suggestions give for #2, and those didn't work... but that gave me the idea to create a separate user. Doing that worked - the Surface accepted WORKGROUP/newuser immeidately and logged into the HDA. It mostly matters to me to have the connection and I won't be picky, but it doesn't make sense completely since I've had other machines connect with my credientials (ie the laptop this Surface replaced...). Anyways, HDA is working on the desktop and Surface now so at least that's a load off of my mind.

Good to hear.

Sounds like the user credentials are cashed somewhere, causing he issue.

Since you have a work around, will mark this as resolved.