similar to: Sysvol not accessible?

Displaying 20 results from an estimated 10000 matches similar to: "Sysvol not accessible?"

2010 Feb 11
1
issue with mapping BUILTIN on ADS member server
Hello list, Quick summary of the issue (repeated below after the details): Running 'wbinfo --user-info=markc' on either smb ads member server will return identical info. Running 'wbinfo --group-info=BUILTIN\\Users' returns different information on each server. I'd like to make mappings for BUILTIN consistent in case I ever use them. Background and details: I have a
2014 Feb 25
1
advice, suggestions. ( dns-dhcp) and "shared" sysvol ?
Hai, ? Im radicaly changing my network, and i need some advice. ? The setup wil be like this. ? Samba-MASTER???AD-DC server, with DNS-master and TIME-master Samba-SLAVE1?????AD-DC server, DNS Slave1, TIME1, DHCPmaster-server1 ( with failover to 2)???? and when above is running, i'll add. Samba-SLAVE2?????AD-DC server, DNS Slave2, TIME2, DHCPmaster-server2 ( with failover to 1?)? ? Slave1
2018 Oct 17
0
Samba v3 works with LDAP, but not Samba v4
Hi Andrew! I am not 100% sure that the password is correct. I was told that it was changed to the one I am testing. But, when I try the old password, I get a different error message (NT_STATUS_INVALID_SID). I will attached the output. I added the 'ntlm auth = yes' to the smb.conf. How would I change the client? The version of Samba that we are running is 4.7.1, which is the latest
2018 Oct 16
0
Samba v3 works with LDAP, but not Samba v4
I can not see any ldap call, did you try to tcpdump for ldap packets? Michal út 16. 10. 2018 v 21:14 odesílatel Emil Henry via samba < samba at lists.samba.org> napsal: > Hello! > > We have Samba v3 (3.5.10) working against an LDAP server, and need to > upgrade to Samba v4 (4.7.1), RHEL 7 supports only v4. Tried multiple > configs of the smb.conf (including the old config)
2013 Feb 04
0
not able to connect to windows machine
Hi, I am using samba4 and libsmbclient.h and libsmbclient.so. I have implemented the below apis locally within linux machines, but now I want to connect to my windows machine for this I am giving my windows machine username and password In below get_auth_data_fn() function: static void get_auth_data_fn(const char * m_pserver, const char * m_pshare,
2015 Mar 13
1
replicating sysvol with windows DCs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 12.03.2015 um 23:50 schrieb mots at nepu.moe: > The easiest solution/workaround would be to make all the changes to > the policies on one oft he Windows DC's and then use rsync to > replicate them to samba. It won't work. Because you will loose the filesystem ACLs if you sync from Windows to *nix. Regards, Marc -----BEGIN PGP
2018 Oct 17
0
Samba v3 works with LDAP, but not Samba v4
Hi Andrew! Really appreciate the clarification and help. Understood about the password. I have attached the log.127.0.0.1 with the "correct" password being used. I do see entries in that log for the Primary Group of 0. Not sure where I would need to make the change. Any guidance would be really appreciated. Have been fighting this for the last 3 weeks. :-( Thanks. On Tue, Oct 16, 2018
2013 Oct 15
0
sysvol as a DFS Proxy share
Hi all, Is there any reason not to set the [sysvol] share up in the following way on secondary DCs: [global] host msdfs = yes [sysvol] msdfs root = yes msdfs proxy = \primary-ad\sysvol Thanks, Alex
2015 Mar 10
0
net ads join fails
On 10/03/15 20:14, Roman Dilken wrote: > On 10.03.2015 20:20, Rowland Penny wrote: > >> OK, the first will not work (well not yet), the second should, I >> take it you ran 'kinit Administrator at AD.DILKEN.EU' as root before >> the join ? >> >> You could try 'net ads join -U Administrator' and enter the >> password when prompted, I
2015 Mar 12
0
replicating sysvol with windows DCs
The easiest solution/workaround would be to make all the changes to the policies on one oft he Windows DC's and then use rsync to replicate them to samba. -----Urspr?ngliche Nachricht----- Von: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] Im Auftrag von Alex King Gesendet: Donnerstag, 12. M?rz 2015 22:56 An: samba at lists.samba.org Betreff: [Samba] replicating
2015 Jan 26
0
Did you get my previous email? Not Spam.
On 26/01/15 10:21, Jason Long wrote: > Thanks. > > The videos show me to configure below files : > > /etc/nsswitch.conf : > hosts: files dns mdns4 > > then > > /etc/sudoers : > DOMAINNAME\\ACCOUNT ALL=(ALL) ALL > %DOMAINNAME\\domain^users ALL=(ALL) ALL > > and after it, Installed Likewiseopen. The video url is : > >
2012 Oct 28
2
Domain DFS on samba 4
Hello, Our company currently stores its data on centralized samba servers which causes performance problems for remote office employees. We are thinking of decentralizing the data with NAS in each office and synchronizing all the NAS on our central domain controller with MSDFS. I have heard this can be done in real time with Windows and Active Directory.
2015 Mar 10
0
net ads join fails
On 10/03/15 20:29, Roman Dilken wrote: > Oh, I have a pair of samba-4.1.17-DC's, raspberry-pi and dc2 to which make the domain ad.dilken.eu on site Neuoetting. > > resolv.conf points to the two dc's: > > search ad.dilken.eu > nameserver 192.168.2.33 > nameserver 192.168.2.2 > > In the output I find some relations to dc2 resp. 192.168.2.2, but perhaps it
2013 Oct 16
1
Samba 4 sysvol - slow access
Hi everybody, I have yet another issue that I can't solve in my Samba4.0.10 AD DC. For some reason when I access sysvol share via domain name \\domain.local, every directory open waits for about 60 seconds. But when I open it directly on DC \\dc1.domainname.local, it works fine. Is anybody familiar with such issue, (domain was replicated from w2k3) and everything except this is working as
2018 Oct 17
4
Samba v3 works with LDAP, but not Samba v4
On Tue, 2018-10-16 at 20:20 -0700, Emil Henry wrote: > Hi Andrew! > > I am not 100% sure that the password is correct. I was told that it > was changed to the one I am testing. But, when I try the old > password, I get a different error message (NT_STATUS_INVALID_SID). I > will attached the output.  Then it is the old password, and you have other issues you need to sort out.
2016 Jun 09
2
FW: Problem with Active Directory authentication
Hi, Try using the format <domainname><winbind separator><username> to login instead of <username>@<domainname>. I'm not sure why, and don't have time to check into it right now, but ssh doesn't like the <username>@<domainname> format for me either. The default winbind separator is a backslash "\", so you'll have to escape it,
2016 Jun 09
1
FW: Problem with Active Directory authentication
Hi, If you have the "template = /bin/bash" option, I think it is more likely something wrong with the way ssh is trying to authenticate the username. Do a "getent passwd" and then try "ssh -v '<username exactly as getent returns it (case sensitive)>'@<fqdn of server>. If it doesn't work, post the output of what ssh generates. Mike E. On Thu,
2005 Jan 04
1
msdfs: links to shares not visible/accessible in dfs root
Hello list, I am trying to get a DFS share to work here, linking to a few Windows 2000, XP and NT machines. Using Samba 3.0.6 on Debian. I followed the instructions in chapter 17 of the official HOWTO collections and set it up like this: [global] ... netbios name = fileserver host msdfs = yes [dfs] path = /home/data/shares/postdfs valid users = @post force group = +post read only = No force
2016 Jun 09
0
FW: Problem with Active Directory authentication
Hello -- I tried the two methods listed in your e-mail, and unfortunately neither worked. The connection simply closed, or timed out, after about a minute. I mentioned the possibility of creating a symbolic link to the bash shell in my previous e-mail, could that be part of the solution? Thanks. ________________________________ From: Data Control Systems - Mike Elkevizth [mike at
2018 Oct 16
5
Samba v3 works with LDAP, but not Samba v4
Hello! We have Samba v3 (3.5.10) working against an LDAP server, and need to upgrade to Samba v4 (4.7.1), RHEL 7 supports only v4. Tried multiple configs of the smb.conf (including the old config) without success. Cleaned up smb.conf is below. Also, included is the output of a smbclient command on the SMBServer with debug option 10. Hoping that someone can point me in the right direction. Thanks