similar to: samba-tool password edits

My Samba4 computers (DC's & member server) are not shown within W10 File Explorer Network. Only the other workstations appear. I believe this is due to smb1 being depreciated. All the folder redirection still works, gpo, etc. Domain users can log in. What do I need to adjust so these machines appear in smb2? (I know this has been talked about before sorry.) -- Thank you. Bob Wooden

This topic may have been discussed many times, sorry to repeat here. I have been trying various combinations of adding test users via ADUC. The first three (3) added fine. Then the strange began. Many, many W10 client re-starts throughout these process to make client capture any changes from servers. In one case, create the user, give him/her a password. Login from W10 client. Logout of W10

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

I am having some issues that I believe might be related to folder redirection that has prompted me to review my folder redirection GPO settings. On the "Configuring Windows Profile Folder Redirections" page of the Samba WIKI I find an 'information box' that says, /"//Windows does not support dynamically-generated user home folders provided by the Samba [homes] section.

Rowland, I remember now, you and I have been here before and I have lost the email. Due to the manner that linux handles backslashes "\" users need to backslash *around* the backslash you need for W10 like so, "\\\\FQDN" to get "\FQDN" on the W10 path? Therefore, the following is what I want: "--profile-path=\\dtmbr04.ad.dtntwk.work\profiles\sttest11

The "short" version on why multiple groups here. For all my member servers apply the following. This line : > > AllowGroups servers-ssh sshgroup There are 2, linux only Admin accounts, ( local accounts ) And, only if these are member of the "local group" sshgroup then your allowed to login. Only users that are allowed to login with ssh on these servers

When I run "gpresult /R" on one of my domain users the ". . . following security groups" listed at the bottom of the output includes "Denied RODC Password Replication Group". Did a little web search digging and found that RODC stands for Read Only Domain Controller. My domain consists of two DC's and one member server with three W10 workstations. I have never

Rowland, If I stop one of the DC's the other will run fine. The non-running DC when "samba -i" complains that it cannot communicate with the other DC. Running "systemctl start samba=ad=dc.service" has the same cannot connect to other DC. If I stop the running DC with "systemctl stop samba-ad-dc.service" and start the second DC with "systemctl start

The sshgroup exists on the client/workstation: > root at lws4:~# cat /etc/groups > ..................... > sshgroup:x:998:adminlinux > ..................... > But, on my member server that acts as a fileserver for domain users (redirected) files there is no "sshgroup" at this time. The AD has server-ssh group: > root at dc1:~# samba-tool group listmembers

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

Somewhat Samba related, I ask this question (that might be over the line and into Windows territory) but, here I go . . . Of those user on this mailing list that manage Samba installs for various clients/customers, what are your most used GPO policies you have put into place for AD management? I ask because, when you venture over into Windows world and start reading posted articles about their

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

Hai Bob, > I hope you remember me from a few years ago. And I apologize for the direct message. > I have a almost non-Samba question, I think. So, I do not want to post it to the forum, yet. Yes yes, i remember you :-) , and i have no problem with direct messages. How are you doing? I'll reply to the list with a CC for you. Because this involves samba also. And this might help

I have been accessing Windows shares on Windows 7 and 10. However, the update last month seems to have killed samba access. The shares are accessible in Windows. Any idea why samba no longer works with W10 and what can be done about the problem? I'm running openSUSE 13.1. I have enabled the firewall rule as describe here, but it doesn't help, nor does turning off the firewall. tnx jk

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:

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

You can add windows server 2012 to samba 4 domain as a domain member (without AD DC role) without any issues. I myself have added multiple windows 2012, 2012r2 and 2016 member servers without any issues. And, what's important, You actually DON'T want to make them DC, because of what Rowland just wrote. Regards, Kacper. W dniu 04.05.2019 o 20:19, Rowland Penny via samba pisze: >

As the result of my own actions I have had to rebuild my DC's and member server Samba version. It's my fault for upgrading to v4.13.0 too soon. On W10, logged in as administrator, connected to the member server via FileExplorer, the file permissions (via Properties tab) >> Security (tab >> Advanced >> shows the following permissions for the \\mbr04\data folder: Creator

It has become necessary to have a W2012 server on my local lan. I have an existing Samba 4 (Ubuntu) domain with two controllers, a (Ubuntu) member server and a few W10 workstations. If I am reading the wiki correctly "Joining a Windows Client or Server to a Domain" page indicates Windows clients or "servers" and the "server" portion of the lists include W2012. Now,

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