search for: fs01

Hi, I am having some issues with a new server install in Singapore. Outbound calls work fine. Inbound calls are not picked up by Asterisk. Zaptel 1.2.25 and Asterisk 1.2.28 both built from source. libpri installed wctdm and zaptel load without error Jun 6 23:34:03 fs01 kernel: [211138.372933] Zapata Telephony Interface Registered on major 196 Jun 6 23:34:03 fs01 kernel: [211138.372937] Zaptel Version: 1.2.25 Jun 6 23:34:03 fs01 kernel: [211138.372943] Zaptel Echo Canceller: KB1 Jun 6 23:34:03 fs01 kernel: [211138.383639] Freshmaker version: 73 Jun 6 23:34:03...

...home data if needed. These two mounts (/data and /rsnapshot) should be independent of each other. However, a couple of times now I've had somebody accidentally unplug my backup drive (sde), which causes NFS to shut down. Here are the messages entries when this happens. Oct 28 16:34:12 linux-fs01 kernel: xhci_hcd 0000:00:14.0: Cannot set link state. Oct 28 16:34:12 linux-fs01 kernel: usb usb4-port2: cannot disable (err = -32) Oct 28 16:34:12 linux-fs01 kernel: usb 4-2: USB disconnect, device number 2 Oct 28 16:34:17 linux-fs01 systemd: Stopping NFS server and services... Oct 28 16:34:17 lin...

....%m # max 50KB per log file, then rotate max log size = 50 log level = 10 # ############ THE SHARES ############ # [homes] comment = Home Directories browseable = no writable = yes It doesn't work. I get this eror in /var/log/messages: Sep 24 23:40:54 fs01 smbd[1406]: connect_to_domain_password_server: unable to open the domain client session to machine DC.MYDOMAIN.RO. Error was : NT_STATUS_CANT_ACCESS_DOMAIN_INFO. Sep 24 23:40:54 fs01 smbd[1406]: [2014/09/24 23:40:54.406665, 0] rpc_client/cli_pipe_schannel.c:54(get_schannel_session_key_common) Se...

...drwx------ 3 torque torque 8192 May 23 11:31 mirror_trash drwx------ 3 torque torque 8192 May 23 11:31 mirror_trash Volume Name: gv01 Type: Distributed-Replicate Volume ID: 03cf79bd-c5d8-467d-9f31-6c3c40dd94e2 Status: Started Number of Bricks: 11 x 2 = 22 Transport-type: tcp Bricks: Brick1: fs01:/bricks/b01 Brick2: fs02:/bricks/b01 Brick3: fs01:/bricks/b02 Brick4: fs02:/bricks/b02 Brick5: fs01:/bricks/b03 Brick6: fs02:/bricks/b03 Brick7: fs01:/bricks/b04 Brick8: fs02:/bricks/b04 Brick9: fs01:/bricks/b05 Brick10: fs02:/bricks/b05 Brick11: fs01:/bricks/b06 Brick12: fs02:/bricks/b06 Brick13:...

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 in fs01 we get chown: invalid user: `stdom\\ldaptest01:stdom\\...

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 mount it. mount //fs01/wikidata 3. Then ran following command to confirm mount. df Output of 'df': //fs01/wikidata 1821803064 1435...

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 the local site while retaining the credential synchronization ac...

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

...gt;> upgrade to >>>>>> version 4.9 >>>>>> >>>>>> dc01:~# samba-tool dbcheck --cross-ncs >>>>>> Checking 4503 objects >>>>>> SID S-1-5-21-3258148492-1502286889-3538134041-1601 for >>>>>> CN=FS01,OU=Server,DC=xx,DC=xx,DC=xx conflicts with our current >>>>>> RID set >>>>>> in CN=RID Set,CN=DC01,OU=Domain Controllers,DC=xx,DC=xx,DC=xx >>>>>> Please use --fix to fix these errors >>>>>> Checked 4503 objects (1 errors) >&...

...y = No write list = root Administrator @Printer-Admins Fileserver smb.conf, samba = Version 4.10.1-Univention [global] bind interfaces only = Yes deadtime = 15 debug pid = Yes interfaces = lo ens3 ldap server require strong auth = allow_sasl_over_tls logging = file logon drive = I: logon home = \\FS01\%U logon path = \\FS01\%U\windows-profiles\%a machine password timeout = 0 map to guest = Bad User max log size = 0 max open files = 32808 max xmit = 65535 name resolve order = wins host bcast obey pam restrictions = Yes passdb backend = samba_dsdb passwd chat = *New*password* %n\n *Re-enter*new*pa...

....22. I've followed the example in the Samba-3 by example guide to use my server as a PDC. I'm able to connect to this server with all my users but I'm unable to use "Administrator" to log. Maybe it's normal but I doubt it. Here's the log I got for smbclient: [root@fs01 sbin]# smbclient -L localhost -U Administrator -d 3 lp_load: refreshing parameters Initialising global parameters params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Processing section "[global]" added interface ip=192.168.1.10 bcast=192.168.1.255 nmask=2...

...r and also the samba 3 by example and can confirm that nsdc is not enabled. https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member 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 in fs01 we get chown: invalid user: `stdom\\ldaptest01:stdom\\...

...el 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 >>>>>>>> CN=FS01,OU=Server,DC=xx,DC=xx,DC=xx conflicts with our current >>>>>>>> RID set >>>>>>>> in CN=RID Set,CN=DC01,OU=Domain Controllers,DC=xx,DC=xx,DC=xx >>>>>>>> Please use --fix to fix these errors >>>>>>>> Check...

...s() - Processing configuration file "/etc/samba/smb.conf" Processing section "[global]" doing parameter local master = no doing parameter realm = MY.BIG.DOMAIN.LOC doing parameter password server = 10.109.40.128 doing parameter workgroup = MYDOMAIN doing parameter netbios name = FS01 handle_netbios_name: set global_myname to: FS01 doing parameter encrypt passwords = yes doing parameter security = ads doing parameter log file = /var/log/samba.log doing parameter server string = "" doing parameter winbind separator = + doing parameter winbind uid = 10000-20000 doing par...

...lients when accessing the share. I have configured ACLs and the box resolves users and groups. Everything works, except for the shares. Below I attached all of the information I believe to be useful. Ask if you need more, and thank you for your help! smb.conf: ====== [global] netbios name = FS01 workgroup = TRUEVINE security = ADS realm = TRUEVINE.LAN encrypt passwords = yes idmap config *:backend = tdb idmap config *:range = 70001-80000 idmap config SAMDOM:backend = ad idmap config SAMDOM:schema_mode = rfc2307 idmap config SAMDOM:range = 500-40000 winbind n...

...d to run a fileserver on an AD DC, but hopefully you can still offer some advice on troubleshooting. Maybe this isn't even a smb config issue. It could be Windows related??? Here is the actual smb.conf for my fileserver: [global] debug level = 1 logging = file max log size = 0 netbios name = FS01 server role = active directory domain controller name resolve order = wins host bcast server string = Univention Corporate Server server services = -dns -smb +s3fs -nbt server role check:inhibit = yes # use nmbd; to disable set samba4/service/nmb to s4 nmbd_proxy_logon:cldap_server=127.0.0.1 workgr...

...my smb.conf as below: [global] server string = Samba Server Version %v log file = /var/log/samba/log.%m browseable=no guest ok = no security = user map to guest = bad user load printers = no printing = bad printcap name = /dev/null disable spools = yes workgroup = HIKNAS netbios name = fs01 [gltest] comment = path = /mnt/gltest public = yes writeable = yes valid users = nobody write list = nobody directory mask = 0755

...omment out everything, so I edited that to uncomment the bind 9.12 line. Now I'm talking to the outside world again! HOWEVER... I can't resolve the name of the fileserver I built yesterday (from either dc01 or dc02) I CAN find (both with ping and through windows file manager by entering \\fs01 into the search bar) it from the windows clients I have joined to the domain though. Which is weird. itadmin at dc02:/$ ping fs01 ping: fs01: Temporary failure in name resolution so now I'm stuck again.... but it's getting better! On Sun, Sep 6, 2020 at 12:31 AM Peter Milesson via samba...

...vior 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 everything is up. In addition the error message was unhelpful: -bash-3.2# glusterfs --server fs01 /data --volume-name=data glusterfs: could not open specfile -- Matt

...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 >>>> CN=FS01,OU=Server,DC=xx,DC=xx,DC=xx conflicts with our current RID >>>> set >>>> in CN=RID Set,CN=DC01,OU=Domain Controllers,DC=xx,DC=xx,DC=xx >>>> Please use --fix to fix these errors >>>> Checked 4503 objects (1 errors) >>>> >>>> &gt...