similar to: "net time" cannot connect to Windows 10 Pro computer

On Thu, Jun 08, 2017 at 06:43:34PM +0200, Ralph Böhme via samba wrote: > Hi Andy, > > On Thu, Jun 08, 2017 at 09:23:50AM -0700, Andy Qian via samba wrote: > > The smbcacls cmd worked before till recently. Due to the recent Windows > > patch which disables SMB v1, we have to add the following line into the > > [global] section in smb.conf file on Linux machine so that

Hi, all, we run smbcacls tool from linux machine to set file permissions on windows server. here is our environment: Linux machine: Ubuntu 14.04 LTS, kernel version 3.13.0-112-generic Samba version: 4.3.11 Windows machine: Windows server 2012 the cmd we run is something like following: /usr/bin/smbcacls -U 'Domain\Administrator'%'pwd' '//win_server/testshare'

On Tue, 8 Oct 2024 00:20:44 -0400 samba3to4 via samba <samba at lists.samba.org> wrote: > Hello Experts, > > I am trying to migrate a Samba 3.6 server to Samba 4.19. > > [...] > > The log file shows that the user can authenticate: > > [2024/10/07 23:27:24.974539, 2] ../../source3/auth/auth.c: > 338(auth_check_ntlm_password) check_ntlm_password:

On Tue, Nov 08, 2005 at 08:04:54AM -0800, Bryan J. Smith wrote: > > > NAS offers safe concurent access (generally, there might be > > some NAS devices outthere that do not). NAS device will > > manage file system internally, and export it over NFS or > > SMB protocols to the clients. > > Such NAS' are a combined host+storage aka

Hai, Im wondering here.. If the client is a windows 10 pc connecting, > ../source3/smbd/negprot.c:419(reply_nt1) using SPNEGO > ../source3/smbd/negprot.c:761(reply_negprot) Selected protocol NT LM 0.12 > ../source3/smbd/process.c:554(receive_smb_talloc) > receive_smb_raw_talloc failed for client > ipv4:10.55.66.82:59271 read error = NT_STATUS_CONNECTION_RESET. And i

I am having a problem with getting smbclient to interact with a Window 10 PRO/64 bit machine. The smbclient is being run from a FreeBSD-11.1/amd64 machine. smbclient - Version 4.6.11 Windows 10 Pro - version 1709 I have tried numerous methods, like the following: smbclient -I 192.168.0.102 -L HP-ENVY protocol negotiation failed: NT_STATUS_CONNECTION_RESET In every instance, it ends with the

I am getting the following error from backuppc when trying to backup a windows7 machine from my ubuntu machine(though I believe this error comes directly from samba): [CODE][ skipped 44618 lines ] Error reading file \medSchool\body\dissectionimages\practice.pptx : NT_STATUS_CONNECTION_RESET Didn't get entire file. size=272456645, nread=126584640[/CODE] The backup occurs fine for *hours*

Hello I have an samba server with a public share. It was configured with security=share. Now I have to tight security with setting those flags in the windows client: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] EnablePlainTextPassword=0 EnableSecuritySignature=1 RequireSecuritySignature=1 Since this change the public share is not working anymore. I found

See Inline LPHvBvs> Hi Gregory, LPHvBvs> On the questions. >> Is there a good reason to avoid Samba internal DNS? LPHvBvs> No, imo not, but i only use bind9_dlz because i need bind in my lan for other setups also. LPHvBvs> I just used my RSAT on my win7 64b, but at my point it works fine. LPHvBvs> I do have questions to get a better impression of the setup. LPHvBvs>

Hi, Some users are experiencing problems working with files in Windows and Samba shares within engineering applications. The sequence is as follows: A user opens a file, e.g. a drawing, inside an application. The user works fine for a while, but suddenly it cannot edit the file anymore. The only way to continue working is closing and opening the file again, like if the session had expired and a

I have an NT domain on Debian Stretch. It's been upgraded numerous times, but has been running for almost a decade. Since upgrading from 4.1.17 to 4.3.3 (huge Debian jump), then to 4.3.6, clients cannot connect to shares. Prior to upgrading, I found the changes mentioned for 4.2 regarding NT domains and applied them. Even so, I still cannot connect to network shares nor print to

Hai, ... > > As I said, where is the fault, is it something that Windows 10 is or > isn't doing, or is it Samba ? > > Well, we cannot change Windows, so on that basis, I think you should > make a Samba bug report and let it work through the system. > > Rowland Well, yes, we can change windows, by allowing/disallowing SMB1. Which might help in detecting whats

Hello Experts, I am trying to migrate a Samba 3.6 server to Samba 4.19. The OS of the old server is FreeBSD 10.3 and the new one is FreeBSD 14.1. The client computers are Win 10 Pro. Simple Samba configuration, no need for Active Directory, just a file server with user authentication. On the Windows computer I try to mount the shares from the new server as \\[new server IP address]. The log

You may have included this in another email however I will ask anyway, did you set DNS to your server in the Linux and Windows clients? Can you check if a Windows Server can join? Can you use DNS management to check the DNS on you samba server? On Mar 28, 2016 2:15 PM, "Dale Schroeder" <dale at briannassaladdressing.com> wrote: > No takers thus far. These are the Samba 4.2

FreeBSD 12 Samba 4.8.12 Samba is not showing up on my Win 10 PRO machine. I can access the shares if I use the machines hostname or IP, though. How can I determine what version of ?smb? is being used? I have set ?client max protocol = SMB3? in the config file; however, I am not sure if it is being used. Thanks! -- Gerard -------------- next part -------------- A non-text attachment was

Dear all, Le 07.09.2015 à 15:52, soonerdave a écrit : > Windows 10 will try to negotiate SMB3_11, which Samba4 doesn't yet support > except in the current 4.3 release candidate. I suspect for now disabling > SMB2/3 on the Windows 10 client is your best, if not ideal, option. > > Instructions for doing.this can be found > here: https://support.microsoft.com/en-us/kb/2696547

Dear,Samba updated to 4.4.5 version.The Samba is a secundary DC.I'm getting some authentication errors. smbclient -k -L //domain.localsession setup failed: NT_STATUS_INTERNAL_ERROR Using my PC when I try to access the \\sambadc, is asking User and Password.The logs appears this: ctx setting sec (0, 0) - 0 = sec_ctx_stack_ndx[25/07/2016 14: 08: 04.581532, 5]

Hi everybody, May someone help me out on a short question, please? We own an ERP based on MSAccess, backend is on a samba share, openSuSe 42.3. The ERP is very sensitive on disconnection from those - also if it is just a reload of config. We did not changed anything within the last week, but on thusday/friday my collegues started to comlain about "database or network error" message

I have a toshiba copy machine that is also used as a scanner. The scanner can be set to store files to a SMB UNC. So I create a username/password for the scanner to login with, then configured a unc path for to store to. All was working well for a while. Then the scanner stopped storing to the samba share. Initial analysis seemed to indicate that the username/password was failing. So I reset it

On Mon, 14 Oct 2019 13:47:34 +0100, Rowland penny via samba stated: >On 14/10/2019 13:27, Gerard Seibert via samba wrote: >> FreeBSD 12 >> Samba 4.8.12 >> >> Samba is not showing up on my Win 10 PRO machine. I can access the >> shares if I use the machines hostname or IP, though. How can I >> determine what version of ?smb? is being used? I have set ?client