You are not logged in.
I switched and have some problems connecting to servers using my bunsenlabs helium client, both with thunar and command line smbclient.
I am aware that the network neigbourhood isn't supposed to work by design so I ckecked with a win10 machine (smb1 deinstalled) to directly connect to the share e.g. //server/share which works fine so it looks like that I am missing something.
I already switched to "min protocol = smb2" in smb.conf but that doesn't help.
If I try to connect smbclient -U anonymous //server/share I will get a password prompt but...
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
regards
Addendum: will try "protocol = SMB2"
...and it all started with a #!
Offline
protocol = SMB2
solved it!
...and it all started with a #!
Offline
@earlybird Thank you for your input! I would like too but the share is on a router and there is no easy way using smb3 because it is not available in the compiled packages (openwrt), probably had to compile it myself or switch to snapshot. For now I am glad that I've got smb2 working ;- )
regards
...and it all started with a #!
Offline