Can't connect to CIFS using "FreeSync" for Android

Status
Not open for further replies.

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377
I'm trying to access my CIFS share via wifi on my Android phone (for automated phone backups) but it refuses to connect with an error "Failed to connect: 0.0.0.0<00>/192.168.0.9"

I've tried with and without the use anonymous login option ticked.
I know the app works because I just set up a share on my Windows PC for this and when I tested it the error wasn't failed to connect it was "Logon failure: unknown user name or bad password" so it's clearly getting further.

I'm using 9.2.1.6 of FreeNAS and I'm going to assume the CIFS implementation on FreeNAS is (obviously) not entirely identical to Windows but I'd figure it should be compatible enough with the standard?
Has anyone got this app to work? Here's a link to the free version:
https://play.google.com/store/apps/details?id=dk.tacit.android.foldersync.lite
You configure your shares / destinations under the "accounts" section, should only take a matter of 90 seconds for another FreeNAS user to test.

I've messed around a fair bit with FolderSyncs options and I'll be damned if I can get it to connect.
If someone can tell me if the CIFS daemon has a log file, I'll gladly post it if it'll help (but I don't know where it is on my FreeNAS machine)
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
I have the paid version, and I can tell you that it most definitely works with FreeNAS. Your problem is almost certainly file permissions, so I'd start looking there.

The log you are looking for should be in /mnt/<poolname>/.system/syslog/log/samba4
 

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377
Sweet! I'm glad someone else has it working, yeah darn 0k, well at least I know.
I'm a version behind on FreeNAS and I know some CIFS changes happened but I doubt it's that is it?
I'll find the log, I was just reading doco already too.

EDIT: also for the sake of future timesaving for yourself - is that path in the CIFS doco (it probably is but I couldn't' find it yet?) might be something that should be if it isn't.
 
Last edited:

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377
Got the bastard! Well... kinda!

[2014/09/22 15:27:47.813123, 3] ../source3/smbd/process.c:1405(switch_message)
switch message SMBnegprot (pid 21810) conn 0x0
[2014/09/22 15:27:47.813259, 3] ../source3/smbd/negprot.c:563(reply_negprot)
Requested protocol [NT LM 0.12]
[2014/09/22 15:27:47.813447, 0] ../source3/smbd/negprot.c:673(reply_negprot)
No protocol supported !
[2014/09/22 15:27:48.229854, 3] ../source3/smbd/server_exit.c:221(exit_server_common)
Server exit (failed to receive smb request)
[2014/09/22 15:27:48.231486, 3] ../source3/smbd/server_exit.c:221(exit_server_common)
Server exit (failed to receive smb request)
[2014/09/22 15:27:48.233025, 3] ../source3/smbd/server_exit.c:221(exit_server_common)
Server exit (failed to receive smb request)
[2014/09/22 15:27:48.234078, 3] ../source3/smbd/server_exit.c:221(exit_server_common)
Server exit (failed to receive smb request)
[2014/09/22 15:27:48.233218, 3] ../source3/smbd/server_exit.c:221(exit_server_common)
Server exit (failed to receive smb request)
[2014/09/22 15:27:48.452515, 3] ../source3/lib/access.c:338(allow_access)
Allowed connection from GALAXY-S3.fritz.box (192.168.0.17)
[2014/09/22 15:27:48.452737, 3] ../source3/smbd/oplock.c:870(init_oplocks)
init_oplocks: initializing messages.
[2014/09/22 15:27:48.453021, 3] ../source3/smbd/process.c:1802(process_smb)
Transaction 0 of length 51 (0 toread)
[2014/09/22 15:27:48.453085, 3] ../source3/smbd/process.c:1405(switch_message)
switch message SMBnegprot (pid 21814) conn 0x0
[2014/09/22 15:27:48.453220, 3] ../source3/smbd/negprot.c:563(reply_negprot)
Requested protocol [NT LM 0.12]
[2014/09/22 15:27:48.453407, 0] ../source3/smbd/negprot.c:673(reply_negprot)
No protocol supported !
 

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377
If you don't mind me asking CyberJock how's your CIFS section configured? I just want to know if I should be looking at share permissions or CIFS config.

Here's mine.
CIFS_7rohnv80ft.jpg

(I've tried fiddling with "Allow Empty Password" in the options)
 

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377
Anyone else out there - can you tell me your FreeNAS version and CIFS configuration?
 

mjws00

Guru
Joined
Jul 25, 2014
Messages
798
I went ahead and set up the free version just for fun. Worked perfectly. I just logged on as root to test access. My Cifs is exactly the same as yours except. I have no "minimum protocol."

My share and datasets on this box are pretty open and I think pretty much click ok defaults. ;) File permissions are tough to troubleshoot online. I'm not even close to attempting that.
 

Attachments

  • cifs share.PNG
    cifs share.PNG
    23.3 KB · Views: 600

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Compared to your settings the stuff I have different:

Use syslog is checked
Unix Extensions unchecked
Hostname lookups unchecked
minimum protocol is ---------
 

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377
Thanks guys, really appreciate it - it's my own dumb fault.
I was playing with CIFS near 2 months ago to try to fix a performance issue - I must've set a minimum protocol -soon as I turned that off - no worries.
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
To further explain, some Linux-based clients use smbclient. Smbclient defaults to smb1 (NT1), and this default cannot be changed (prior to Samba 4.1.0). Unsetting 'min protocol' allows the client to automatically negotiate the proper protocol to use.
 
Last edited:

FritVetBE

Explorer
Joined
Dec 28, 2013
Messages
87
I had the very same issue. For no reason i configured a minimum protocol. Setting it to blank indeed solved my issue as well regarding any linux distro or Android device to connect to my freenas box as it should. Thanks alot for the answer and further explanation!
 

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377
Just a note, I purchased FreeSync to support the developer (I actually can use only 2 folder pairs, since one pair is the entire internal SD card, the other is the external SD card) - but I thought, since the program does precisely what I want and I like the design of it (not clunky garbage) I'll support em

Anyhow, if you do buy the full version your settings won't come across, so you need to re-configure the program unfortunately, I've done so now though. It is nice to know my entire phone is fully backed up nightly. Initial sync is terribly slow but now it's 15 minutes I think for the whole lot generally in a days changes.
 

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377
Update to this thread, sorry for an old bump.
The program is "FolderSync" not "FreeSync" or "Free Sync" - and FolderSync is very good, now that it's working properly (my fault) I'm very very happy with it backing up my *entire* phone and SD card, each night over wifi. The free version supports 2 paths to backup, full one supports more. I recommend it if anyone is interested.
 

Beancurd

Cadet
Joined
Jun 17, 2018
Messages
1
Up until today, FolderSync only supports SMB1, doesn't support SMB2 or above.
The sync speed is twice as slow comparing to other File Manager android apps. The only good side about the app is it can set a scheduled time to sync my TV Shows to my android phone
 
Status
Not open for further replies.
Top