2017-03-31, 16:31
@Milhouse,
It's not only one server or computer but the entire workgroup doesn't appear ("workgroup" doesn't show). It got 2 rpi's with the latest build (should be using smb3?) and windows 10 pc's (smb3) and an updated Synology DS216+ II where smb3 is enabled in the network settings. Shouldn't it at least show "workgroup" with itself as it's using smb3? Could it be that it doesn't work in a mixed envoirement (got some Enigma2 sat and cable receivers that use smb1)?
Why do both problems work when connecting via ip adress? Isn't this more a problem with name resolving?
But yes, adding: client max protocol = SMB1 solves it!
It's not only one server or computer but the entire workgroup doesn't appear ("workgroup" doesn't show). It got 2 rpi's with the latest build (should be using smb3?) and windows 10 pc's (smb3) and an updated Synology DS216+ II where smb3 is enabled in the network settings. Shouldn't it at least show "workgroup" with itself as it's using smb3? Could it be that it doesn't work in a mixed envoirement (got some Enigma2 sat and cable receivers that use smb1)?
Why do both problems work when connecting via ip adress? Isn't this more a problem with name resolving?
But yes, adding: client max protocol = SMB1 solves it!
