similar to: Windows 10 update kills samba access

On 09/20/2016 03:54 PM, Bob of Donelson Trophy via samba wrote: > All of us are having trouble with the "Anniversary update" to W10 > Version 1607. If you can roll back to previous Version 15?? (sorry can't > remember) that MIGHT correct your issue. No promises. It's definitely that update that caused the problem.

On 09/20/2016 04:09 PM, Bob of Donelson Trophy via samba wrote: > On 2016-09-20 15:00, James Knott via samba wrote: > >> On 09/20/2016 03:54 PM, Bob of Donelson Trophy via samba wrote: >> >>> All of us are having trouble with the "Anniversary update" to W10 >>> Version 1607. If you can roll back to previous Version 15?? (sorry can't >>>

On 2016-09-19 14:08, Marcio Vogel Merlone dos Santos via samba wrote: > Em 09/09/2016 12:48, Luc Lalonde via samba escreveu: > >> We have some machines that have updated to the Windows 10 anniversary update (1607) that are having roaming profile sync problems. >> >> Before I search the event logs or provide details, has anyone experience profile sync wierdness? >>

Hello folks, We have some machines that have updated to the Windows 10 anniversary update (1607) that are having roaming profile sync problems. Before I search the event logs or provide details, has anyone experience profile sync wierdness? They changed the profile version again... in 1511 it is version 5, in 1607 it is now version 6. Thank You! -- Luc Lalonde, analyste

I'm trying to access a share on an XP Home system, from SuSE 9.3, using Samba. When I use Konqueror to browse, I can't see anything under the shared directory (D:\), though I can see the contents of the "SharedDocs" folder. If I mount the XP share manually, I can then see all the files. Any idea, why Konqueror can't browse that directory? tnx jk

I've set up a CIPE VPN, between my notebook computer and my Linux based firewall. While the VPN generally works well, I've noticed a strange problem with file sharing from the local network to the notebook. I set up the VPN, with the idea of accessing my systems at home via a dial up ISP, to my home network via cable modem. The VPN works well for most protocols, such as telnet,

On 2016-11-05 08:21, Rowland Penny via samba wrote: > On Sat, 05 Nov 2016 08:07:18 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-11-05 07:46, Mike Lykov via samba wrote: > > 05.11.2016 16:09, Bob of Donelson Trophy via samba пишет: > > Once again, reading here and there and I am confused. > > I thought the W clients

On 2016-12-01 10:00, Rowland Penny via samba wrote: > On Thu, 01 Dec 2016 09:20:15 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> From: Bob of Donelson Trophy via samba <samba at lists.samba.org> >> To: SAMBA MailList <samba at lists.samba.org> >> Subject: [Samba] member server resolv.conf question >> Date: Thu,

On 2016-11-05 07:46, Mike Lykov via samba wrote: > 05.11.2016 16:09, Bob of Donelson Trophy via samba пишет: > >> Once again, reading here and there and I am confused. >> >> I thought the W clients (both W7 and W10) reverse dns PTR records where >> added by the ADDC automatically. >> >> This mornings testing (nslookup of client IP addresses) is not

Once again, reading here and there and I am confused. I thought the W clients (both W7 and W10) reverse dns PTR records where added by the ADDC automatically. This mornings testing (nslookup of client IP addresses) is not finding clients via their IP addresses. (Forward lookups via hostname work fine.) Do we (users of samba4) need to add each W client to our dns servers? (Grated this would

On 2016-11-07 03:06, Rowland Penny via samba wrote: > On Mon, 7 Nov 2016 09:51:50 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > I thought the W clients (both W7 and W10) reverse dns PTR records > where added by the ADDC automatically. Yes, correct if your setup is correct then yes this works. With a default windows install and with a

On 2016-11-14 08:39, L.P.H. van Belle via samba wrote: > Is this on a windows 7 or 10 client or both? > Are you useing \\FQ.DN\share or \\hostname\share > Try the FQ.DN, as Microsoft advices. > > And where are the TLS parameters in the below config. > Did you set this up? > > Greetz, > > Louis > >> -----Oorspronkelijk bericht----- >> Van:

I just transfered fsmo roles from one DC to my newer DC and all went well. Thank you Samba team!! Great documentation, BTW. My domain (basically) consists of one ADDC, one member server and two W10 clients and one W7 client. While setting up the newer DC had been running some nslookup on the DC's and decided to run nslookup on my member server and do not know if I have discovered and

I have a member server running Ubuntu 16.10, Samba 4.4.5 that is serving files to W10 and W7 clients. Things appear fine and suddenly the server share disappears and the W clients "cannot see" the server. The client error message is: "The device or resource (member hostname) is nt setup to accept is not setup to accept connections on port "The file and print sharing

>> I thought the W clients (both W7 and W10) reverse dns PTR records >> where added by the ADDC automatically. >> Yes, correct if your setup is correct then yes this works. With a default windows install and with a few GPO changes. > Early samba4 versions does not support (or have a buggy support) for auto->register PTR recors, as far i remember. I use windows to let

On 2016-10-10 08:33, Marc Muehlfeld via samba wrote: > Hi Bob, > > Am 10.10.2016 um 13:18 schrieb Bob of Donelson Trophy via samba: > >> I noticed the "Joining a Samba DC to an Existing Active Directory" wiki >> page was updated yesterday (October 9, 2016.) > > yes, I'm currently doing a lot of major updates, rewrites, enhancements, > and so on.

Yesterday I was "tailing" a log file (nmbd, I think) and noticed complaints by my member server that there was another "domain master" at the ipaddress on my DC1. This morning Windows clients are being denied updates to "116.168.192.in-addr-arps/IN" (which I believe is the reverse zone.) I think I have an error in my smb.conf file for this server as I have had an

Yes, thank you for the guidance. Regarding "*You do not put the users password here (if that is what you are trying to do): --password=PASSWORD1*" My experience has been this, no matter where I put "--password=" in the string, after the "user" as the manpage suggests or the end. When I run the create string I am asked for a "New Password:' and then

I have been working towards retiring my first member server. (Sernet 4.2.14??) Moved all the user files, checked and double checked the ACL's and all seems good. My users redirect folders to my member servers with a GPO policy. I use roaming profiles (again via GPO) that have been confirmed as working properly against the newer member server (running Samba 4.5.3 from source.) Now, the

Hello, Strangely, the profile sync error is gone now on that machine. But just to be safe, we're rejecting the 1607 updates with our WSUS. It will give me more time to investigate the problem. We'll probably sticking with 1511 in our teaching labs until summer 2017. Sorry I can't help more... Cheers, Luc. Le 2016-09-19 16:30, Bob of Donelson Trophy via samba a écrit : > On