Tompkins, Michael
2014-Oct-29 18:23 UTC
[Samba] Samba client 3.6.5 fails sending to MAC 0S 10.9.x Maverick server
I have been searching for weeks for information to our problem, trying to connect our smbclient 3.6.5 to a MAC running 10.9.5 server, and I finally came across the reason. It appears with Maverick, Apple will only accept SMB2 signed signatures. The problem with the 3.6.5 client is, it never supported SMB2, thus will not write the SMB2 signatures. I can add "client signing = disabled" to the smb.conf file, but I don't want to restrict for all servers, a device may talk to. Is there any workaround for 3.6.5, so I can be flexible depending on the server ? Any help would be appreciated, even from Apple if anyone has a contact. I've tried several, but have not received a response. Regards, Mike
Jeremy Allison
2014-Oct-30 03:23 UTC
[Samba] Samba client 3.6.5 fails sending to MAC 0S 10.9.x Maverick server
On Wed, Oct 29, 2014 at 06:23:26PM +0000, Tompkins, Michael wrote:> I have been searching for weeks for information to our problem, trying to connect our smbclient 3.6.5 to a MAC running 10.9.5 server, and I finally came across the reason. It appears with Maverick, Apple will only accept SMB2 signed signatures. The problem with the 3.6.5 client is, it never supported SMB2, thus will not write the SMB2 signatures. I can add "client signing = disabled" to the smb.conf file, but I don't want to restrict for all servers, a device may talk to. Is there any workaround for 3.6.5, so I can be flexible depending on the server ? Any help would be appreciated, even from Apple if anyone has a contact. I've tried several, but have not received a response.The 4.1.x client fully supports SMB2 signatures. Did you back-port all the client code to 3.6.5 ? You might want to extend the back-port to include the SMB2 client signing. Jeremy.
Apparently Analagous Threads
- Samba client doesn't work SMB2 with MAC 0S 10.9.5
- smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
- Crossing Compiling samba 4.1.0
- smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
- NT_STATUS_BAD_NETWORK_PATH writing/deleting files to MAC 0S 10.9.5 server