Martin Schaefer
Martin Schaefer
We're going to look into this. Might take a while, though.
Can you try to use initWithHost:netbiosName:group: directly on the SMBFileServer and pass the domain as netbiosName?
Should work as you described. SMBFileServer* server = [[SMBFileServer alloc] initWithHost:<hostname> netbiosName:<domain> group:nil]; [server connectAsUser:<username> password:<password> completion:^(BOOL guest, NSError *error) {...}];
Can you pull the newest master and then try the new connect method with the explicit domain argument? Init the server similar to this: let fileServer = SMBFileServer.init(host: “192.168.10.2”, netbiosName:“hostname”...
This is very well possible. Your best bet is to check the server logs and to compare a successful listing of shares with the failed attempt in Wireshark. Filing an...
Yes, that's our plan. We're currently contacting potentially contributing stakeholders. Work on SMB2/3 support will start in May. Unfortunately neither server discovery nor share listing is supported with that library.
Duplicate of #11
Ok, thank you for the details. Unfortunately this is a problem with libdsm, which does not support security signatures. See [this issue](https://github.com/videolabs/libdsm/issues/80) I filed two years ago. While it seems...
I can only assume, that "access denied" is indeed the case. Check if the login falls back to guest access.
Possibly. Currently smb v1 is the only supported option.