similar to: Asterisk not picking up incoming calls from TDM400P

Hello everyone. I joined this list because I cannot find an answer to my problem. The setup is this: I installed CentOS release 6.5 (Final) minimal version Updated all packages Added the server to the Active Directory domain as a member server using the method described here (using adcli, kerberos and sssd): http://jhrozek.livejournal.com/3581.html It worked, I tested by trying to connect through

Hi, We are having some issues with LDAP authentication. Here is our setup PDC and LDAP(samba classic) = dc01 SambaClassic domain = stdom Member server = fs01 We migrated from TDB to LDAP. The old TDB users are able to login to the domain and access file shares without issues. Any new user created in LDAP is not able to access the shares. When trying to create shared drives for the new users

I have been trying to mount a windows file share so I can use it for remote storage particularly for my Deki Wiki attachments. Anyway, I seem to have a mount established by doing the following. 1. Added following line to /etc/fstab //fs01/wikidata /var/www/dekiwiki/attachments cifs user,uid=500,rw,suid,username=wikisvcacct,password=testpwd,domain=corporate 2. Then ran following command to

Hi, Not sure exactly how I would word the subject line so appologies in advanced. We are trying to accomplish the following scenario: Location 1: PDC: fs01.loc1.example.com IP: 10.0.0.1 Location 2: SDC: fs01.loc2.example.com IP: 10.0.1.1 Clearly when we join the SDC to the PDC there is a naming conflict. The end result would be to have clients at each site resolve the fs01 name to

Hi, Our setup: Samba (classic) DC: cdr-dc01 Samba (classic) member server: cdr-fs01. This is also a file server AD realm: CDR.internal We migrated to AD and came across an issue with accessing shares. The shares in question worked pre-migrated. i.e using a windows machine a user was able to access that share. The share in question was locked down to just that user Post migration, we are able

Am 25.09.2018 um 12:37 schrieb Rowland Penny via samba: > On Tue, 25 Sep 2018 12:08:00 +0200 > Daniel Jordan <d.jordan at gfd.de> wrote: > >> Am 25.09.2018 um 11:35 schrieb Rowland Penny via samba: >>> On Tue, 25 Sep 2018 11:18:03 +0200 >>> Daniel Jordan via samba <samba at lists.samba.org> wrote: >>> >>>> Am 24.09.2018 um 19:33

Hi, I'm trying to join my Linux file server to an AD domain. I've looked at several different documents describing how to do this, but I still am not able to get everything to work correctly. I am able to join my domain, but I cannot use smbclient to connect to another file server in the domain, nor can I connect to the samba server from my desktop PC. My kerberos tickets seem to be in

Sorry, but I didn't really know how to word this. I have Univention Corporate server running as AD DC, with a UCS running as a member fileserver. One win10 client has file permission issues after lack of reboot or logout/login in roughly a weeks time. Symptom = can't write to shares even though permissions are correct. Sometimes files are created without honoring default ACL. Could this

Am 25.09.18 um 14:26 schrieb Rowland Penny via samba: > On Tue, 25 Sep 2018 13:12:18 +0200 > Daniel Jordan <d.jordan at gfd.de> wrote: > >>>>>>>> dc01:~# samba-tool dbcheck --cross-ncs >>>>>>>> Checking 4503 objects >>>>>>>> SID S-1-5-21-3258148492-1502286889-3538134041-1601 for >>>>>>>>

I have been using Samba4 for ages and love it as a DC and a print-server. I just setup my first member-server designed solely to host file shares, and have hit an issue. Group policy is mapping it correctly for the users in the group, but those users are getting an access denied message from their Windows 7 Pro 64bit clients when accessing the share. I have configured ACLs and the box

Thank you everyone for your help. I corrected my resolv.conf files as Peter Milesson suggested and then had to take a number of extra steps so now things are looking a little better. In case it helps anyone else in the future, here's what I found (plus I am now having problems resolving internal addresses). As far as I can see, the setup on both servers is identical (except they use their own

Am 25.09.2018 um 11:35 schrieb Rowland Penny via samba: > On Tue, 25 Sep 2018 11:18:03 +0200 > Daniel Jordan via samba <samba at lists.samba.org> wrote: > >> >> Am 24.09.2018 um 19:33 schrieb Andrew Bartlett via samba: >>> On Mon, 2018-09-24 at 13:51 +0200, Daniel Jordan via samba wrote: >>>> Hello list, >>>> >>>> I'm

Hi , We ran the classic upgrade and migrated the domain . We were then able to add a Windows Server 2008R2 and dcpromo it. Here are some of the issues we are seeing post migration - Pre the migration, the password backend was LDAP. We had some groups that we had migrated into LDAP from TBD. These groups doesn't seem to have come up in AD. - Any groups that were created in

Hi Rowland, We did the classicupgrade. Post the classicupgrade, we added a Windows 2008R2 server and dcpomo'd it. The original Samba box (classic DC) was where we did the classicupgrade. Did you mean that we need to shut that box down? Leaving a Windows DC (FSMO?) and Samba member server? Sorry I was not aware of this step. What if we hadn't added a Windows 08 box? Here is the

I just had to deal with a situation where a glusterfs filesystem would not mount because someone had managed to create some files and directories under the mount point. Perhaps this behavior is intentional, but I would prefer that it work like NFS and just overmount. When bringing a cluster down and back up, it is quite possible for overeager users to log in and start working before

Hi all, Now I have a directory shared with anonymous account nobody. And I have add it to the write list of my share. When i mount it by windows 10, I create a sample file name test.txt, I check it in backend file system looks like this: -rwxr—r— 1 nobody nobody test.txt I can delete/create/rename a file, but can not write into it. Please help me. My samba version is 4.4.4, samba server

Hello, I'm trying to configure a CIFS-Proxy. My configuration is: [global] workgroup = MYDOM server role = member server realm = MYDOM.NET netbios name = FS01 server services = +smb +s3fs dcerpc endpoint servers = +winreg +srvsvc [test] ntvfs handler = cifs cifs:server = 192.168.1.10 cifs:share = projects$ but in

Hello list, I'm getting a weird error message regarding our file server when i run dbcheck on my dc01 running Samba v4.7.9. The error only occurs on dc01, dc02 is fine, the file server also works fine but I want to clean the database before doing the upgrade to version 4.9 dc01:~# samba-tool dbcheck --cross-ncs Checking 4503 objects SID S-1-5-21-3258148492-1502286889-3538134041-1601 for

Am 24.09.2018 um 19:33 schrieb Andrew Bartlett via samba: > On Mon, 2018-09-24 at 13:51 +0200, Daniel Jordan via samba wrote: >> Hello list, >> >> I'm getting a weird error message regarding our file server when i >> run >> dbcheck on my >> dc01 running Samba v4.7.9. The error only occurs on dc01, dc02 is >> fine, >> the file server also

extensions.conf has ignorepat => 9 exten => _9X.,1,Dial(Zap/G2/${EXTEN:1}) The first user to try it asked if instead of keeping the same dialtone after pressing 9, if I could play a different dialtone. Can this be done? I'm running asterisk 1.0.0 in case that matters.