Network folder

[wonder]

No solution? Its a fantastic utility...
If not solution, how can add this entry in fstab? I search but I view differents options and any works...

Regards!

[JRamrez]

I think the tool you need is called smb4k in the next video what exĺican:
https://www.youtube.com/watch?v=FTnDshS8xbE

[Winux2000]

I went back to using kernel 4.12.x since 4.13 caused networking issues. There seems to be a work-a-round to this problem. Have a look here;
https://www.happyassassin.net/2017/11/03...rsion-fun/
I haven't had time to try the suggested options with kernel 4.13.x, but seems to work for others.

Up until kernel 4.13, the kernel’s default SMB protocol version was 1.0. So when you mount an SMB share, if you don’t explicitly specify a protocol version with the vers= mount option, with kernel 4.12 or earlier, SMB 1.0 will be used.

With kernel 4.13, the default protocol version is changed to 3.0. So now, when mounting SMB mounts that don’t explicitly specify a version, your system will request 3.0.

[wonder]

I went back to using kernel 4.12.x since 4.13 caused networking issues. There seems to be a work-a-round to this problem. Have a look here;
https://www.happyassassin.net/2017/11/03...rsion-fun/
I haven't had time to try the suggested options with kernel 4.13.x, but seems to work for others.

Up until kernel 4.13, the kernel’s default SMB protocol version was 1.0. So when you mount an SMB share, if you don’t explicitly specify a protocol version with the vers= mount option, with kernel 4.12 or earlier, SMB 1.0 will be used.

With kernel 4.13, the default protocol version is changed to 3.0. So now, when mounting SMB mounts that don’t explicitly specify a version, your system will request 3.0.

Hello.
Correct, this is the issue and solution.
I installed 4.12.14 kernel and with this kernel (and others olders that I have) works fine.
With newers kernels of 4.12.x not works.

Thank you very much!!

[leszek]

Nice finding. So actually it is a problem of the device you try to connect to as it is using an outdated smbv1 protocol.
I would recommend updating that device if possible in the upcoming new year.

[wonder]

Nice finding. So actually it is a problem of the device you try to connect to as it is using an outdated smbv1 protocol.
I would recommend updating that device if possible in the upcoming new year.

My device its a TP Link Archer C5 1200, I think thats, are not very old...
http://www.tp-link.es/products/details/c...er-C5.html

I can't change this device for other more newer, this device work very fine and good, and are not very older.
The first firmware for this device are of year 2014 (only 3 years...).

What protocol need for works with news firmwares?

[leszek]

What protocol need for works with news firmwares?

Samba v3 is the newest I guess.

Perhaps you can configure it within the routers firmware. If not you have to use then the legacy v1 mode and mount manually.
I don't recommend using /etc/fstab as it could delay the boot when the network isn't available.
If you only need it occasionally you could just simply use the file manager dolphin and its smb:// protocol implementation and save it as a link in the sidebar of dolphin. Of course it is not "real" mounting so only KDE or more specifically KIO capable applications can access the files directly.

[wonder]

Samba v3 is the newest I guess.

I question this because, in the past, I need was contact with tp link support and have a great support. This router is not very old and for this, its strange that, the newest kernels not have this protocol...but I go to writte to tp link for if have some solution.
I can writte dd-wrt firmware and I'm sure that have this new protocol...but I like very much like work original firmware.

Perhaps you can configure it within the routers firmware. If not you have to use then the legacy v1 mode and mount manually.

Legacy v1 are the old 4.12.x kernel?

I don't recommend using /etc/fstab as it could delay the boot when the network isn't available.

True, I don't think in this...

If you only need it occasionally you could just simply use the file manager dolphin and its smb:// protocol implementation and save it as a link in the sidebar of dolphin. Of course it is not "real" mounting so only KDE or more specifically KIO capable applications can access the files directly.

Yes, I only need it occasionally.
And I configured this like you indicate in the past, in dolphin address I type: wmb://192.168.0.1/folder1 and enter well but...
I have configured dolphin for view remote previews, and always that access to my shared folder in my router with dolphin (like indicate now, link in the sidebar dolphin) need recreate this previews and it takes a lot.
If I access by the applicaton Network of home folder (the application I was start this thread) its fantastic, all everything very fast and the previews are seen just open dolphin.
For this reason I thought about mounting it on the fstab, in case this circumstance was solved.

I hope to have explained myself well

Thanks and regards!