FreeNAS-11.1-U3 user can't connect to share

Status
Not open for further replies.

vikozo6

Patron
Joined
Oct 16, 2015
Messages
290
hello
after a update to FreeNAS-11.1-U3
the user can't login to the smb share

after going back to FreeNAS-11.1-U2 it works again
hava a nice day
vinc
 
D

dlavigne

Guest
What exact error appears in the logs after the failed connection?
 

Bageland2000

Dabbler
Joined
Aug 24, 2014
Messages
48
Hello,
I have the same problem. I went into users to update my password and it errored out as well . Logging into the share on Windows yielded a wrong password error. Please let me know what data I can provide to help diagnose.
 

ere109

Contributor
Joined
Aug 22, 2017
Messages
190
I was able to go into Account > Users and manually re-enter my password to solve this.
 

KrisBee

Wizard
Joined
Mar 20, 2017
Messages
1,288
Just upgraded a test FreeNAS VM from u2 to u3, it's the SMB password database that gets wiped which obviously is bad news.

Before:

Code:
root@freenas:~ # pdbedit -L -v
---------------
Unix username:		rancher
NT username:		  
Account Flags:		[U		  ]
User SID:			 S-1-5-21-2611193793-3872297391-549815604-1003
Primary Group SID:	S-1-5-21-2611193793-3872297391-549815604-513
Full Name:			rancher
Home Directory:	   \\freenas\rancher
HomeDir Drive:		
Logon Script:		 
Profile Path:		 \\freenas\rancher\profile																											  
Domain:			   FREENAS																																
Account desc:																																				
Workstations:																																				
Munged dial:																																				 
Logon time:		   0																																	  
Logoff time:		  9223372036854775807 seconds since the Epoch																							
Kickoff time:		 9223372036854775807 seconds since the Epoch																							
Password last set:	Fri, 29 Dec 2017 10:09:24 GMT																										  
Password can change:  Fri, 29 Dec 2017 10:09:24 GMT																										  
Password must change: never																																  
Last bad password   : 0																																	  
Bad password count  : 0																																	  
Logon hours		 : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF																							 
---------------																																			  
Unix username:		chris																																  
NT username:		  
Account Flags:		[U		  ]
User SID:			 S-1-5-21-2611193793-3872297391-549815604-3000
Primary Group SID:	S-1-5-21-2611193793-3872297391-549815604-513
Full Name:			chris
Home Directory:	   \\freenas\chris
HomeDir Drive:		
Logon Script:		 
Profile Path:		 \\freenas\chris\profile
Domain:			   FREENAS
Account desc:		 
Workstations:		 
Munged dial:		  
Logon time:		   0
Logoff time:		  9223372036854775807 seconds since the Epoch
Kickoff time:		 9223372036854775807 seconds since the Epoch
Password last set:	Wed, 18 Oct 2017 10:15:48 BST
Password can change:  Wed, 18 Oct 2017 10:15:48 BST
Password must change: never
Last bad password   : 0
Bad password count  : 0
Logon hours		 : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF


after:

Code:
root@freenas:~ # pdbedit -L -v
root@freenas:~ #
 
Last edited by a moderator:

FuriousPy

Dabbler
Joined
Jan 24, 2018
Messages
10
After returning to U2 I could not connect, even after changing the password...

It seems this did solve it to me.

Go to Services -> SMB -> edit and check bind to the IP of the NIC
Capture.JPG
 
Last edited:

FlangeMonkey

Contributor
Joined
Dec 6, 2012
Messages
111
I have rolled back to RELEASE for the time being, when I checked the sam database using "pdbedit -L -v" it was empty in U3 and full in RELEASE. The change in bind's made no difference in U3 and it was working as expected in RELEASE.
 

jon_2112

Explorer
Joined
Feb 8, 2016
Messages
52
Same happened here. Samba passwords got wiped out. I only have a few users, so I just went and manually put the passwords back [via the web] and will hope I don't have any issues.
 

Craash

Cadet
Joined
Jul 24, 2017
Messages
5
Same here. Confirmed resetting the password on one account did fix the issue. Now to deal with the mess of the other accounts . . .

Sure seems like a big thing to miss when I'm on the 'stable' channel . . .
 

oRAirwolf

Explorer
Joined
Dec 6, 2016
Messages
55
I am experiencing this problem, too, after upgrading to U3 on the stable train. I only have a single user (myself). I tried both resetting and changing my password, but it is not helping.

Edit: I have a virtualized server in a DC that I use as a lab and I was able to reset my password there to fix the problem. For some reason, it is not working on my home server, though.
Edit 2: I was able to resolve the issue on my home server by rebooting my desktop. Other computers on my network were able to access the SMB share without rebooting.
 
Last edited:

davidjb

Cadet
Joined
Mar 20, 2017
Messages
3
Same issue here as well. Resetting the password for accounts fixes the issue as others have found. Is there a reported bug on the issue tracker?
 
D

dlavigne

Guest
Same issue here as well. Resetting the password for accounts fixes the issue as others have found. Is there a reported bug on the issue tracker?

Yes, two at the moment to see if they are the same issue (both hidden due to debugs).
 

Ruff.Hi

Patron
Joined
Apr 21, 2015
Messages
271
Ditto here ... booted back to U2.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Status
Not open for further replies.
Top