Accessing smb v2 and v3 shares with ShareView

With v0.02, double-clicking on a file in the Filer seems to transfer it to the current ShareView directory rather than opening it!

v0.03 arriving shortly. In the mean time the download is back to v0.01.

I’ve tried a few variations, such as leaving the workgroup/domain parameter empty in users/txt and using the domain\username format for the user part, but still no luck so far.

v0.03 arriving shortly. In the mean time the download is back to v0.01.

New version available (v0.03) here.
Only change is it should no longer try to upload a file when double-clicked in the filer.

I know it’s still alpha, but I surely would like to understand why ShareView can’t contact my Windows11 PC. When I do a smb-share-enum smb://192.168.2.24/ command, I get the following error: Failed to connect to IPC$. Session setup failed with (0xc0000022) STATUS_ACCESS_DENIED, while the same command with the IP address of my NAS just works.

On the PC side, I’ve disabled SMBv1 support. When I re-enable it, I can share everything with LanMan, so I suppose that the sharing things shouldn’t be the problem, should they?

Sounds like when you had SMBv1 enabled it allowed guest access.

You just need a local user to log on with.

Then you can do,

smb-share-enum smb://username @192.168.2.24/

Then give access to that user for the required shares.

There’s another updated version (v0.04) available here.

New in this version,

Allows single file/folder deletes.
Some errors are now shown when connecting to a share fails.

smb-share-enum smb://username @192.168.2.24/

With a space after the username, I get a ‘Wrong URL format’ error, and without the space I get a “STATUS_LOGON_FAILURE”.

With a space after the username,

No space after username. I had to put it in otherwise the formatting on the forum went wrong.

STATUS_LOGIN_FAILURE means the password is incorrect in the user/txt file for that user.

STATUS_LOGIN_FAILURE means the password is incorrect in the user/txt file for that user.

It’s the same password (and the same user) that is used by LanMan. Apologise for being so annoying, but I’m wandering in the dark.

It’s the same password (and the same user) that is used by LanMan. Apologise for being so annoying, but I’m wandering in the dark.

Paul, on your Windows 11 system could you try (in a Command Prompt)

net use \\ip-address-of-the-w11-system\ipc$ /user:your-username

It’s the same password (and the same user) that is used by LanMan. Apologise for being so annoying, but I’m wandering in the dark.

You could trying resetting the password on W11 for that user or create a new user and use that.

At a Windows administrator command prompt:

powershell

Get-SMBServerConfiguration

Then, to help him know what to reproduce for testing, let Chris know the output, which should be something like this

PS C:\Windows\system32> get-smbserverconfiguration


AnnounceComment                 :
AnnounceServer                  : False
AsynchronousCredits             : 64
AuditSmb1Access                 : False
AutoDisconnectTimeout           : 15
AutoShareServer                 : True
AutoShareWorkstation            : True
CachedOpenLimit                 : 10
DurableHandleV2TimeoutInSeconds : 180
EnableAuthenticateUserSharing   : False
EnableDownlevelTimewarp         : False
EnableForcedLogoff              : True
EnableLeasing                   : True
EnableMultiChannel              : True
EnableOplocks                   : True
EnableSecuritySignature         : False
EnableSMB1Protocol              : False
EnableSMB2Protocol              : True
EnableStrictNameChecking        : True
EncryptData                     : False
IrpStackSize                    : 15
KeepAliveTime                   : 2
MaxChannelPerSession            : 32
MaxMpxCount                     : 50
MaxSessionPerConnection         : 16384
MaxThreadsPerQueue              : 20
MaxWorkItems                    : 1
NullSessionPipes                :
NullSessionShares               :
OplockBreakWait                 : 35
PendingClientTimeoutInSeconds   : 120
RejectUnencryptedAccess         : True
RequireSecuritySignature        : False
ServerHidden                    : True
Smb2CreditsMax                  : 2048
Smb2CreditsMin                  : 128
SmbServerNameHardeningLevel     : 0
TreatHostAsStableStorage        : False
ValidateAliasNotCircular        : True
ValidateShareScope              : True
ValidateShareScopeNotAliased    : True
ValidateTargetName              : True

It’s the same password (and the same user) that is used by LanMan. Apologise for being so annoying, but I’m wandering in the dark.

Isn’t one significant difference between SMB1 and SMB2 the encryption of the password?

net use \\ip-address-of-the-w11-system\ipc$ /user:your-username

Thank you Stuart. I taught me that there’s a difference between my user name in the Users directory on the C drive, and the name with which I logon. Moreover, my Microsoft account has its own user name. But whatever name I enter, I always get the same result (Status is ‘Disconnected’). Strangely, on LanMan I always get a connection with my logon user name (the one that is displayed when I switch the PC on), and the Microsoft password. But that doesn’t work for ShareView, or smb-share-enum, nor any of the combinations that I tried.

You could trying resetting the password on W11 for that user

I’ve done that, but to no avail.

Get-SMBServerConfiguration

When I do that, I get the following output that differs from yours at some points:

AnnounceComment                        :
AnnounceServer                         : False
AsynchronousCredits                    : 64
AuditSmb1Access                        : False
AutoDisconnectTimeout                  : 15
AutoShareServer                        : True
AutoShareWorkstation                   : True
CachedOpenLimit                        : 10
DisableCompression                     : False
DisableSmbEncryptionOnSecureConnection : True
DurableHandleV2TimeoutInSeconds        : 180
EnableAuthenticateUserSharing          : False
EnableDirectoryHandleLeasing           : True
EnableDownlevelTimewarp                : False
EnableForcedLogoff                     : True
EnableLeasing                          : True
EnableMultiChannel                     : True
EnableOplocks                          : True
EnableSecuritySignature                : False
EnableSMB1Protocol                     : False
EnableSMB2Protocol                     : True
EnableSMBQUIC                          : True
EnableStrictNameChecking               : True
EncryptData                            : False
EncryptionCiphers                      : AES_128_GCM, AES_128_CCM, AES_256_GCM, AES_256_CCM
InvalidAuthenticationDelayTimeInMs     : 0
IrpStackSize                           : 15
KeepAliveTime                          : 2
MaxChannelPerSession                   : 32
MaxMpxCount                            : 50
MaxSessionPerConnection                : 16384
MaxThreadsPerQueue                     : 20
MaxWorkItems                           : 1
NullSessionPipes                       :
NullSessionShares                      :
OplockBreakWait                        : 35
PendingClientTimeoutInSeconds          : 120
RejectUnencryptedAccess                : True
RequestCompression                     : False
RequireSecuritySignature               : False
RestrictNamedpipeAccessViaQuic         : True
ServerHidden                           : True
Smb2CreditsMax                         : 2048
Smb2CreditsMin                         : 128
SmbServerNameHardeningLevel            : 0
TreatHostAsStableStorage               : False
ValidateAliasNotCircular               : True
ValidateShareScope                     : True
ValidateShareScopeNotAliased           : True
ValidateTargetName                     : True

Isn’t one significant difference between SMB1 and SMB2 the encryption of the password?

I actually don’t think so, because when I enable SMB1, I have to disable password encryption, otherwise LanMan refuses to connect. But then again, I’m wandering in the dark.

Even more mysterious: I no longer can do a *smb-share-enum in a TaskWindow! When I do, I get the error: File ‘smb-share-enum’ not found.

Now I’m wandering in even more darkness…

I compared your output for Get-SMBServerConfiguration to mine and they are the same.

Even more mysterious: I no longer can do a *smb-share-enum in a TaskWindow! When I do, I get the error: File ‘smb-share-enum’ not found.

If you copy smb-share-enum into the !Boot.Library folder it will always be found.

But whatever name I enter, I always get the same result (Status is ‘Disconnected’).

You hadn’t previously mentioned this. Are you using v0.04? It will show the actual error message on the screen.

If you go back and mount the share as smbv1 from RISC OS. Then run powershell as admin and type the command,

get-smbsession | select-object -property *

It will show the user the session is connected as.

get-smbsession | select-object -property *
It will show the user the session is connected as.

Surely, I’m doing things wrong again, but this is the output, after having established a LanMan98 connection through SMBv1 from my 4té2:

PS C:\Users\pfwsp> get-smbsession | select-object -property *
get-smbsession : Toegang geweigerd.
At line:1 char:1
+ get-smbsession | select-object -property *
+ ~~~~~~~~~~~~~~
    + CategoryInfo          : PermissionDenied: (MSFT_SMBSession:ROOT/Microsoft/...MSFT_SMBSession) [Get-SmbSession],
   CimException
    + FullyQualifiedErrorId : Windows System Error 5,Get-SmbSession

I should add that ‘Toegang geweigerd’ means ‘Access denied’

You need to run the powershell as Administrator, Paul

Stone me, I thought that I had the Administrator version of the powershell on my task bar. But you’re right. It appears that I’m logged on as a guest, and that it doesn’t matter what I enter after ‘User name:’ in the LanMan window. Here’s the proper output:

SmbInstance           : Default
ClientComputerName    : 192.168.2.202
ClientUserName        : PAULS-HP\GAST
ClusterNodeName       :
Dialect               : 1.0.1
NumOpens              : 0
ScopeName             : *
SecondsExists         : 5210
SecondsIdle           : 8
SessionId             : 292057776129
TransportName         : \Device\NetBT_Tcpip_{17C01B42-D064-4765-84BE-CC1B4BEE4990}
PSComputerName        :
CimClass              : ROOT/Microsoft/Windows/SMB:MSFT_SmbSession
CimInstanceProperties : {ClientComputerName, ClientUserName, ClusterNodeName, Dialect...}
CimSystemProperties   : Microsoft.Management.Infrastructure.CimSystemProperties

Trying to logon with ShareView and every combination of user names and passwords that I can think of, I always get a STATUS_LOGON_FAILURE. This is with version 0.04.
Which user name is required exactly? The one that is in the Users directory on the C drive, or the one of my Microsoft account (which is actually my e-mail address), Or another? And which password?

Ignore the one in C:\Users – that’s just some garbled crap that Windows invented to go along with your long Microsoft account name.

I’d create a local user with a simple name like pauls (as in ye olden days, and you shouldn’t even need to log on as that) and add that user to the share. Then use that username on your remote clients.

I’d create a local user with a simple name like pauls (as in ye olden days, and you shouldn’t even need to log on as that) and add that user to the share. Then use that username on your remote clients.

That’s it! Thank you, Stuart. I finally managed to get access to Windows through ShareView. I can’t say that all the secrets of file sharing are now clear to me – and they probably will never be – but this big little mystery is solved now. Many thanks again!

Another new version available (v0.05) here.

New in this version,

It’s now possible to create a folder in the current folder.
When downloading the date/timestamp is preserved.