"You can’t access this shared folder because your organization’s security policies block unauthenticated guest access" - WINDOWS 10

Berikut ini adalah cara solving problem tidak bisa mengakses file share

1.  Buka gpedit.msc

2. Lalu Pilih Computer Configuration - Administrative Templates - Network - Lanman Workstation, lalu edit value Enable insecure guest logons. menjadi "ENABLE"

3. Setelah itu click "OK"

sekarang coba akses kembali folder yang ingin kita tuju.

Pada Active Directory tidak hanya user account yang memiliki password, tetapi setiap komputer yang sudah terjoin ke domain juga memiliki password (yang dinamakan Machine Account Password) dalam bentuk kode binary yang secara otomatis melakukan update setiap 30 hari dan berjalan di background system windows. Password machine account tersebut akan tersimpan (cached) di database local komputer user dan akan melakukan sinkronisasi ke server AD.

Machine account password ini bisa di ibaratkan unique ID yang terdaftar di database server AD. Jika sudah 30 hari seharusnya unique ID tersebut telah di generated, sedangkan kondisi PC user tidak terhubung ke server AD maka kode password machine nya jadi tidak sinkron antara PC user (client) dengan server AD. Sehingga impactnya terjadi error berikut saat user login AD : "The trust relationship between this workstation and the primary domain failed"

Issue ini terjadi biasanya disebabkan komputer user tidak bisa melakukan sinkronisasi machine account password ke server AD, bisa dikarenakan koneksi jaringan terputus atau tidak stabil. Bisa juga dikarenakan user sudah terlalu lama/sering login PC menggunakan user account local (bukan user AD) sehingga machine account password tidak terupdate dan gagal sinkron dengan server AD.

silahkan download tutorialnya disini

silahkan download tutorial nya  pada link dibawah ini.

Download Tutorial

silahkan di download tutorial nya pada link dibawah ini.

Silahkan ikuti cara berikut:

Download Pdf  File

*Note: You must disable CentOS-Base.repo  CentOS-Sources.repo for use the local repositori

1. Open |Terminal

2. change directori to /etc/yum.repos.d

    cd /etc/yum.repos.d

3. create file  local.repo

    nano local.repo

4.  type like this

       [RHEL7-REPO]

   name=Local REPO

   baseurl=file:///mnt/CentOS

   enabled=1

   gpgcheck=0

and then save the file

5. mount the DVD image to folder /mnt/CentOS

       mkdir -p /mnt/CentOS

   mount /dev/sr0 /mnt/CentOS

6. yum clean all

[root@zimbra yum.repos.d]# yum clean all

Loaded plugins: fastestmirror, langpacks

Cleaning repos: RHEL7-REPO

Cleaning up everything

Cleaning up list of fastest mirrors

7. yum update

[root@zimbra yum.repos.d]# yum update

Loaded plugins: fastestmirror, langpacks

RHEL7-REPO                                               | 3.6 kB     00:00

(1/2): RHEL7-REPO/group_gz                                 | 157 kB   00:00

(2/2): RHEL7-REPO/primary_db                               | 2.7 MB   00:00

Determining fastest mirrors

No packages marked for update

8. test to install NC package from local dvd

       yum install nc

[root@zimbra yum.repos.d]# yum install nc

Loaded plugins: fastestmirror, langpacks

Loading mirror speeds from cached hostfile

Resolving Dependencies

--> Running transaction check

---> Package nmap-ncat.x86_64 2:6.40-4.el7 will be installed

--> Finished Dependency Resolution

Dependencies Resolved

================================================================================

 Package           Arch           Version              Repository          Size

================================================================================

Installing:

 nmap-ncat         x86_64         2:6.40-4.el7         RHEL7-REPO         200 k

Transaction Summary

================================================================================

Install  1 Package

Total download size: 200 k

Installed size: 410 k

Is this ok [y/d/N]: y

Downloading packages:

Running transaction check

Running transaction test

Transaction test succeeded

Running transaction

  Installing : 2:nmap-ncat-6.40-4.el7.x86_64                                1/1

  Verifying  : 2:nmap-ncat-6.40-4.el7.x86_64                                1/1

Installed:

  nmap-ncat.x86_64 2:6.40-4.el7

Complete!

Thanks.!!

   

Buat script pada direktori tmp

Masuk ke user zimbra dengan menggunakan perintah su - zimbra

Jalankan perintah sh /tmp/export.sh /tmp/hasil-export.csv

Jika proses sudah selesai, data dapat diambil/dilihat pada file hasil-export.csv pada direcroty tmp.

berikut script nya

==============================================================

RESULT=$1

if test -f $RESULT; then

rm -rf $RESULT

fi

TMPFILE=/tmp/userattr

for user in `zmprov -l gaa`; do

echo "getting $user attributes"

zmprov ga $user > $TMPFILE

gn=`cat $TMPFILE | grep ^givenName | cut -d: -f2 | sed -e 's/^ *//'`

sn=`cat $TMPFILE | grep ^sn | cut -d: -f2 | sed -e 's/^ *//'`

dname=`cat $TMPFILE | grep ^displayName | cut -d: -f2 | sed -e 's/^ *//'`

name=`cat $TMPFILE |grep ^zimbraMailDeliveryAddress | cut -d: -f2 | sed -e 's/^ *//'`

echo "FirstName: $gn, LastName: $sn, displayName: $dname, email: $name" 

echo "$gn,$sn,$dname,$name" >> $RESULT

done

script for set account to the maintenance mode

pls follow this step to create the script.

vim account_to_maintenance.sh

put the code

here is the code.

#!/bin/bash
for i in $( cat /tmp/daftar_user.txt ); 
do
    zmprov ma $i zimbraAccountStatus maintenance
done

save the file

Note : 
pls create this file  daftar_user.txt

daftar_user.txt  : put the list user who wants to be a maintenance mode

i got this error, the root cause is DNSRBL to njabl.org  and ahbl can not be used anymore because the service has been closed therefore each perform lookup dnsrbl will always fail

http://www.ahbl.org/content/last-notice-wildcarding-services-jan-1st

Jan 7 15:18:55 zmmail postfix/smtpd[13988]: NOQUEUE: reject: RCPT from unknown[10.33.10.10]: 554 5.7.1 Service unavailable; Client host [10.33.10.10] blocked using dnsbl.ahbl.org; List shut down. See: http://www.ahbl.org/content/last-notice-wildcarding-services-jan-1st; from=<> to= proto=ESMTP helo=

to solve this problem pls. run this command as zimbra user

su - zimbra
zmprov mcf -zimbraMtaRestriction "reject_rbl_client dnsbl.ahbl.org"

zmprov mcf -zimbraMtaRestriction "reject_rbl_client dnsbl.njabl.org"

zmmtactl reload

To fix this issue, find the Zimbra crontabs directory at /opt/zimbra/zimbramon/crontabs

Now, lets put the cronjob’s to a single file (just to make your job easier) as follows:

[root@zimbra crontabs]# cat crontab >> crontab.zimbra
[root@zimbra crontabs]# cat crontab.ldap >> crontab.zimbra
[root@zimbra crontabs]# cat crontab.logger >> crontab.zimbra
[root@zimbra crontabs]# cat crontab.mta >> crontab.zimbra
[root@zimbra crontabs]# cat crontab.store >> crontab.zimbra

Finally,Load the crontab.zimbra file to crontab as follows:
[root@zimbra crontabs]# crontab -u zimbra crontab.zimbra

to verify the crontab zimbra is exist

su - zimbra

crontab -l

1.  Cari account spam pada search bar  yang ada pada zimbra admin console
2.  Klik kanan => view mail

Maka akan muncul mailbox dari account spam tersebut

• Cari e-mail yang dibutuhkan
• Klik kanan => Redirect => masukan nama e-mail tujuan
• Setelah itu e-mail akan masuh pada inbox tujuan

E-mail yang sudah di redirect bisa di lihat pada inbox user

semoga bermanfaat.

    1.        Melakukan tunning zimbraPop3NumThreads dan zimbraImapNumThreads

●     login sebagai zimbra user, lalu masukan perintah seperti dibawah ini.

su - zimbra zmprov ms `zmhostname` zimbraPop3NumThreads 300 zmprov ms `zmhostname` zimbraImapNumThreads 500

●     Lakukan Restart service zimbra

zmcontrol restart

Note:

lakukan pada server-server mailbox

http://wiki.zimbra.com/wiki/Performance_Tuning_Guidelines_for_Large_Deployments

Use the following commands to create the new user anwar, grand him the same privileges as root and set him a password :

# useradd -ou 0 -g 0 anwar
# passwd anwar

We've just created the user anwar, with UID 0 and GID 0, so he is in the same group and has the same permissions as root.

http://www.shellhacks.com/en/HowTo-Create-USER-with-ROOT-Privileges-in-Linux

First download the appropriate binaries from this location:

RHEL/CentOS 6: http://files.zimbra.com/downloads/8.0.7_GA/curl/RHEL6_64/curl-7.35.0.tgz
UBUNTU 10: http://files.zimbra.com/downloads/8.0.7_GA/curl/UBUNTU10_64/curl-7.35.0.tgz
UBUNTU 12: http://files.zimbra.com/downloads/8.0.7_GA/curl/UBUNTU12_64/curl-7.35.0.tgz
SLES 11: http://files.zimbra.com/downloads/8.0.7_GA/curl/SLES11_64/curl-7.35.0.tgz

The MD5 checksums are also available:

RHEL/CentOS 6: http://files.zimbra.com/downloads/8.0.7_GA/curl/RHEL6_64/curl-7.35.0.tgz.md5sum
UBUNTU 10: http://files.zimbra.com/downloads/8.0.7_GA/curl/UBUNTU10_64/curl-7.35.0.tgz.md5sum
UBUNTU 12: http://files.zimbra.com/downloads/8.0.7_GA/curl/UBUNTU12_64/curl-7.35.0.tgz.md5sum
SLES 11: http://files.zimbra.com/downloads/8.0.7_GA/curl/SLES11_64/curl-7.35.0.tgz.md5sum

Then place the downloaded tgz file at the following location: /tmp/curl/$PLAT/
(where $PLAT is one of RHEL6_64, SLES11_64, UBUNTU10_64, or UBUNTU12_64).

Then run:
[root@mail01 ~]# ./zmcurl807-updater.sh -o

Validating patched curl: success
Backing up old curl: complete
Installing patched curl: complete
Curl patch process complete.
Please restart Zimbra Collaboration Suite as the Zimbra user via 

--------------------------------------------------
restart service mta
--------------------------------------------------
[root@mail01 zimbra]# su - zimbra
[zimbra@mail01 ~]$ zmmtactl stop
/postfix-script: stopping the Postfix mail system
Stopping saslauthd...done.
[zimbra@mail01 ~]$ zmmtactl start
Rewriting configuration files...done.
Starting saslauthd...done.
/postfix-script: starting the Postfix mail system

-----------------------

check with this command

-----------------------

[root@mail01 ]# curl https://shellshocker.net/shellshock_test.sh | bash

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

  Dload  Upload   Total   Spent    Left  Speed

101  2627  101  2627    0     0    416      0  0:00:06  0:00:06 --:--:--  1957

CVE-2014-6271 (original shellshock): not vulnerable

CVE-2014-6277 (segfault): not vulnerable

CVE-2014-6278 (Florian's patch): not vulnerable

CVE-2014-7169 (taviso bug): not vulnerable

CVE-2014-7186 (redir_stack bug): not vulnerable

CVE-2014-7187 (nested loops off by one): not vulnerable

CVE-2014-//// (exploit 3 on http://shellshocker.net/): not vulnerable

ClearOS Resource Report Not Shown

 you will see the file configuration in this path

/usr/clearos/sandbox/etc/my.cnf.

vim /usr/clearos/sandbox/etc/my.cnf.

find following configuration and  updated them to :

---------------------------------------------

innodb_log_file_size=500M
innodb_log_buffer_size=64M

afterwards execute the commands:

----------------------------------------------

1. service system-mysqld stop
2. mv /var/lib/system-mysql/ib_logfile* /tmp
3. service system-mysqld start

after entered these values, restarted the databases, and after about 10 minutes, the reports started working again.

tutorial yang sangat mudah di ikuti.

when i check the status of replication, i got this status :


[root@ldap conf]# /opt/zimbra/libexec/zmreplchk
SSL_ca_path /opt/zimbra
/conf/ca does not exist at /opt/zimbra/zimbramon/lib/IO/Socket/SSL.pm line 377.
[root@ldap conf]#


use this command to edit the script


vi /opt/zimbra/libexec/zmreplchk



A workaround is to add following line:

chomp $val;

After this line:

my $val=`$c{zmlocalconfig} -x -s -m nokey ${key} 2> /dev/null`;

And that fix the issue. 

Let me know if how it goes.