Cifs Unable to Mount Share

Gotit · 2021-11-26 20:44:43

Hi - I recently re-installed Arch and now I can't mount a share with CIFS. Before re-installing, I had this line in
fstab:

//share-IP-address/netdrive/Files /mnt/Netdrive-Files cifs guest,vers=1.0,x-systemd.device-timeout=30,_netdev,iocharset=utf8,x-systemd.automount,sec=ntlm 0 0

However, that no longer mounts the share and when I run mount:

$ sudo mount -a
mount error(22): Invalid argument

I found the offending argument to be:

sec=ntlm

but, according to the manual, that's valid. So, I removed it and then get:

$ sudo mount -a
Retrying with upper case share name
mount error(6): No such device or address

When I try mounting the sare from CLI:

$ sudo mount.cifs //share-ip-address/netdrive/Files /mnt/Netdrive-Files vers=1.0
Password for root@//share-ip-address/netdrive/Files: 
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down

tried with vers=2.0

$ sudo mount.cifs //share-ip-address/netdrive/Files /mnt/Netdrive-Files vers=2.0
Password for root@//share-ip-address/netdrive/Files: 
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Tried as "guest" and get a different message:

$ sudo mount.cifs guest //1share-ip-address/netdrive/Files /mnt/Netdrive-Files vers=1.0
Couldn't chdir to //share-ip-address/netdrive/Files: No such file or directory

SMB is enabled and I can mount the share by surfing to it in Thunar Browse Networks.

$ systemctl -t service -a | grep Samba
  nmb.service                                                                               loaded    active   running Samba NMB Daemon
  smb.service                                                                               loaded    active   running Samba SMB Daemon
  winbind.service                                                                           loaded    inactive dead    Samba Winbind Daemon

smbclient can see the share:

$ smbclient -NL //share-ip-address/netdrive

	Sharename       Type      Comment
	---------       ----      -------
	NetDrive        Disk      
	IPC$            IPC       IPC Service (Samba 3.0.37-(Optimized by Tuxera Inc, 3015.11.5.2_1))
Reconnecting with SMB1 for workgroup listing.

	Server               Comment
	---------            -------
	VIRUS-SANDBOX-1      Samba 3.0.28a

	Workgroup            Master
	---------            -------
	HOMESHARES           DESKTOP
	WORKGROUP            VIRUS-SANDBOX-1

related packages installed

samba
cifs-utils
keyutils

I checked journalctl, but no related messages

I feel like I'm missing something so simple...

seth · 2021-11-26 21:38:39

"sudo mount.cifs //share-ip-address/netdrive/Files /mnt/Netdrive-Files -o vers=1.0"
Linux 5.15.x? Does it work w/ the lts kernel?

Gotit · 2021-11-26 21:45:10

Hi Seth - the option indicator doesn't seem to make a difference

$ sudo mount.cifs guest //share-ip-address/netdrive/Files /mnt/Netdrive-Files -o vers=1.0
Couldn't chdir to //share-ip-address/netdrive/Files: No such file or directory

Yes on linux 5.15.4

Last edited by Gotit (2021-11-26 21:48:26)

seth · 2021-11-26 21:53:19

Not as "guest".

Do you control the smb server? Can you check its logs?

Gotit · 2021-11-26 22:30:05

w/o guest:

$ sudo mount.cifs //share-ip-address/netdrive/Files /mnt/Netdrive-Files -o vers=1.0
Password for root@//share-ip-address/netdrive/Files: 
Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Log entries:

$ journalctl -kS 17:25
Nov 26 17:25:29 Asus405 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
Nov 26 17:25:29 Asus405 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
Nov 26 17:25:29 Asus405 kernel: CIFS: Attempting to mount \\share-ip-address\netdrive
Nov 26 17:25:29 Asus405 kernel: CIFS: VFS: \\share-ip-address failed to connect to IPC (rc=-6)
Nov 26 17:25:29 Asus405 kernel: CIFS: VFS: cifs_mount failed w/return code = -6
Nov 26 17:25:29 Asus405 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
Nov 26 17:25:29 Asus405 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
Nov 26 17:25:29 Asus405 kernel: CIFS: Attempting to mount \\share-ip-address\NETDRIVE
Nov 26 17:25:29 Asus405 kernel: CIFS: VFS: \\share-ip-address failed to connect to IPC (rc=-6)
Nov 26 17:25:30 Asus405 kernel: CIFS: VFS: cifs_mount failed w/return code = -6

seth · 2021-11-27 08:25:09

You're not issueing any credentials, but the original fstab line seems to have been for a guest config anyway

//share-IP-address/netdrive/Files /mnt/Netdrive-Files cifs guest,vers=1.0,x-systemd.device-timeout=30,_netdev,iocharset=utf8,x-systemd.automount,sec=ntlm 0 0

Sanity check:

stat /mnt/Netdrive-Files

If that's not your "D'oohhh!" moment, try the lts kernel and with "logs" I actually meant the ones of the CIFS server (and it's config, because if you know what you want to attach to and/or why it won't let you, it's easier to say what to do than just poking around until it works ;-)

Gotit · 2021-11-29 17:23:24

OK, so it works on LTS via fstab, (big thanks for that suggestion) but not from cli.
Here's a comparison between LTS and 5.15.5

On LTS wifi
With mount commented in fstab:

#//share-ip-address/netdrive/Files /mnt/Netdrive-Files cifs guest,vers=1.0,uid=1002,gid=1002,forceuid,forcegid,x-systemd.device-timeout=30,_netdev,iocharset=utf8,x-systemd.automount,sec=ntlm 0 0

Try mounting via cli:

$ sudo mount.cifs guest //share-ip-address/netdrive/Files /home/gotit/Netdrive-Files -o vers=1.0
Couldn't chdir to //share-ip-address/netdrive/Files: No such file or directory

Mountpoint status:

stat Netdrive-Files
  File: Netdrive-Files
  Size: 4096      	Blocks: 8          IO Block: 4096   directory
Device: 8,3	Inode: 1713640     Links: 2
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-11-28 15:36:27.214199993 -0500
Modify: 2021-11-24 12:32:38.318719807 -0500
Change: 2021-11-28 15:36:27.207533327 -0500
 Birth: 2021-11-24 12:32:38.318719807 -0500

With mount uncommented in fstab:

$ sudo mount -av
/                        : ignored
/efi                     : already mounted
/home                    : already mounted
none                     : ignored
mount.cifs kernel mount options: ip=share-ip-address,unc=\\share-ip-address\netdrive,vers=1.0,forceuid,forcegid,iocharset=utf8,sec=ntlm,uid=1002,gid=1002,user=,prefixpath=Files,pass=********
/mnt/Netdrive-Files      : successfully mounted

Kernel 5.15.5
With mount commented in fstab
Try mounting via cli:

$ sudo mount.cifs guest //share-ip-address/netdrive/Files /home/gotit/Netdrive-Files -o vers=1.0
Couldn't chdir to //share-ip-address/netdrive/Files: No such file or directory

Mountpoint status:

$ stat Netdrive-Files
  File: Netdrive-Files
  Size: 4096      	Blocks: 8          IO Block: 4096   directory
Device: 8,3	Inode: 1713640     Links: 2
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-11-28 15:36:27.214199993 -0500
Modify: 2021-11-24 12:32:38.318719807 -0500
Change: 2021-11-28 15:36:27.207533327 -0500
 Birth: 2021-11-24 12:32:38.318719807 -0500

With mount uncommented in fstab:

$ sudo mount -av
/                        : ignored
/efi                     : already mounted
/home                    : already mounted
none                     : ignored
mount.cifs kernel mount options: ip=share-ip-address,unc=\\share-ip-address\netdrive,vers=1.0,forceuid,forcegid,iocharset=utf8,sec=ntlm,uid=1002,gid=1002,user=,prefixpath=Files,pass=********
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Earlier, I found sec=ntlm to be the invalid argument, and removing it sends me down another rat hole as noted in an earlier post.

seth wrote:

"logs" I actually meant the ones of the CIFS server

Not sure where the cifs logs are, I didn't find reference to them in my searches. But if they are the smbd logs in /var/log/samba, there's nothing of intrest in them

[2021/11/28 18:17:59.134727,  0] ../../source3/smbd/server.c:1738(main)
  smbd version 4.15.2 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2021
[2021/11/28 18:30:04.335355,  0] ../../source3/smbd/server.c:1738(main)
  smbd version 4.15.2 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2021
[2021/11/28 18:31:42.501793,  0] ../../source3/smbd/server.c:1738(main)
  smbd version 4.15.2 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2021
[2021/11/29 11:12:22.634510,  0] ../../source3/smbd/server.c:1738(main)
  smbd version 4.15.2 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2021
[2021/11/29 11:37:29.714062,  0] ../../source3/smbd/server.c:1738(main)
  smbd version 4.15.2 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2021

nmdb not much help either:

[2021/11/28 18:30:51.975119,  0] ../../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2021/11/29 11:11:38.482587,  0] ../../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2021/11/29 11:36:49.848997,  0] ../../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...

seth wrote:

and it's config

Not sure about cifs config, is this the samba.config?

$ testparm -s
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed

Server role: ROLE_STANDALONE

# Global parameters
[global]
	client max protocol = SMB3
	client min protocol = NT1
	dns proxy = No
	log file = /var/log/samba/%m.log
	map to guest = Bad User
	max log size = 100
	name resolve order = bcast host
	obey pam restrictions = Yes
	pam password change = Yes
	security = USER
	server role = standalone server
	server string = %h server (Samba ASUS)
	unix password sync = Yes
	usershare allow guests = Yes
	usershare max shares = 100
	usershare owner only = No
	usershare path = /var/lib/samba/usershare
	workgroup = HOMESHARES
	idmap config * : backend = tdb
	force user = gotit

duing · 2021-11-29 18:27:23

Leave defaults and add only options you know. So guest is an option. Try

sudo mount.cifs -o guest //1share-ip-address/netdrive/Files /mnt/Netdrive-Files

Does it work? Then you don't need the option vers=1.0 anymore.

Gotit · 2021-11-29 19:08:06

Changes the error message a bit:

$ sudo mount.cifs -o guest //share-ip-address/netdrive/Files /home/steve/Netdrive-Files
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Also tried:

$ sudo mount.cifs -o guest, vers=1.0 //share-ip-address/netdrive/Files /home/steve/Netdrive-Files
Couldn't chdir to //share-ip-address/netdrive/Files: No such file or directory

duing · 2021-11-29 22:07:39

use

mount -t cifs -o guest -o vers=1.0

or

mount -t cifs -o guest,vers=1.0

Later you will add uid=$UID but not user=empty. Btw, have a look into the comprehensive manual.

man mount
man mount.cifs

Last edited by duing (2021-11-29 23:07:50)

Gotit · 2021-11-29 22:57:02

@duing
Both the above commands give the same error:

$ sudo mount -t cifs -o guest -o vers=1.0 //192.168.1.1/netdrive/Files /home/steve/Netdrive-Files
Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

$ sudo mount -t cifs -o guest,vers=1.0 //192.168.1.1/netdrive/Files /home/steve/Netdrive-Files
Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

As for:

duing wrote:

Btw, have a look into the comprehensive manual.

Almost memorized it by now

Odd how I can at least get it to mount via fstab on LTS, but 5.15.5 gives heartburn no matter what I do.

duing · 2021-11-30 00:19:18

Thus it works with sec=ntlm on LTS? According to my manual page this is the default, but may change with kernel version. Also I don't know how it is involved for package signing as guest.

Of course your network is up, the server is up and reachable

ping $IP

and the service is running :\

Last edited by duing (2021-11-30 01:11:48)

Gotit · 2021-11-30 01:56:02

Network is definitely up.

ping share-ip-address
PING share-ip-address (share-ip-address) 56(84) bytes of data.
64 bytes from share-ip-address: icmp_seq=1 ttl=64 time=0.702 ms
64 bytes from share-ip-address: icmp_seq=2 ttl=64 time=0.946 ms
64 bytes from share-ip-address: icmp_seq=3 ttl=64 time=0.749 ms
64 bytes from share-ip-address: icmp_seq=4 ttl=64 time=0.979 ms
64 bytes from share-ip-address: icmp_seq=5 ttl=64 time=1.07 ms

Works on LTS but not 5.15.5
I even tried on ethernet and no difference.

Last edited by Gotit (2021-11-30 01:58:01)

seth · 2021-11-30 08:38:13

"sudo mount.cifs guest //share-ip-address/netdrive/Files /home/gotit/Netdrive-Files -o vers=1.0" is wrong syntax,

mount.cifs --help

Usage:  mount.cifs <remotetarget> <dir> -o <options>

The fstab mount is equivalent to

sudo mount.cifs //share-ip-address/netdrive/Files /home/gotit/Netdrive-Files -o guest,vers=1.0,uid=1002,gid=1002,forceuid,forcegid,x-systemd.device-timeout=30,_netdev,iocharset=utf8,x-systemd.automount,sec=ntlm

Scratch systemd options

sudo mount.cifs //share-ip-address/netdrive/Files /home/gotit/Netdrive-Files -o guest,vers=1.0,uid=1002,gid=1002,forceuid,forcegid,iocharset=utf8,sec=ntlm

logs in /var/log/samba, there's nothing of intrest in them

Raise the log level and restart the server: https://wiki.samba.org/index.php/Settin … _Log_Level

Earlier, I found sec=ntlm to be the invalid argument, and removing it sends me down another rat hole as noted in an earlier post.

https://www.samba.org/samba/history/samba-4.5.0.html
https://git.kernel.org/pub/scm/linux/ke … 68f61a179c

The smb server version is … err… geriatric.
You could try
"sec=krb5" or "sec=ntlmv2" instead, see https://man.archlinux.org/man/extra/cif … .cifs.8.en for the full list.

Gotit · 2021-11-30 21:32:34

So, I set log level = 7, restarted smb and nmb services and ran:

$ sudo mount.cifs //share-ip-address/netdrive/Files /home/gotit/Netdrive-Files -o guest,vers=1.0,uid=1002,gid=1002,forceuid,forcegid,iocharset=utf8,sec=ntlm
Couldn't chdir to /home/gotit/Netdrive-Files: No such file or directory

smdb.log has no entries for the time period, but nmdb.log has:

[2021/11/30 16:26:05.642402,  4] ../../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet)
  find_workgroup_on_subnet: workgroup search for HOMESHARES on subnet workgroup-ip-address: found.
[2021/11/30 16:26:05.642537,  4] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
  dump_workgroups()
   dump workgroup on subnet   workgroup-ip-address: netmask=  255.255.255.0:
  	HOMESHARES(1) current master browser = DESKTOP
  		ASUS405 40819a03 (Asus405 server (Samba ASUS))
  		DESKTOP 40849a03 (Desktop server (Samba, Ubuntu))
[2021/11/30 16:26:15.652774,  4] ../../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet)
  find_workgroup_on_subnet: workgroup search for HOMESHARES on subnet workgroup-ip-address: found.
[2021/11/30 16:26:15.652863,  4] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
  dump_workgroups()
   dump workgroup on subnet   workgroup-ip-address: netmask=  255.255.255.0:
  	HOMESHARES(1) current master browser = DESKTOP
  		ASUS405 40819a03 (Asus405 server (Samba ASUS))
  		DESKTOP 40849a03 (Desktop server (Samba, Ubuntu))
[2021/11/30 16:26:25.662532,  4] ../../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet)
  find_workgroup_on_subnet: workgroup search for HOMESHARES on subnet workgroup-ip-address: found.
[2021/11/30 16:26:25.662712,  4] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
  dump_workgroups()
   dump workgroup on subnet   workgroup-ip-address: netmask=  255.255.255.0:
  	HOMESHARES(1) current master browser = DESKTOP
  		ASUS405 40819a03 (Asus405 server (Samba ASUS))
  		DESKTOP 40849a03 (Desktop server (Samba, Ubuntu))
[2021/11/30 16:26:35.673511,  4] ../../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet)
  find_workgroup_on_subnet: workgroup search for HOMESHARES on subnet workgroup-ip-address: found.
[2021/11/30 16:26:35.673652,  4] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
  dump_workgroups()
   dump workgroup on subnet   workgroup-ip-address: netmask=  255.255.255.0:
  	HOMESHARES(1) current master browser = DESKTOP
  		ASUS405 40819a03 (Asus405 server (Samba ASUS))
  		DESKTOP 40849a03 (Desktop server (Samba, Ubuntu))

sadly nothing stands out to me here.

seth · 2021-11-30 21:46:23

'key, guess I kinda buried this:

seth wrote:

Earlier, I found sec=ntlm to be the invalid argument, and removing it sends me down another rat hole as noted in an earlier post.
https://www.samba.org/samba/history/samba-4.5.0.html
https://git.kernel.org/pub/scm/linux/ke … 68f61a179c
The smb server version is … err… geriatric.
You could try
"sec=krb5" or "sec=ntlmv2" instead, see https://man.archlinux.org/man/extra/cif … .cifs.8.en for the full list.

The samba server is tooold™ and doesn't speak ntlmssp, but the client (archlinux kernl cifs implmentation) has scratched that protocol.
=> You'll have to find a protocol that both speak or update the server samba.

Last edited by seth (2021-11-30 21:46:38)

Gotit · 2021-11-30 23:29:29

I changed sec= if fstab and all errored out:
none

$ sudo mount -a
Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

krb5

$ sudo mount -a
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

krb5i

$ sudo mount -a
mount error(524): Unknown error 524
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

ntlmi

$ sudo mount -a
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

ntlmv2

$ sudo mount -a
Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

ntlmv2i

sudo mount -a
mount error(524): Unknown error 524
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

ntlmssp

$ sudo mount -a
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

ntlmsspi

$ sudo mount -a
mount error(524): Unknown error 524
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Not seeing any errors in nmdb.log.
Can I really be the only person where cifs works with LTS and not 5.15.x?

seth · 2021-12-01 05:08:11

krb5

$ sudo mount -a
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Omit "vers=1.0", client and server support newer protocols.

Can I really be the only person where cifs works with LTS and not 5.15.x?

1. Wait until ubuntu hits 5.15
2.

seth wrote:

or update the server samba

Gotit · 2021-12-01 13:25:41

seth wrote:

Omit "vers=1.0", client and server support newer protocols.

Omitted:

$ sudo mount -a
Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

seth wrote:

...or update the server samba.

$ samba -V
Version 4.15.2

Now I'm thinking you mean update on the system that is sharing the device... Hmmm, don't think I can do that.

seth wrote:

Wait until ubuntu hits 5.15

Always nice to be a pioneer

seth · 2021-12-01 13:32:07

Now I'm thinking you mean update on the system that is sharing the device...

Yup. Is the config you posted from the server or the client?

Gotit · 2021-12-01 16:14:36

seth wrote:

Is the config you posted from the server or the client?

My laptop, the client.
Guess I'm bound to LTS for a while, guess that's why they have it!

seth · 2021-12-01 17:42:15

I was more curious about the server config…
You need to resolve this if you can't update the server because at some point the LTS kernel will move to a version that doesn't have ntlm anymore either.

Gotit · 2021-12-01 23:37:32

seth wrote:

I was more curious about the server config…

Unfortunately, I don't have access to server config or version of samba.

seth · 2021-12-02 07:53:05

VIRUS-SANDBOX-1 Samba 3.0.28a

What is the actual device that runs this (maybe you can get an update or a telnet access)

Gotit · 2021-12-02 13:14:35

seth wrote:

What is the actual device that runs this...

Linksys Router. I was thinking of going to Fresh Tomato or OpenWRT but they don't support the model.
Guess I can ask Linksys for a firmware upgrade to support newer kernels.

Arch Linux

#1 2021-11-26 20:44:43

Cifs Unable to Mount Share

#2 2021-11-26 21:38:39

Re: Cifs Unable to Mount Share

#3 2021-11-26 21:45:10

Re: Cifs Unable to Mount Share

#4 2021-11-26 21:53:19

Re: Cifs Unable to Mount Share

#5 2021-11-26 22:30:05

Re: Cifs Unable to Mount Share

#6 2021-11-27 08:25:09

Re: Cifs Unable to Mount Share

#7 2021-11-29 17:23:24

Re: Cifs Unable to Mount Share

#8 2021-11-29 18:27:23

Re: Cifs Unable to Mount Share

#9 2021-11-29 19:08:06

Re: Cifs Unable to Mount Share

#10 2021-11-29 22:07:39

Re: Cifs Unable to Mount Share

#11 2021-11-29 22:57:02

Re: Cifs Unable to Mount Share

#12 2021-11-30 00:19:18

Re: Cifs Unable to Mount Share

#13 2021-11-30 01:56:02

Re: Cifs Unable to Mount Share

#14 2021-11-30 08:38:13

Re: Cifs Unable to Mount Share

#15 2021-11-30 21:32:34

Re: Cifs Unable to Mount Share

#16 2021-11-30 21:46:23

Re: Cifs Unable to Mount Share

#17 2021-11-30 23:29:29

Re: Cifs Unable to Mount Share

#18 2021-12-01 05:08:11

Re: Cifs Unable to Mount Share

#19 2021-12-01 13:25:41

Re: Cifs Unable to Mount Share

#20 2021-12-01 13:32:07

Re: Cifs Unable to Mount Share

#21 2021-12-01 16:14:36

Re: Cifs Unable to Mount Share

#22 2021-12-01 17:42:15

Re: Cifs Unable to Mount Share

#23 2021-12-01 23:37:32

Re: Cifs Unable to Mount Share

#24 2021-12-02 07:53:05

Re: Cifs Unable to Mount Share

#25 2021-12-02 13:14:35

Re: Cifs Unable to Mount Share

Board footer