Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.ubuntu    |    I preferred Xubuntu, seemed a bit faster    |    134,474 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 133,893 of 134,474    |
|    Paul to pinnerite    |
|    Re: Revisiting a mount statement    |
|    15 Jun 24 19:44:38    |
      XPost: alt.os.linux.mint, alt.os.linux.mageia       From: nospam@needed.invalid              On 6/15/2024 1:23 PM, pinnerite wrote:       > This is a summary of where I amm now.       >       > The share section in smb.conf on 192.168.1.100       >       > [data]       > comment = data       > path = /home/Data       > valid users = alan       > admin users = alan       > read only = No       >       > The target drive is 192.168.1.4       > I am trying to mount it on /spare/albury/Data.       >       > This is the mount command:       >       > sudo mount -t cifs //192.168.1.4/data/ /spare/albury/Data --verbose -o       > rw,noperm,username=alan,password=conte55a,domain=ASANDCO,vers=1.0,uid=alan       >       > The above should all be one line. It returns:       >       > mount error(6): No such device or address       >       > It is unclear which device or address.       >       > I have read through the man page for cifs. That added nothing to what I       already knew.       >       > $ smbclient -L //192.168.1.100 alan ## Displays all the shares correctly       >       > I cannot think of anything else to try. :(       >       >       >       > Linux Mint 21.3 kernel version 5.15.0-112-generic Cinnamon 6.0.4       > AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 1TB SSD, 2TB Barracuda       >              I tested here on LM213TST and it worked.              Note that in my case, it did not accept the passage of an inline password,       and insisted I type the password into the terminal. This could have       consequences       if buried in a script, such as you might be doing. I would recommend switching       the syntax, to the syntax that uses a file containing USER and PASS       information.              But just for the sake of showing, "something works", which is ultra-important       with SAMBA issues, here goes...              bullwinkle@LM213TST:~$ sudo mkdir /mnt/sharemount              bullwinkle@LM213TST:~$ sudo mount -t cifs //192.168.2.102/ramdrive       /mnt/sharemount --verbose -o rw,noperm,username=bullwinkle,domai       =WORKGROUP,vers=1.0,uid=bullwinkle               Password for bullwinkle@//192.168.2.102/ramdrive:        mount.cifs kernel mount options: ip=192.168.2.102,unc=\\192.1       8.2.102\ramdrive,noperm,vers=1.0,uid=1000,user=bullwinkle,domain       WORKGROUP,pass=ZZZZZ              Listing the contents of /mnt/sharemount now, contained the remote content.              bullwinkle@LM213TST:~$ sudo umount /mnt/sharemount # clean up later              I see two friction-points, considering yours used to work before.              1) Your workgroup details changed or are different on the two machines.        Check the declaration in /etc/samba/smb.conf              2) The password behavior I observed, needs to be corrected.        Try passing credentials by indirection (use the file with the USER and PASS       info in it).        It's like it was slapping my fingers.               I passed this:               username=bullwinkle,password=something               and the response I get is               Enter the password for bullwinkle, you twit              Which means it is warning me of the security implications of putting       the password in the script. The perms on the credential file can be       600, to make the thing feel better about itself.               Paul              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca