Samba broke after upgrade to Stretch (SOLVED Finally)

[02ebz06]

Had no problems going from Wheezy to Jessie, but Samba broke with the upgrade to Stretch.
Anybody else have this problem?

I have two servers.
Samba runs standalone on both.
One is my primary server and the one I did the upgrade on is a backup server.
Upgrade was pretty uneventful.

Username/Password is same on my Windows PC (win-7) as the Debian servers.
Also same for Samba.
When I try to connect from my PC, I get prompted for a username/password.
I type in valid info, but keeps prompting.
Been googling and fighting this for two days now.

Any ideas?

TIA

[02ebz06]

A little more information...

Samba versions is 4.2.14 on Jessie.
The upgrade to Stitch upgraded Samba to 4.5.12

[Bulkley]

Wild stab in the dark: Does Samba create a configuration somewhere? Try renaming it and reboot.

[02ebz06]

There is an smb.conf file, but it defines all the shares.
I tried removing Samba and reinstalling, that didn't help.
Getting ready to do that again and delete all the files that didn't get removed.

[02ebz06]

Well, after many hours of googling and trying different things and none working, I finally found the answer.

The problem was not with Samba, but Windoze.
Turns out Windows caches credentials. A reboot doesn't clear them.
I had to issue this command in a DOS window on each PC --> net use X: \\<servername>\<sharename> "" /user:""
It created an X drive and I could access the files.
After that I could click on a desktop shortcut to a Share and would connect directly without a username/password prompt. Whew!!!

Hopefully my agony will help someone else using Samba that has the problem after upgrading.

Here is a link to the page that solved my problem.
https://superuser.com/questions/863243/ ... x-does-not

[02ebz06]

Well, what I posted just above turned out to be a short term fix.
That works until you reboot (or log out and back in) the Windows PC. Then you get the username/password prompt again that doesn't accept a correct combo.

[02ebz06]

Finally found the answer.
Had to add the following to SMB.CONF

[guest]
# This share allows anonymous (guest) access without authentication!
path = /srv/samba/guest/
read only = no
guest ok = yes

Not sure what changed or why I had to do this, but it works now.
When prompted for Username/Password, enter guest, leave password blank, and check the remember username box and hit enter.
That's it.
All future connects after a reboot or log out/in will not ask for username/password.

Now on to find why emacs broke on one server and postfix on the other.

[stevepusser]

If there really was a Stitch release and someone asked about installing LILO on it, that would be perfect.

[02ebz06]

Yeah, I realized that this morning.
Had Stretch in the text, buy Stitch in subject.
My brain was on vacation I guess.