similar to: Crossing Compiling samba 4.1.0

I know SMB2 support was added for the smbclient in samba 4.1.0, but was SMB3 support also added ? Is there a way to just make smbclient ? Mike

Our smbclient 3.6.5 and smbclient 4.0.7 does not work with SMB2/SMB3, which is a security concern for us. Is there a patch or a workaround that can be done for those releases? I've read that Apple made changes in Maverick 10.9, which now causes failures, but am hoping that something was done to support the MAC OS 10.9 releases. Regards, Mike Tompkins

Second request ... Thank you in advance ... - Mike Sent: Friday, April 10, 2015 2:16 PM To: samba at lists.samba.org Subject: smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1 We are having issues with smbclient 4.0.7 not working to clusters, because it's resolving the host name ( 'default service = dev3k1.my.domain.com' in smb.conf file ) to an IP address

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

Is samba FIPS compliant ? If so, does it need to use SMB2/SMB3 to be FIPS compliant ? We do not use the Heimdal Kerberos libraries that can be compiled with the samba release. We are use samba 4.0.7. Regards, - Mike ?

The problem is that I don't want it to use the IP address, but to use the hostname. Regards, - Mike ? ? -----Original Message----- From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland Penny Sent: Monday, April 20, 2015 10:38 AM To: samba at lists.samba.org Subject: Re: [Samba] smbclient 4.0.7 resolves host name to IP

I?m still struggling to swap PCs to a replacement PDC. Is there a way to reset the machine account (trust relationship) between an existing PC (Windows XP) and a replacement PDC with the same settings as the original PDC? I think it works if I take the PC off the domain by setting it to a workgroup and then put it back onto the domain when connected to the new PDC. However, I?d feel a lot

When we build smbclient 4.3.3 we now have 76 shared libraries to deliver with the smbclient binary. Is there any way to specify it statically linking the libraries so we only have to deliver an executable ? With 3.6.5 and 4.0.7, we only had 3 libraries, which was more more manageable. Thank you, Mike Tompkins

We've been trying to cross compile since 4.1 for PowerPC but were never able to get it to happen and was told it broke with the introduction of Waf. Now we're trying for the latest release, have read some things on the web improvements have been made in this area, but can't seem to get it to build. It appears it's trying to build samba ( we only use smbclient ) for Intel, and also

Thanks for the quick reply Jeremy. We have other FIPS compliant libraries, which check for, and ensure the proper FIPS compliant algorithms are used. Is there a link option to specify this kind of library ? ~ Mike -----Original Message----- From: Jeremy Allison <jra at samba.org> Sent: Tuesday, October 2, 2018 2:08 PM To: Tompkins, Michael <Michael.Tompkins at xerox.com> Cc:

This issue is reproducible for this customer and a couple of others. We execute the smbclient command the same way for each instance. The null user name is valid syntax sent from the smbclient. When we send the command " smbclient -c 'cd <dir>; ls' ", samba code executes starting with Negotiate Protocol Request, and onward. I'm guessing this could be a DFS issue, but

Hello all: I am trying to build smbtorture using static linked libraries. The samba source code I have is samba-4.1.13 for configure, I did: waf configure --builtin-libraries=ALL for build, I did: waf build --targets=smbtorture (so that it only build target smbtorture) But, the waf build fails immediately. Then, I tried to only link with lib talloc and tevent statically, so I did: waf

Sorry about the lack of info. So in the wireshark trace, our printer smbclient 4.0.7 sends a Unicode value in Russian of ???? with a password of ????123. The server rejects the login attempt with STATUS_LOGON_FAILURE. The second attempt is with the linux version smbclient 4.0.7, and the same credentials to the same server work. The only thing I see different in the requests are the flags sent:

We are trying to use Russian(Cyrillic) names in smbclient 4.3.3 but that does not seem to work. Previously we had a problem in 4.0.7 which the location of upcase.dat changed from 3.6.5. In 4.3.3, we don't see it trying to access that file, nor do I believe that file needs to be delivered anymore. Is there a new way to configure the printer to use Russian user names ? Mike

On Tue, 31 Oct 2017 16:06:13 +0000 "Tompkins, Michael via samba" <samba at lists.samba.org> wrote: > Re-sending ... We tend to see a lot of issues with NetApp servers and > SMB 311. Not sure what might be wrong with their response packet, > that 4.6.6 doesn't like. > > ~ Mike > > > -----Original Message----- > From: samba [mailto:samba-bounces at

We get STATUS_INVALID_PARAMETER failures when smbclient uses SMB2 but passes with NT1. We do get some success, but mostly failures. It appears to happen after it transfers the PDF file. These are the packets leading up to SMB2 failing after the transfer: No. Time Source Destination Protocol Length Info 266 2015-04-09 08:30:43.688568000

I have a customer running AIX 6.1 and using pware Samba 3.0.28, and they are looking to install a SMB2/3 compatible version on their AIX server. I found this link https://wiki.samba.org/index.php/AIX_building_samba and understand that it requires xlC 13.1 and a lot of RPMs. Since this customer does not have a current AIX support contract I think it's unlikely that we'll be able to get the

Hello all: I am working on implementing server-side-copy client code. When I checked samba4 source code, I saw that smbtorture has some sort of function that does server-side-copy client function. So, I followed the way that smbtorture does, and implemented my own server-side-copy client code (let's call it cifs_cp). Basically, my cifs_cp code, calls the functions in the files of:

"Tompkins, Michael via samba" <samba at lists.samba.org> writes: > I'm wondering if anyone else has any feedback on this or needs anymore info ? Can you provide the output of the failing command with full debug messages (-d10)? -- Aurélien Aptel / SUSE Labs Samba Team GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg,

hello, When I compil the samba new version samba 3.6.5, on Debian jessie 8.8, most of the time I've got an error message. I can compile without problems samba 3.6.4 on the running servers. It doesn't happen on a fresh install Thanks for your help, - serge. 'configure' finished successfully (1m56.906s) WAF_MAKE=1 python ./buildtools/bin/waf build Waf: Entering directory