phd21 wrote: ⤴Mon Sep 30, 2019 9:20 pm
Hi fattage,
I just read your post and the good replies to it. Here are my thoughts on this as well.
It would help to know more about your system setup. If you run "
inxi -Fxzd" and "
lsusb" from the console terminal prompt, highlight the results, copy and paste them back here, that should provide enough information.
Can you access your drive connected to your router using this samba address in your file manager?
smb://192.168.50.1
Recent posts:
4.15 and the SMB bug
viewtopic.php?f=61&t=302142
Samba Networking and Linux firewall questions <Solved> - Linux Mint Forums
viewtopic.php?f=157&t=302266
Hope this helps ...
I will get that information back as soon as I get home this evening. I was able to open the drive using file explorer and smb://192.168.50.1
altair4 wrote: ⤴Tue Oct 01, 2019 6:43 am
There's a bunch of things wrong with your post:
[1] Incorrect syntax in your fstab declaration.
You can't mount a server. You can only mount a share on that server. So your line should look something like this:
//192.168.50.1/SHARE /media/SHARE cifs credentials=/home/USER/.smbcredentials,uid=1000 0 0
Replace SHARE with whatever the share name is in the router.
[2] Incorrect syntax in your manual mount declaration.
Same problem as above + you didn't specity the type of mount so the line should look like this:
sudo mount -t cifs //192.168.50.1/SHARE /media/SHARE -o username=USER
[3] Editing smb.conf may or may not have an affect when accessing the share from the file manager but it will have no affect on a cifs mount since mount.cifs does not know smb.conf exists.
Note1: mount.cifs in the Linux kernel you are using will attempt to connect to a server using SMBv2.1 up to SMBv3.11. If the update to your router only uses SMBv2 but not SMBv2.1 that may be a problem.
I would suggest doing a series of manual mounts to determine the best way to connect:
sudo mount -t cifs //192.168.50.1/SHARE /media/SHARE -o username=USER,vers=2.0
sudo mount -t cifs //192.168.50.1/SHARE /media/SHARE -o username=USER,vers=1.0
Note2: Keep in mind I'm trying to mount the entire drive. It works fine in windows.
No it doesn't. The equivalent of a cifs mount in Windows is a "mapped network drive mount" and you can't mount an entire server in Windows either:
WinMap.png
Note3: Maybe it's just me but that ip address just doesn't look right. Are your sure it's not 192.168.1.50 or better yet 192.168.1.1 ?
So on windows I am able to open the drive just by putting \\192.168.50.1 or \\(routername) or just by opening network and it shows up as available computer kind of like my laptop does just as my router name. So I thought it should work similarly on here.
Now my router gives the path as "//192.168.50.1/WD Elements 25A2/Elements" now it gives the option to remove the drive name in the share which I selected yes which I think removes the elements folder? It also give the option to have it work like a WINS server which is select as yes also "force as Master Browser", not sure what that is, is off
I'm sorry but I am a newish to linux, I couldn't find out how to do path quotes. for example
Code: Select all
sudo mount -t cifs "//192.168.50.1/WD Elements 25A2" /media/SHARE
I do have further folders after elements like Movies, music, backup but Ideally I want to be able to see all of those at once.
192.168.50.1 is correct, I thought it was odd too at first but apparently ASUS changed their default IP.
I will attempt those examples you provided, again not sure what folder to put after the IP I think is part problem.
Spearmint2 wrote: ⤴Mon Sep 30, 2019 8:28 pm
Open Disks program, have it install a line for that partition into the fstab file.
I will take a look at that.