problem while connecting to a windows share [possibly SMB1 missing]

st-one-io / node-red-contrib-smb

Node of Node-RED for SMB Protocol.

Apache License 2.0

2 stars 7 forks source link

problem while connecting to a windows share [possibly SMB1 missing] #9

Open lost-bits opened 3 years ago

lost-bits commented 3 years ago

Hi,

i created a simple flow for connection to a windows host.

On the Windows Host (windows 10) i did the following:

create a local user called logbee
create a directory and share this dir with read/write permission for logbee user

I tested the credentials and the share on an other PC -> it worked fine.

Then I set up the following flow:

after triggering I receive the following message in the debug window:

At first I need some help to fix this, but furthermore I like to suggest 1) implementation of better errors for diagnosis 2) setting SMB1,SMB2,SMB3 on the settings dialog to force the usage of a certain SMB protocoll

Thx

mikepallister commented 3 years ago

Try without the domain. Works for me

blackw1ng commented 3 years ago

Hey, i get the same error when connecting to a Windows 7 machine. Seems to be related to SMB security. https://docs.microsoft.com/en-us/archive/blogs/openspecification/smb3-secure-dialect-negotiation

With or without domains does not make a difference to me.

Solution hints would be appreciated.

blackw1ng commented 3 years ago

Quite some digging resolved in some pretty interesting findings https://github.com/jborean93/smbprotocol/pull/73#issue-562227733 explains issue and solution quite well:

in case of a SMB2.x server you basically cannot do the normal SMB3 flow, as the dialect is unclear
just ignore the STATUS_NOT_SUPPORTED error you are receiving, as long as the server had signed it.
If the server has not signed it then you need to disable secure negotiation

that is surely something to be done in the dependency

lost-bits commented 3 years ago

@mikepallister > Try without the domain. Works for me Tried without domain before I made this issue ... so it does not work either. @blackw1ng I will give it a try .. but some machines are not under my control ... I will report back as soon as tested.