similar to: smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1

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

On 21/04/15 13:37, Tompkins, Michael wrote: > The problem is that I don't want it to use the IP address, but to use the hostname. > > Regards, > - Mike > > You posted: Is there a way to turn off resolving the hostname in either the smb.conf file or as a command line option to smbclient using SMB2/3 ? Using '-I' is a command line

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

hi All, We have a glusterfs cluster with 5 nodes on Ubuntu 12.04 amd64. We use this smb.conf: [global] socket options = IPTOS_THROUGHPUT TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=131072 SO_RCVBUF=131072 read raw = yes server string = %h write raw = yes #oplocks = yes max xmit = 131072 dead time = 15 getwd cache = yes use sendfile=yes block size = 131072 load printers = no aio read size

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

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:

When I search for "smb2", I get nothing in my log file for the NT1 limited system. If it is a workstation issue, that would be great. I'll search around for what settings to change. Maybe SMB2 was inadvertently disabled. Thanks for all of your help on this! On Tue, Apr 19, 2016 at 3:20 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 3:11

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

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

Hello, I set client min protocol = SMB2 in my smb.cnf But I see some clients still connecting in NT1 (smbstatus) : smbstatus -p Mon Jul 22 11:39:36 2019 Samba version 4.8.3 PID???? Username???? Group Machine?????????????????????????????????? Protocol Version Encryption?????????? Signing

I did not set max protocol to SMB2 in smb.cnf, I don't want to force SMB2 selection if SMB3 can be used by a client. The machine is a Windows 7, so is SMB2 compliant. Le 22/07/2019 ? 11:44, Gaiseric Vandal via samba a ?crit?: > I would guess that changing the min protocol does not affect existing > connections unless you were to restart samba. > > Is the max protocol set to at

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 ?

I have a classic NT4 domain with the PDC also the wins server. With the recent ransomware problem, we're trying to remove SMB1 and below protocols. However when I do this, the browse list is gone. Hosts can access properly the shares, but they have to know exactly \\machine\share in order to to connect. The same thing from a linux client: smbclient -L {PDC} -m SMB2 Domain=[{MYDOMAIN}]

Just saw that, as well. After running the commands to enable SMB2 & SMB3 and rebooting...no luck. Will keep searching for other registry settings. On Tue, Apr 19, 2016 at 3:27 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 3:24 PM, Bill Baird wrote: > > When I search for "smb2", I get nothing in my log file for the NT1 limited >

Hi, I am using samba 4.5.4 in my fedora machine. when I execute "smbtree" command it shows nothing with SMB2 protocol. If I change my client max protocol=NT1 in smb.conf, I can see all server present in my Network. looks like below bug. https://bugzilla.samba.org/show_bug.cgi?id=12431 Can it be fixed or someother options can be used for the same to work with protocol greater than NT1

Hello, We are running some legacy software that instructs us to, via Windows registry settings, disable all oplocks and SMB2 entirely on each Windows workstation that connects to the Samba share where the software is hosted. The software maintainers give dire warners of corruption, etc., if oplocks (and SMB2) are left enabled. We?ve run this software off of a Samba share for 20 years and have

That does indeed show "default". For logs, I tested with my system and a system that gets SMB2. Any tips for what I might be looking for? Early on in the logs, I see this for the NT1 system (no mentions of smb2 anywhere) [2016/04/19 14:48:37.738460, 3, pid=21479, effective(0, 0), real(0, 0)] ../source3/smbd/negprot.c:395(reply_nt1) using SPNEGO [2016/04/19 14:48:37.738476, 3,

*testparm -v | grep "client min protocol"* client min protocol = CORE On Tue, Apr 19, 2016 at 2:50 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 2:43 PM, Bill Baird wrote: > > I am accessing the new member server. All my other servers are still on > 3.6.x. > > Both settings are set to "default". > > Will look at

On Fri, Jan 23, 2015 at 01:08:31PM -0800, Jeremy Allison wrote: > On Fri, Jan 23, 2015 at 10:05:44PM +0100, Markus Doits wrote: > > > > On 23.01.15 19:57, Miguel Medalha wrote: > > > I am using Samba 4.1.16 with smb2/3 and symbolic links are working alright. > > > > > > Following the smb.conf man page, I use: > > > > > > unix extensions

Hi Samba Users, I'm in the process of building a Samba4 CTDB /GPFS Cluster joined as a member server to AD that also supports ACL's . It has taken some time but almost everything is working now :) . My one outstanding issue is editing files using Excel 2007 on Windows 7 results in a 'Document not saved' error. I believe this is an issue with the SMB2 protocol as I can edit the same