Struggling with credentials to shared drive, on just one client

[Marc_G 95]

Hi folks,

 

I've seen threads recently tangentially similar to this, but so far I haven't been able to resolve this problem. Maybe someone more networking proficient than I am can help me sort this out.

 

My Emby Server is on a Win10 box. It has several media folders on local drives in the box, which are shared via standard windows sharing with "Everybody" (no Homegroup or anything), and until recently there was no problem. Nothing changed other than windows updates on my network within the last 10 months.

 

One computer, which is my Windows 7 Pro desktop, which happens to be my "primary computer" and where I do all my ripping and such, suddenly started prompting me for credentials to access the shared files on the server. This happened after BOTH server and Desktop took some updates.

 

Each time I log off or reboot my desktop, I now have to re-enter the credentials for the server to access the files through simple network browsing.

 

It doesn't seem that other computers on the network have this problem. Two computers (one Win10, one win 7) seem free of it.

 

I've gone into the credential manager on the Desktop, removed credentials, recreated them (shows as enterprise level), but still when I reboot or often just log off / log on, I have to redo access. What gives, and how to fix it?

 

Thanks!

[Marc_G 95]

I may have solved this. It's working so far.

 

So, all three mapped shared drives were on the same home theater server. I had, in initial trouble shooting, deleted one of the mapped drives, then re-mapped it. The problem still occurred.

 

This time I removed all three mapped drives, leaving nothing behind on my desktop that was from the server. Rebooted desktop. Re-mapped the drives. Now, the credentials seem to persist. We'll see how long it lasts...

[Luke 42077]

Well done.

[Marc_G 95]

As a follow up to this thread, the problem recurred.

 

All was fine for three weeks or so, across many logoff/logons and shutdown/restart cycles.

 

Over the weekend I let the computer take an "important" windows update (Win 7 x64). After that immediately the credential problem came back. After each logoff/log-back-on I would have to resupply my credentials to the share.

 

AGain, I deleted all of the shares on that server, rebooted, and recreated the shares. The credentials now persist across restarts.  Not sure why this is the case, and why it keeps breaking with each windows update.

[mastrmind11 722]

simple solution.  get a Linux server

[Marc_G 95]

simple solution. get a Linux server

The problem is with the desktop client, not the server [emoji3]

[mastrmind11 722]

The problem is with the desktop client, not the server [emoji3]

simple solution, throw windows out your back door

 

j/k, I still have a windows client around,  sole purpose is for Microsoft Money LOL (and Nvidia Now for hopefully some day when the kids can wipe their own asses).

[Marc_G 95]

Yeah I have a few apps that are specialty without Linux versions so I'm stuck with MS. Had thoughts about going to win 10 for this one but just so comfortable with 7.

[Luke 42077]

I think the issue is that windows 10 no longer allows anonymous network shares, at least not very easily anymore, right?

[Marc_G 95]

I think the issue is that windows 10 no longer allows anonymous network shares, at least not very easily anymore, right?

Possibly, but my other computer on the network has no problems accessing those same shared folders. Never need to re-enter credentials on it (a win10 mini laptop). So the problem seems localized to the win7 client.

[Marc_G 95]

This problem continues, but is now known to be the symptom of TWO SEPARATE problems.

 

1. The Win 7 client now loses credentials with every reboot (and I think, even logoff/logon), even when those credentials are entered directly through the credential manager, with no prior credentials present for the server. Sigh. This started maybe in December or so. It has gotten worse lately; it used to be that if I manually entered them, they would persist for a while. No more. Other computers on the network that I've tried don't seem to experience this problem, just my desktop. It's not a problem at the server, specifically, because other computers retain the credentials.

 

2. It occurred to me that credentials shouldn't need to be stored; the server is set to have password protected sharing OFF. I purposefully set it that way to enable easy access to the media from other PCs, and on my home network I'm not too concerned about this security hole.  I have REPEATEDLY set this one to password sharing--OFF. Guess what? It got turned ON again.  I checked this morning and indeed somehow it flipped back to on. Since I had turned it off before this didn't occur to me as a likely problem.

 

Having re-corrected item 2, the symptom is now in remission, for the moment.

[Luke 42077]

Well done.

[Marc_G 95]

All was well on this until the recent windows 10 update. After my server took the update, the problem accessing the drives recurred. I checked the server's settings about password protected sharing, and found the update had turned password protected sharing back on. I turned it off again. At least I know where to look when this problem recurs.

Edited June 13, 2018 by Marc_G

[Luke 42077]

Thanks for the feedback.

[tdiguy 99]

simple solution, throw windows out your back door

 

j/k, I still have a windows client around,  sole purpose is for Microsoft Money LOL (and Nvidia Now for hopefully some day when the kids can wipe their own asses).

I have a windows client still also, my main laptop for "gaming" but its 3 years old now. I have a mapped drive on it for my ubuntu server make renaming things or moving things around a little easier on me, though i have started getting pretty good with the bash commands.