From: lew.pitcher@digitalfreehold.ca   
      
   On Sat, 14 Sep 2024 16:06:18 +0200, alex wrote:   
      
   > Il 14/09/24 14:41, Carlos E.R. ha scritto:   
   >>   
   >> That was the error message you got.   
   >>   
   >> //HOST/public /mnt/public cifs   
   >> noauto,x-systemd.automount,_netdev,x-systemd.idle-timeout=300   
   guest,rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0   
   >>   
   >> + ls /mnt/public/   
   >> ls: cannot access '/mnt/public/': No such device   
   >>   
   >> Means that the problem was with "//HOST/public", not "/mnt/public".   
   >>   
   >   
   > I don't understand where you're getting at but that's okay   
      
   The   
     "No such device"   
   response seems to indicate that system can't communicate to the CIFS   
   networked file system that you specified in the mount parameters.   
      
   For CIFS, this can occur under a number of different conditions ranging   
   from basic network communications problems (such as routing, packet loss,   
   firewall intervention, etc.) through protocol issues (incompatable CIFS   
   version numbers, etc.) through to CIFS configuration errors (wrong   
   CIFS username or password, no server permissions, etc.)   
      
   Next step would be to check logs on both the linux client (where you   
   mount the CIFS filesystem to), and the CIFS server (that hosts the   
   files) to see if there are any details as to /why/ the CIFS automount   
   failed.   
      
   --   
   Lew Pitcher   
   "In Skills We Trust"   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)