SOLVED smb/cifs not accessible after update

Status
Not open for further replies.

heffjos

Cadet
Joined
Nov 7, 2014
Messages
5
Hi,

I updated from FreeNAS-9.3-STABLE-201501212031 to FreeNAS-9.3-STABLE-201502162250 using the GUI. My shares are no longer available on my Windows machines. I can log in through ssh and the web gui. If I boot from the previous version, the shares are again accessible.

Nothing was changed in the CIFS share options. I included screenshots of my CIFS screens. I ran testparm and see not problems either. I also included the last 100 lines of /var/log/messages.

Any help would be appreciated.
 

Attachments

  • CifsSettings1.png
    CifsSettings1.png
    28.9 KB · Views: 387
  • CifsSettings2.png
    CifsSettings2.png
    10.6 KB · Views: 381
  • testparm.txt
    2.7 KB · Views: 335
  • messages.txt
    9.5 KB · Views: 369

djonik1562

Explorer
Joined
Feb 6, 2014
Messages
61
I have same problem too. On FreeNAS-9.3-STABLE-201502110455 good work. After update to FreeNAS-9.3-STABLE-201502162250 or FreeNAS-9.3-STABLE-201502210408 sharing don't work. I must rollback on FreeNAS-9.3-STABLE-201502110455 after update and charing working. Please, help.
 

rogerh

Guru
Joined
Apr 18, 2014
Messages
1,111
CIFS sharing to Mac and Windows 8 is working in 201502162250 for me. But my WINS server (a somewhat flaky version of SAMBA on SuSE 11.4) does not seem to be advertising my FreeNAS CIFS shares so I need to actually open \\<netbios-name-of-FreeNAS>\ in an explorer window to find them.
 

Osiris

Contributor
Joined
Aug 15, 2013
Messages
148
My newbish 2 cents:

What do you mean by "sharing doesn't work" ? You say your shares are no longer available.
Are they actually even when accessed from winX via \\nas-ip\share or are you getting the good ol'e Error 13 Permission Denied when connecting to them ?
If so, it's a known (windows) bug which I encountered when connecting to cifs after a freenas upgrade.
Change your cifs password to something else & then back to the same & retry.

Could you post the content of
Code:
/usr/local/etc/smb4.conf
 

djonik1562

Explorer
Joined
Feb 6, 2014
Messages
61
Sharing doesn't work - on my network i can't see freenas. I try open \\nas-ip - not opened. Thinking, thinking and doesn't open.
 

heffjos

Cadet
Joined
Nov 7, 2014
Messages
5
Same thing is happening to me. In explorer, if I type \\nas-ip it times out and pops up with "Windows cannot access \\nas-ip". Here is a screenshot of the remaining message:

WindowsError.png


When I try to troubleshoot the problem in Windows, it comes up with this error:

TroubleShoot.png


I changed my user password for both my Windows and FreeNAS machines, but I still cannot connect to CIFS shares from my Windows machines. I also tried booting from a fresh install of FreeNAS on a different USB, but I still couldn't access the CIFS shares. I may try this option again, because there were other problems that were also happening when I did this. Everything still works with 201501212031 on the original USB. I attached /usr/local/etc/smb4.conf file and the past couple days of /var/log/samba4/log.smbd. Where would the error 13 show, in /var/log/messages?
 

Attachments

  • log2.smbd.txt
    14.2 KB · Views: 449
  • smb4.conf.txt
    2.5 KB · Views: 352
D

dlavigne

Guest
Please create a bug report at bugs.freenas.org and post the issue number here.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
You should attach a debug file to this thread too...
 

djonik1562

Explorer
Joined
Feb 6, 2014
Messages
61
I now updated to FreeNAS-9.3-STABLE-201502232343, but CIFS don't working, Rollback on FreeNAS-9.3-STABLE-201502110455.
You should attach a debug file to this thread too...
What debug file? In CIFS set log to debug and get debug file?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
It's a button in the GUI. Sorry I don't remember where it's at but I'm sure you can find it.
 

djonik1562

Explorer
Joined
Feb 6, 2014
Messages
61
Debug from GUI. When freenas running, sharing thinking, thinking. When freenas i rebooted, then error "Connection problem".
 

Attachments

  • debug-djoniknas-20150225203502.tgz
    406.7 KB · Views: 330

heffjos

Cadet
Joined
Nov 7, 2014
Messages
5
Just an update, a solution was found. I had to add the line "127.0.0.1 mymachinename mymachinename.domain.name" without quotes to /etc/hosts file.
 
Status
Not open for further replies.
Top