![]() |
Accessing a NAS device - Sustaining Credentials - Printable Version +- Linux Lite Forums (https://www.linuxliteos.com/forums) +-- Forum: Hardware - Support (https://www.linuxliteos.com/forums/forumdisplay.php?fid=6) +--- Forum: Network (https://www.linuxliteos.com/forums/forumdisplay.php?fid=24) +--- Thread: Accessing a NAS device - Sustaining Credentials (/showthread.php?tid=6512) Pages:
1
2
|
Re: Accessing a NAS device - Sustaining Credentials - Valtam - 12-27-2019 Also, make sure there is 1 blank line at the end of the fstab file. Re: Accessing a NAS device - Sustaining Credentials - allen04084 - 12-27-2019 NAS specific cifs version https://askubuntu.com/questions/1032237/why-is-mount-cifs-not-working-in-fstab-any-more-after-upgrading-from-16-04-to-18 Re: Accessing a NAS device - Sustaining Credentials - Valtam - 12-27-2019 Will it not work without that entry? Sent from my Mobile phone using Tapatalk Re: Accessing a NAS device - Sustaining Credentials - allen04084 - 12-27-2019 without vers=1.0 I get "invalid arguement" when sudo mount -a Code: allen / etc sudo nano fstab Re: Accessing a NAS device - Sustaining Credentials - allen04084 - 12-27-2019 As mentioned previously, I CAN see the NAS share in Thunar now - BEFORE I reboot. Once I reboot, wireless net will not connect. Once I change fstab to the unmodified fstab, wireless connection returns after reboot. Re: Accessing a NAS device - Sustaining Credentials - allen04084 - 12-27-2019 Code: allen / etc cd /home/allen/tim Re: Accessing a NAS device - Sustaining Credentials - Valtam - 12-28-2019 A rare situation. I cannot find any information online about this specific situation. My gut tells me it's systemd related. Do a fresh reboot, then paste your dmesg contents here. /var/log/dmesg Re: Accessing a NAS device - Sustaining Credentials - Valtam - 12-28-2019 Source - https://forums.linuxmint.com/viewtopic.php?t=221115#p1161236 Try this format: Code: //192.168.0.1/tim /media/tim cifs username=smbuser,password=smbuserpw,uid=1000,noauto,user,vers=3.0 0 0 ' ** Make sure your mount point is under /media - this will trigger a udisks event that makes it work as I describe below.' |