Impossible to access a path

Question

Good morning sirs,

I'd like to enter in this network path, pointing to another W10 PC.

I succeed in 3 other clients, except from a PC, and I get this error:

with \192.168.1.35 or \andrea i get the same error

I don't understand why I get this problem only in 1 client. Can you help?

Answer 1

Hello @Andrea Vironda ,

The credentials used in this failing case are domain = "." (i.e. the credentials refer to a local account on the SMB server) and username = "Bernardo" (password not known since NTLM is used for authentication).

You mention that everything works from 3 other clients - that still leaves 2 possibilities:

1. Correct credentials are used when testing from the other 3 clients.
2. Incorrect credentials are used when testing from the other 3 clients, but the clients are content to use a "guest" session.

Is there a user named "Bernardo" in the local accounts database on the SMB server? I don't quite understand what the implications of "Those users were managed by a server that now is crashed" are...

Gary

Answer 2

Hello @Andrea Vironda ,

There are probably lots of possibilities. Two commands that I can immediately think of that could be used on the SMB server are:

1. "net sessions" (from any command window)
2. The PowerShell cmdlet "Get-SmbSession"

Both should show the client user name.

Gary

Answer 3

Thanks for Gary's analysis.

Hi @Andrea Vironda ,

I am sorry that this issue still hasn't been resolved.

If there is no progress, I would suggest you contact Microsoft Customer Services and Support to get a deeper analysis of the .etl trace and an efficient solution:

You can find the phone number of your region in the following link.

https://support.microsoft.com/en-us/gp/customer-service-phone-numbers

Best Regards,
Sunny

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.