similar to: NT_STATUS_BAD_NETWORK_PATH writing/deleting files to MAC 0S 10.9.5 server

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

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

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

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

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:

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

Samba 3.6.5 client does not train down to plain NTLM if there is no "client ntlmv2 auth = no" statement in the smb.conf file. If the server is configured for just plain NTLM (not NTLMv2), the client will receive a login error, without the smb.conf statement. I know that smbclient 3.6.5 defaults to "client ntlmv2 auth = yes", but the lack of it should be able to login as just

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

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 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.

Are CP850.so and CP437 still needed for smbclient 4.0.7 and later? They don't seem to be built in that release !? From what I've gathered, they seem to be for ms-DOS support, and more needed on the server than the client. Please let me know, so we can remove the dependency to deliver the 2 files. - Mike ?

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 ?

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'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

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

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

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

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