Skip to main content
fixed grammar and formatting
Source Link
intika
  • 14.6k
  • 7
  • 46
  • 85

As intika has indicated in the comment you did not give us enough details.As intika has indicated in the comment you did not give us enough details.

SmbSMB protocol version

I presume you are not using smb1 as it is considered unsafe. Are
Are you using smb2 or smb3 to connect smbclient/mount.cifs?

There maybe NTMLNTLM security implications if you are using smb3 protocol, which could prevent you listing the directory.

Note: Youyou should check the log (event viewer) on the server not on the client, to see what is going on.

I think you may suffer from the dot smbv2 bug (when using mount). Which
Which in short is:

If smbv1 is disabled and you can't enable it for testing purposes you can enable smbSMB debugging by using:

As intika has indicated in the comment you did not give us enough details.

Smb protocol version

I presume you are not using smb1 as it is considered unsafe. Are you using smb2 or smb3 to connect smbclient/mount.cifs?

There maybe NTML security implications if you are using smb3 protocol, which could prevent you listing the directory.

Note: You should check the log (event viewer) on the server not on the client, to see what is going on.

I think you may suffer from the dot smbv2 bug (when using mount). Which in short is:

If smbv1 is disabled and you can't enable it for testing purposes you can enable smb debugging by using:

As intika has indicated in the comment you did not give us enough details.

SMB protocol version

I presume you are not using smb1 as it is considered unsafe.
Are you using smb2 or smb3 to connect smbclient/mount.cifs?

There maybe NTLM security implications if you are using smb3 protocol, which could prevent you listing the directory.

Note: you should check the log (event viewer) on the server not on the client, to see what is going on.

I think you may suffer from the dot smbv2 bug (when using mount).
Which in short is:

If smbv1 is disabled and you can't enable it for testing purposes you can enable SMB debugging by using:

Rollback to Revision 4
Source Link
intika
  • 14.6k
  • 7
  • 46
  • 85

I presume you are not using smb1 as it is considered unsafe. Are Are you using smb2 or smb3 to connect smbclient/mount.cifs?

Third option that comes into my mind would be to have more than 2 entries at the mount root. Those should start in a way that they should be before the entry(ies) you want to see.

I presume you are not using smb1 as it is considered unsafe. Are you using smb2 or smb3 to connect smbclient/mount.cifs?

Third option that comes into my mind would be to have more than 2 entries at the mount root. Those should start in a way that they should be before the entry you want to see.

I presume you are not using smb1 as it is considered unsafe. Are you using smb2 or smb3 to connect smbclient/mount.cifs?

Third option that comes into my mind would be to have more than 2 entries at the mount root. Those should start in a way that they should be before the entry(ies) you want to see.

deleted 6 characters in body
Source Link
intika
  • 14.6k
  • 7
  • 46
  • 85

I presume you are not using smb1 as it is considered unsafe. AreAre you using smb2 or smb3 to connect smbclient/mount.cifs?

Third option that comes into my mind would be to have more than 2 entries at the mount root. Those should start in a way that they should be before the entry(ies) you want to see.

I presume you are not using smb1 as it is considered unsafe. Are you using smb2 or smb3 to connect smbclient/mount.cifs?

Third option that comes into my mind would be to have more than 2 entries at the mount root. Those should start in a way that they should be before the entry(ies) you want to see.

I presume you are not using smb1 as it is considered unsafe. Are you using smb2 or smb3 to connect smbclient/mount.cifs?

Third option that comes into my mind would be to have more than 2 entries at the mount root. Those should start in a way that they should be before the entry you want to see.

added 2 characters in body
Source Link
Hauke Laging
  • 90.4k
  • 19
  • 130
  • 179
Loading
editing answer with possible solution
Source Link
tukan
  • 5.7k
  • 8
  • 20
Loading
rephrasing
Source Link
tukan
  • 5.7k
  • 8
  • 20
Loading
Source Link
tukan
  • 5.7k
  • 8
  • 20
Loading