similar to: Cross Compiling 4.1.0 issue

What is the status of cross compiling samba 4.1.0 with the new waf configure. We don't have a native compiler or emulator to use. We used autoconf in 3.6.5 and earlier, which worked successfully. We are in need of smbclient, which supports SMB2 (and maybe SMB3?) right away, so we need to resolve this issue. Thanks, Mike Tompkins

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

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:

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:

I'm checking back in to see if samba is FIPS compliant, as in using FIPS compliant algorithms ? Can it be built with openssl, which is FIPS compliant ? We're currently running 4.7.5. Please let me know. Regards, Mike

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

"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,

We are running Samba-4.6.6 and are running into an issue where it negotiates to a NetApp server but then the client stops the connection. 8262 2017-10-12 09:32:16.198917 10.136.78.14 10.128.101.128 TCP 66 45848 → 445 [FIN, ACK] Seq=403 Ack=581 Win=16768 Len=0 TSval=11546007 TSecr=3316317046 This is at a customer site, and we cannot recreate it here due to

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

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

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

I am trying to use smbclient with a Russian login and it refuses the connection. This is with a smbclient compiled for our printers. If I use the linux version, downloaded from the samba site, it works correctly. I'm thinking it's how I have it configured, but I can't tell from the wireshark trace (included). Any help where I would look specifically in the code would be appreciated.

I am wondering if anyone has had a chance to look at bug 12518? This is the context of the message: Wireshark trace gives a STATUS_INVALID_PARAMETER when running smbclient -c 'cd <dir>;ls' as a standalone program. This is a customer issue. We cannot recreate this issue so we're looking for why this may be happening. From the trace you'll see multiple sessions with

We currently are running smbclient 4.0.7. Users need to add domain name or "\" before username for authentication to succeed. Otherwise, smbclient prepends WORKGROUP\ to username. In a particular environment, "WORKGROUP\username" does not have access to the user's home directory. If we add "workgroup =" parameter in smb.conf file, it now passes. Is it valid to

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

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

I'm trying to compile 4.1.2 with the new KRB5 1.12 library and it needs to reference libkrb5support. I can't find in which wscript file to affect the building of the krb5 libraries. I was editing bin/c4che/default.cache.py, but I know that's not the correct way, and that file does get recreated. Any help would be appreciated. Regards, Mike

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

I noticed that AIX now comes with a version of zlib installed in /usr. (I'm working on 5.2) My first inclination was to simply uninstall it and use the one we compile (and put in /usr/local). However, IBM has made zlib part of the RPM package itself! So, I cannot uninstall it without removing RPM.... Next, I tried passing --with-zlib=/usr/local to configure for ssh. This seems to work, but

I noticed there was Bug 12808 against 4.6.3 ( if I read it right ) about smblcient doesn't handle STATUS_NOT_SUPPORTED gracefully for FSCTL_VALIDATE_NEGOTIATE_INFO. We are currently updating to 4.6.6 and I do not see it in smbXcli_base.c. I see the fix was done in 5/30/2017. Is this something that is still needed, and will be added in future releases ? I would like to know whether I should