Page 1 of 5 123 ... LastLast
Results 1 to 10 of 42

Thread: Recently unable to mount Windows 2012 Server network drives

  1. #1
    Join Date
    Mar 2018
    Beans
    55

    Question Recently unable to mount Windows 2012 Server network drives

    Up until about 7-10 days ago my fstab file in Ubuntu 18.04 was able to mount file shares from a windows 2012 Server without any issues. Now the shares no longer mount; I get the error
    Code:
    mount error(5): Input/output error.


    Interestingly enough, there are other shares being mapped in the same file from a Windows 2016 Server without any issues.


    I've confirmed that the windows account is not locked out; still experienced the same issue. I also tried mounting the drives with a different account and same behaviour. I am specifying
    Code:
    vers=2.1
    in the fstab line.


    Has anyone seen this issue before? Where am I going wrong?

    Thanks!

  2. #2
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,450
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Recently unable to mount Windows 2012 Server network drives

    I haven't followed the topic but check which smb version is used on both ends and its compatibility. OS updates (especially on windows side) can limit which smb version can be used or blocked.

    That might be a reason why it suddenly stops working.

    And regardless if lower versions are supported, try to go as high as possible that could work in your scenario. I guess it offers more security and better result (in theory)...

    PS. It looks obvious but people sometimes forget it. What do the logs say on both sides? There should be something in the logs if mounting is failing...
    Last edited by darkod; August 30th, 2020 at 05:53 PM.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  3. #3
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    21,650
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Recently unable to mount Windows 2012 Server network drives

    Please show the full line, if you'd like help and the outout from lsb_release -a, so we know what release you are running.

    How often is the ubuntu system patched? Some defaults changed for samba about 6 months ago which broke connections to older Windows systems. There are threads here about that. Also, MSFT has been changing some of their defaults for network shares the last year. 2 moving targets are hard to hit when there isn't any coordination between the teams.

  4. #4
    Join Date
    Mar 2018
    Beans
    55

    Re: Recently unable to mount Windows 2012 Server network drives

    I've tried specifying version 3.0 in the config with the same issue. Completely with you on using the highest supported version.

    Where would I be looking for the Ubuntu logs? Windows logs don't really show anything.

  5. #5
    Join Date
    Mar 2018
    Beans
    55

    Re: Recently unable to mount Windows 2012 Server network drives

    Sorry about that; didn't know to post the full release info.


    That info is:
    USER@PServer:~$ lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 18.04.5 LTS
    Release: 18.04
    Codename: bionic

    This system is patched (roughly) monthly.

    Understandable about the two teams; what's weird is that nothing on my end has changed (other than patching both systems) and the Server 2016 still continues to work successfully (fingers crossed).

  6. #6
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,450
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Recently unable to mount Windows 2012 Server network drives

    I suggest you try the mount command in terminal with high verbocity (something like -vvv) to show you more details as it tries to mount.

    Also comparing Windows 2012 and 2016 does not always mean things should work identically. Patching is precisely what can "close down" what they consider vulnerabilties and they are not always identical across different OS versions.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  7. #7
    Join Date
    Mar 2018
    Beans
    55

    Re: Recently unable to mount Windows 2012 Server network drives

    Ok, can you point me in the right direction as to what command I should be using (please)?

    Thanks!

  8. #8
    Join Date
    Dec 2009
    Beans
    6,449

    Re: Recently unable to mount Windows 2012 Server network drives

    Quote Originally Posted by linuxnoob87 View Post
    Ok, can you point me in the right direction as to what command I should be using (please)?

    Thanks!
    Code:
    sudo mount -t cifs --verbose //server/share /mountpoint -o comma,separated,list,of,options
    Side note: The version of the Linux kernel in Ubuntu 18 automatically negotiates with the server for the best smb dialect to use between SMB2.1 and SMB3.X so the only reason you would need to specify a "vers" in the options list would be if the server can only speak SMB2.0 or less.

  9. #9
    Join Date
    Mar 2018
    Beans
    55

    Re: Recently unable to mount Windows 2012 Server network drives

    Code:
    user@PServer:/mnt$ sudo mount -t cifs --verbose //HServer/HPics /mnt/HPhotos -o user=(Username),password=(Password)
    mount.cifs kernel mount options: ip=172.16.249.101,unc=\\HServer\HPics,user=(Username),pass=********
    mount error(5): Input/output error
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  10. #10
    Join Date
    Sep 2020
    Beans
    4

    Re: Recently unable to mount Windows 2012 Server network drives

    Quote Originally Posted by linuxnoob87 View Post
    Code:
    user@PServer:/mnt$ sudo mount -t cifs --verbose //HServer/HPics /mnt/HPhotos -o user=(Username),password=(Password)
    mount.cifs kernel mount options: ip=172.16.249.101,unc=\\HServer\HPics,user=(Username),pass=********
    mount error(5): Input/output error
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
    I am getting the same error message (different path, mountpoint and credentials, of course), dmesg gives me

    Code:
    [  137.556264] Status code returned 0xc000018d STATUS_TRUSTED_RELATIONSHIP_FAILURE
    [  137.556274] CIFS VFS: Send error in SessSetup = -5
    [  137.556330] CIFS VFS: cifs_mount failed w/return code = -5
    I tried several different combinations of the mount options vers= and sec=, none of those attempts have worked so far.
    Connecting to the shares using smbclient works from the same machine using the same credentials.

    The last time I can confirm the mountpoints were working, the syslog entries

    Code:
    Status code returned 0xc000018d STATUS_TRUSTED_RELATIONSHIP_FAILURE
    CIFS VFS: Send error in SessSetup = -5
    were already occurring regularly, so I assume the only syslog entry definitely related to the problem must be

    Code:
    CIFS VFS: cifs_mount failed w/return code = -5
    which started to appear after a reboot following the installation these updates:

    Code:
    Start-Date: 2020-08-28  06:47:46
    [...]
    Upgrade: libnss3:amd64 (2:3.35-2ubuntu2.11, 2:3.35-2ubuntu2.12)
    [...]
    Start-Date: 2020-08-31  16:03:45
    Upgrade: libpam0g:amd64 (1.1.8-3.6ubuntu2.18.04.1, 1.1.8-3.6ubuntu2.18.04.2), libpam-modules:amd64 (1.1.8-3.6ubuntu2.18.04.1, 1.1.8-3.6ubuntu2.18.04.2), libsystemd0:amd64 (237-3ubuntu10.41, 237-3ubuntu10.42), libkmod2:amd64 (24-1ubuntu3.4, 24-1ubuntu3.5), udev:amd64 (237-3ubuntu10.41, 237-3ubuntu10.42), language-pack-de:amd64 (1:18.04+20190117, 1:18.04+20200702), libpam-runtime:amd64 (1.1.8-3.6ubuntu2.18.04.1, 1.1.8-3.6ubuntu2.18.04.2), kmod:amd64 (24-1ubuntu3.4, 24-1ubuntu3.5), libudev1:amd64 (237-3ubuntu10.41, 237-3ubuntu10.42), apport:amd64 (2.20.9-0ubuntu7.16, 2.20.9-0ubuntu7.17), python3-distupgrade:amd64 (1:18.04.37, 1:18.04.38), ubuntu-release-upgrader-core:amd64 (1:18.04.37, 1:18.04.38), python3-apport:amd64 (2.20.9-0ubuntu7.16, 2.20.9-0ubuntu7.17), systemd-sysv:amd64 (237-3ubuntu10.41, 237-3ubuntu10.42), libpam-systemd:amd64 (237-3ubuntu10.41, 237-3ubuntu10.42), systemd:amd64 (237-3ubuntu10.41, 237-3ubuntu10.42), libpam-modules-bin:amd64 (1.1.8-3.6ubuntu2.18.04.1, 1.1.8-3.6ubuntu2.18.04.2), iproute2:amd64 (4.15.0-2ubuntu1.1, 4.15.0-2ubuntu1.2), bcache-tools:amd64 (1.0.8-2build1, 1.0.8-2ubuntu0.18.04.1), libnss-systemd:amd64 (237-3ubuntu10.41, 237-3ubuntu10.42), python3-problem-report:amd64 (2.20.9-0ubuntu7.16, 2.20.9-0ubuntu7.17), base-files:amd64 (10.1ubuntu2.8, 10.1ubuntu2.9)

Page 1 of 5 123 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •