How to Extend Linux Volume Group

Plain and simple of how to extend a volumn group in RHEL

Amusing you already added a Virtual disk and its presented to the server . If not check my this post.

[root@aurhel05 ~]# fdisk /dev/sdb

The number of cylinders for this disk is set to 3916.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sdb: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System

Command (m for help): n
Command action
e   extended
p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-3916, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-3916, default 3916):
Using default value 3916

Command (m for help): p

Disk /dev/sdb: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        3916    31455238+  83  Linux

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.
[root@aurhel05 ~]# fdisk -l

Disk /dev/sda: 32.2 GB, 32259548160 bytes
255 heads, 63 sectors/track, 3922 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         131     1052226   83  Linux
/dev/sda2             132         784     5245222+  83  Linux
/dev/sda3             785        1437     5245222+  83  Linux
/dev/sda4            1438        3918    19928632+   5  Extended
/dev/sda5            1438        1698     2096451   83  Linux
/dev/sda6            1699        1959     2096451   82  Linux swap / Solaris
/dev/sda7            1960        2220     2096451   82  Linux swap / Solaris
/dev/sda8            2221        2481     2096451   83  Linux
/dev/sda9            2482        2612     1052226   83  Linux
/dev/sda10           2613        3918    10490413+  83  Linux

Disk /dev/sdb: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        3916    31455238+  83  Linux

[root@aurhel05 ~]# mkfs.ext3 /dev/sdb1

mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
3932160 inodes, 7863809 blocks
393190 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
240 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

Extending the Volume VolGroup00-mysqldb by another 30GB :

1. Create a physical volume from a free disk or partition (e.g. /dev/sdb1 as a partition)
# pvcreate /dev/sdb1

2. Extend the volume group
# vgextend VolGroup00 /dev/sdb1

3. Extend the logical volume
# lvextend -L +30G /dev/mapper/VolGroup00-mysqldb

4. Extend an ext2/3/4 filesystem on the logical volume.
# resize2fs /dev/mapper/VolGroup00-mysqldb

 

How to protect your Family and Employee from internet Vulnerability ?

 

SquidGuard Configure

The best and easy way to install squidGuard is via YUM repo .Here how to do it .

1.With Squid working you can now go about installing SquidGuard.

You will need to install additional repositories in CentOS, in order to access to necessary software packages that are not available in the default repositories. Install the Extra Packages for Enterprise Linux (EPEL), the epel-release for the current version of Enterprise Linux (EL6). You can find it at the following website: http://fedoraproject.org/wiki/EPEL. A direct link to the RPM is in the command below. Eventually the link will be outdated and need to be replaced. For 64 bit systems you can change /i386/ to /x86_64/ in the command below.
# yum install http://ftp.osuosl.org/pub/fedora-epel/6/i386/epel-release-6-8.noarch.rpm

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

[root@aueq-sproxy02 ~]# yum install http://ftp.osuosl.org/pub/fedora-epel/6/i386/epel-release-6-8.noarch.rpm
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process
Examining /var/tmp/yum-root-8mVrB3/epel-release-6-8.noarch.rpm: epel-release-6-8.noarch
Marking /var/tmp/yum-root-8mVrB3/epel-release-6-8.noarch.rpm to be installed
Resolving Dependencies
–> Running transaction check
—> Package epel-release.noarch 0:6-8 will be installed
–> Finished Dependency Resolution

Dependencies Resolved

===============================================================================================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================================================================================
Installing:
epel-release noarch 6-8 /epel-release-6-8.noarch 22 k

Transaction Summary
===============================================================================================================================================================================================================
Install 1 Package(s)

Total size: 22 k
Installed size: 22 k
Is this ok [y/N]:

 

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

Now install SquidGuard.

# yum install squidGuard

 

[root@aueq-sproxy02 ~]# yum install squidGuard
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process
epel/metalink | 2.8 kB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.9 MB 00:00
Resolving Dependencies
–> Running transaction check
—> Package squidGuard.x86_64 0:1.4-10.el6 will be installed
–> Finished Dependency Resolution

Dependencies Resolved

===============================================================================================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================================================================================
Installing:
squidGuard x86_64 1.4-10.el6 epel 7.1 M

Transaction Summary
===============================================================================================================================================================================================================
Install 1 Package(s)

Total download size: 7.1 M
Installed size: 7.4 M
Is this ok [y/N]:

 

2. cd /var/squidGuard/

tar -zxvf blacklists.tar.gz

mkdir db

mkdir log

chown -R squid:squid db
chown -R squid:squid log

mv blacklists/* db/

chown -R squid:squid db/*

3. Now edit the squidGuard.conf file to configure it to work with the testdomains file. You may want to back up the squidGuard.conf file before making changes.

 

[root@aueq-sproxy02 db]# cp /etc/squid/squidGuard.conf /etc/squid/squidGuard.conf.BAK

 

# vi /etc/squid/squidGuard.conf —> and change as following.

 

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

# Mohammad Alam 23/09/2016
# initial conf file for squidGuard

logdir /var/squidGuard/log
dbhome /var/squidGuard/db

dest whitelist {
domainlist whitelist/domains
urllist whitelist/urls
}

dest specBlacklist {
domainlist specBlacklist/domains
urllist specBlacklist/urls
}

dest ads {
domainlist ads/domains
urllist ads/urls
}

dest adult {
domainlist adult/domains
urllist adult/urls
}

dest aggressive {
domainlist aggressive/domains
urllist aggressive/urls
}

acl {
default {
pass whitelist !specBlacklist !ads !adult !aggressive !audio-video !drugs !porn !chat !warez !phishing !malware !in-addr all
redirect http://10.80.0.37/ERR_ACCESS_DENIED.html
}
}

 

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

 

4. Add this line to /etc/squid/squid.conf

url_rewrite_program /usr/bin/squidGuard -c /etc/squid/squidGuard.conf

5. Reload squidGuard db

squidGuard -b -d -C all

6. Restart Squid.

/etc/init.d/squid reload

7. Check the log file at /var/squidGuard/log

[root@aueq-sproxy02 log]# ls
squidGuard.log
[root@aueq-sproxy02 log]# tail -f squidGuard.log
2016-09-26 11:11:51 [2388] squidGuard 1.4 started (1474852311.153)
2016-09-26 11:11:51 [2388] squidGuard ready for requests (1474852311.167)
2016-09-26 11:11:51 [2389] squidGuard 1.4 started (1474852311.160)
2016-09-26 11:11:51 [2389] squidGuard ready for requests (1474852311.171)

 

 

 

 

 

 

 

 

 

 

Snapshot creation failed.

Problem :

I experience this snapshot error with VEEAM backup and replication. For both  the error ,one single solution worked for me .

Error :

1) Consolidating virtual machine snapshots fails with the error: Change tracking target file already exists 

or

2) Creating Snapshot failed : The virtual disk is either corrupted or not a supported format.

 

Resolution :

To resolve this issue, the CBT files need to be moved out of the working folder of the affected virtual machine(s).

To move the CBT files and consolidate snapshots:

1. Connect to the ESXi host that the virtual machine is running on using SSH.
2. Navigate to the virtual machine folder using this command:

   cd /vmfs/volumes/datastore/virtual_machine/

3. List the contents of the directory using the ls command and look for .ctk files.
4. Create a temporary directory for the CBT files.

   For example:

   mkdir tmp

5. Move the CBT files to this directory with this command:

   mv *-ctk.vmdk tmp/

6. Run the snapshot  again.

Squirelmail Inbox error

Problem:

After signing in , I was getting the following error for one of the inbox ..

ERROR: Could not complete request.
Query: SELECT “INBOX”
Reason Given: Internal error occured. Refer to server log for more information. [2016-02-21 13:25:45]

 

Solution :

• Was checking the /var/log/maillog and got the following information –>  [Feb 24 16:05:18 griffin imap(appts.XXX): File isn’t in mbox format: /var/mail/appts.XXX]
• Then open the file with any text editor like vi /var/mail/appts.XXX
  then Delete the garbage lines(one or two) at the beginning and save the file.

  Restart the service and everything shloud be OK now.

Canot Start Sendmail

While trying to start sendmail it complains with the following error.

[root@augs-suatacd mail]# /etc/init.d/sendmail restart

Shutting down sm-client: [FAILED]
Shutting down sendmail: [FAILED]
Starting sendmail: 451 4.0.0 /etc/mail/sendmail.cf: line 87: fileclass: cannot open ‘/etc/mail/local-host-names’: World writable directory
451 4.0.0 /etc/mail/sendmail.cf: line 596: fileclass: cannot open ‘/etc/mail/trusted-users’: World writable directory
[FAILED]
Starting sm-client: /etc/mail/submit.cf: line 552: fileclass: cannot open ‘/etc/mail/trusted-users’: World writable directory
[FAILED]

Solution : 

Replacing line Fw/etc/mail/ local-host-names with line Fw-o /etc/mail/local-host-names in sendmail.cf, and Ft/etc/mail/trusted-users with line Ft-o /etc/mail/trusted-users in submit.cf and sendmail.cf.

Then restart Sendmail . Hope it will work.

Ashraf

Canot SCP to Checkpoint firewall

When you SCP to Checkpoint SPLAT firewall and get the error “lost connection”, this is what you may see

To resolve this do the following

1. make sure the admin shell has been changed from /bin/cpshell to /bin/bash

chsh admin
Changing shell for admin.
New shell [/bin/cpshell]: /bin/bash
Shell changed.

2. create a new file “touch /etc/scpusers”

3. edit the file and add the users you want to allow for scp

example:
more /etc/scpusers
admin

4. restart the ssh service ( I did not have to restart and it just worked)

service sshd restart

MAC Address Filter (MAC Authentication) on WLCs

Ref : http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008084f13b.shtml

MAC Address Filter (MAC Authentication) on WLCs

When you create a MAC address filter on WLCs, users are granted or denied access to the WLAN network based on the MAC address of the client they use.

There are two types of MAC authentication that are supported on WLCs:

• Local MAC authentication
• MAC authentication using a RADIUS server

With local MAC authentication, user MAC addresses are stored in a database on the WLC. When a user tries to access the WLAN that is configured for MAC filtering, the client MAC address is validated against the local database on the WLC, and the client is granted access to the WLAN if the authentication is successful.

By default, the WLC local database supports up to 512 user entries.

The local user database is limited to a maximum of 2048 entries. The local database stores entries for these items:

• Local management users, which includes lobby ambassadors
• Local network users, which includes guest users
• MAC filter entries
• Exclusion list entries
• Access point authorization list entries

Together, all of these types of users cannot exceed the configured database size.

In order to increase the local database, use this command from the CLI:

<Cisco Controller>config database size ?
<count>        Enter the maximum number of entries (512-2048)

Alternatively, MAC address authentication can also be performed using a RADIUS server. The only difference is that the users MAC address database is stored in the RADIUS server instead of the WLC. When a user database is stored on a RADIUS server the WLC forwards the MAC address of the client to the RADIUS server for client validation. Then, the RADIUS server validates the MAC address based on the database it has. If the client authentication is successful, the client is granted access to the WLAN. Any RADIUS server which supports MAC address authentication can be used.

Configure Local MAC Authentication on WLCs

Complete these steps in order to configure local MAC authentication on the WLCs:

1. Configure a WLAN and Enable MAC Filtering
2. Configure the Local Database on the WLC with Client MAC AddressesNote: Before you configure MAC authentication, you must configure the WLC for basic operation and register the LAPs to the WLC. This document assumes that the WLC is already configured for basic operation and that the LAPs are registered to the WLC. If you are a new user trying to set up the WLC for basic operation with LAPs, refer to Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC).

   Note: There is no special configuration needed on the wireless client in order to support MAC authentication.

Configure a WLAN and Enable MAC Filtering

Complete these steps in order to configure a WLAN with MAC filtering:

1. Click WLANs from the controller GUI in order to create a WLAN.The WLANs window appears. This window lists the WLANs configured on the controller.
2. Click New in order to configure a new WLAN.In this example, the WLAN is named MAC-WLAN and the WLAN ID is 1.

   

3. Click Apply.
4. In the WLAN > Edit window, define the parameters specific to the WLAN.
   1. Under Security Policies > Layer 2 Security, check the MAC Filtering check box.This enables MAC authentication for the WLAN.
   2. Under General Policies > Interface Name, select the interface to which the WLAN is mapped.In this example, the WLAN is mapped to the management interface.
   3. Select the other parameters, which depend on the design requirements of the WLAN.
   4. Click Apply.

The next step is to configure the local database on the WLC with the client MAC addresses.

Refer to VLANs on Wireless LAN Controllers Configuration Example for information on how to configure dynamic interfaces (VLANs) on WLCs.

Configure the Local Database on the WLC with Client MAC Addresses

Complete these steps in order to configure the local database with a client MAC address on the WLC:

1. Click Security from the controller GUI, and then click MAC Filtering from the left side menu.The MAC Filtering window appears.

   

2. Click New in order to create a local database MAC address entry on the WLC.
3. In the MAC Filters > New window, enter the MAC address, Profile Name, Description and the Interface Name for the client.Here is an example:

   

4. Click Apply.
5. Repeat steps 2-4 in order to add more clients to the local database.Now, when clients connect to this WLAN, the WLC validates the clients MAC address against the local database and if the validation is successful, the client is granted access to the network.

   Note: In this example, only a MAC address filter without any other Layer 2 Security mechanism was used. Cisco recommends that MAC address authentication should be used along with other Layer 2 or Layer 3 security methods. It is not advisable to use only MAC address authentication to secure your WLAN network because it does not provide a strong security mechanism.

Configure MAC Authentication using a RADIUS Server

Complete these steps in order to configure MAC authentication using a RADIUS server. In this example, the Cisco Secure ACS server is used as the RADIUS server.

1. Configure a WLAN and Enable MAC Filtering
2. Configure the RADIUS Server with Client MAC Addresses

Configure a WLAN and Enable MAC Filtering

Complete these steps in order to configure a WLAN with MAC filtering:

1. Click WLANs from the controller GUI in order to create a WLAN.The WLANs window appears. This window lists the WLANs configured on the controller.
2. Click New in order to configure a new WLAN.In this example, the WLAN is named MAC-ACS-WLAN and the WLAN ID is 2.

   

3. Click Apply.
4. In the WLAN > Edit window, define the parameters specific to the WLAN.
   1. Under Security Policies > Layer 2 Security, check the MAC Filtering check box.This enables MAC authentication for the WLAN.
   2. Under General Policies > Interface Name, select the interface to which the WLAN is mapped.
   3. Under RADIUS servers, select the RADIUS server that will be used for MAC authentication.

      Note: Before you can select the RADIUS server from the WLAN > Edit window, you should define the RADIUS server in the Security > Radius Authentication window and enable the RADIUS server.

      

   4. Select the other parameters, which depend on the design requirements of the WLAN.
   5. Click Apply.
5. Click Security > MAC Filtering.
6. In the MAC Filtering window, choose the type of RADIUS server under RADIUS Compatibility Mode.This example uses Cisco ACS.
7. From the MAC Delimiter pull down menu, choose the MAC delimiter.This example uses Colon.
8. Click Apply.

The next step is to configure the ACS server with the client MAC addresses.

Configure the RADIUS Server with Client MAC Addresses

Complete these steps in order to add a MAC address to the ACS:

1. Define the WLC as an AAA client on the ACS server. Click Network Configuration from the ACS GUI.
2. When the Network Configuration window appears, define the name of the WLC, the IP address, the shared secret and the authentication method (RADIUS Cisco Aironet or RADIUS Airespace).Refer to the documentation from the manufacturer for other non-ACS authentication servers.

   

   Note: The shared secret key that you configure on the WLC and the ACS server must match. The shared secret is case sensitive.

3. From the ACS main menu, click User Setup.
4. In the User text box, enter the MAC address in order to add to the user database.

   Note: The MAC address must be exactly as it is sent by the WLC for both the username and the password. If authentication fails, check the failed attempts log to see how the MAC is reported by the WLC. Do not cut and paste the MAC address, as this can introduce phantom characters.

5. In the User Setup window, enter the MAC address in the Secure-PAP password text box.

   Note: The MAC address must be exactly as it is sent by the WLC for both the username and the password. If authentication fails, check the failed attempts log to see how the MAC is reported by the AP. Do not cut and paste the MAC address, as this can introduce phantom characters.

6. Click Submit.
7. Repeat steps 2-5 in order to add more users to the ACS database.Now, when clients connect to this WLAN, the WLC passes the credentials to the ACS server. The ACS server validates the credentials against the ACS database. If the client MAC address is present in the database, the ACS RADIUS server returns an authentication success to the WLC and the client will be granted access to the WLAN.

Use the CLI to Configure the MAC Filter on WLC

This document previously discussed how to use the WLC GUI to configure MAC filters. You can also use the CLI in order to configure MAC filters on the WLC. You can use these commands in order to configure the MAC filter on WLC:

• Issue the config wlan mac-filtering enable wlan_id command in order to enable MAC filtering. bEnter the show wlancommand in order to verify that you have MAC filtering enabled for the WLAN.
• config macfilter add command:The config macfilter add command lets you add a macfilter, interface, description, and so forth.

  Use the config macfilter add command in order to create a MAC filter entry on the Cisco Wireless LAN controller. Use this command in order to add a client locally to a wireless LAN on the Cisco Wireless LAN controller. This filter bypasses the RADIUS authentication process.

  config macfilter add MAC_address wlan_id [interface_name] 
  [description] [IP address]

  Example:

  Enter a static MAC-to-IP address mapping. This can be done to support a passive client, that is, one that does not use DHCP and does not transmit unsolicited IP packets.

  >config macfilter add 00:E0:77:31:A3:55 1 lab02 "labconnect" 10.92.125.51

• config macfilter ip-address commandThe config macfilter ip-address command lets you map an existing MAC-filter to an IP address. Use this command in order to configure an IP address into the local MAC filter database:
  

  config macfilter ip-address 
  	 MAC_address IP address

  Example:

  >config macfilter add 00:E0:77:31:A3:55 1 lab02 "labconnect" 10.92.125.51

Configure a Timeout for Disabled Clients

You can configure a timeout for disabled clients. Clients who fail to authenticate three times during attempts to associate are automatically disabled from further association attempts. After the timeout period expires, the client is allowed to retry authentication until it associates or fails authentication and is excluded again.

Enter the config wlan exclusionlist wlan_id timeout command in order to configure the timeout for disabled clients. The timeout value can be from 1 to 65535 seconds, or you can enter 0 in order to permanently disable the client.

Verify

Use these commands in order to verify if the MAC filter is configured correctly:

The Output Interpreter Tool (registered customers only) (OIT) supports certain show commands. Use the OIT to view an analysis ofshow command output.

• show macfilter summary—Displays a summary of all MAC filter entries.
• show macfilter detail <client MAC Address>—Detailed display of a MAC filter entry.

Here is an example of the show macfilter summary command:

(Cisco Controller) >show macfilter summary

MAC Filter RADIUS Compatibility mode............. Cisco ACS
MAC Filter Delimiter............................. None

Local Mac Filter Table

MAC Address               WLAN Id          Description
-----------------------   --------------   --------------------------------
00:40:96:ac:e6:57           1              Guest

(Cisco Controller) >show macfilter detail 00:40:96:ac:e6:57

Here is an example of the show macfilter detail command:

(Cisco Controller) >show macfilter detail 00:40:96:ac:e6:57

MAC Address...................................... 00:40:96:ac:e6:57
WLAN Identifier.................................. 1
Interface Name................................... mac-client
Description...................................... Guest

Protected: How to Setup ownCloud 5 on Ubuntu 13.04

This content is password protected. To view it please enter your password below:

Password:

In View Administrator a View desktop has a status of “Provisioned (Missing)”

Experiencing this issue first thing in the morning while provisioning some VD in an existing pool . Then also tried to create a new pool and issue remains the same . Tried the following KB from vmware but doing some mistake at the end while editing pae_moid attribute . Please note you need to put vm-<MOID> to get it work . I need to log call with vmware support for this .

KB location : http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004269

In View Administrator a View desktop has a status of “Provisioned (Missing)”

Symptoms

• In View Administrator, a View desktop has a status of Provisioned (Missing).
• In vCenter, the View desktop is present and is fully functional.
• You cannot log in into the View desktop.

Cause

A common cause for this issue is if a vSphere/vCenter administrator had previously removed a View VM from inventory and later added it back into inventory. This can cause the View VM to get a different MOID (Managed Object ID) within vCenter. The VM’s MOID now differs between the vCenter database and VMware View’s ADAM database.

Resolution

To resolve this issue, you must make the VM’s MOID in the ADAM database match the vCenter MOID. To make the MOIDs match:

Note: The MOID in vCenter is in the form of a number. In the ADAM database, the number is preceded by vm-.

1. Determine the VM’s MOID within the vCenter Database:
   1. Connect to the vCenter Database.
   2. Execute this query:

      Select id from vpx_entity where name='<Name of the VM>'

      This returns the VM’s MOID as seen by vCenter.

2. Determine the VM’s MOID in the ADAM database on the View Connection Server:
   1. Log in to the machine hosting your VMware View Connection Server through the VMware Infrastructure Client or Microsoft RDP.
   2. Open the ADAM Active Directory Service Interfaces Editor:
      • Windows 2003: Go to Start > Programs > ADAM > ADAM ADSI Edit.
      • Windows 2008: Go to Start > All Programs >Administrator Tools > ADSI Edit.
   3. Right-click ADAM ADSI Edit and click Connect to.
   4. Ensure that Select or type a domain or server is selected and that Destination points to localhost.
   5. Select Distinguished Name (DN) or naming context
   6. Type dc=vdi, dc=vmware, dc=int.
   7. Run a query against OU=Servers, DC=vdi, DC=vmware, DC=int with this string:

      (&(objectClass=pae-VM)(pae-displayname=<Virtual Machine name>))

      Note: The <Virtual Machine Name> can use * or ? as a wildcard to match multiple desktops.

   8. Double-click the CN record for the VM you want to edit.
   9. Scroll down until you see the pae-MOID attribute.
   10. Double-click pae-MOID
   11. Change the pae-MOID to match the VM’s MOID as seen in vCenter.
   12. Restart the Connection Server service for the changes to take effect.