Group Assignment

Course Tittle System & Network Administration

Assignment Tittle Web and Proxy Server Configuration
Group 1

Group Name ID NUM & UID dept & prog

Desalegn Tadesse 019/12 ITDW
Lemlem W/Aregay 006/12 23231 ITDW
Marufa Mohammed 014/12 23232 ITDW
Mekwanint Demisse 012/12 02481 ITDW
Tesfaye Tadesse 039/12 ITDW
Henok Befikadu 01712 23101 Cs Deg We
Teshale Gobena 016/12 Cs Deg We
Mesafint Bogale 029/12 23146 Cs Deg We
Lidiya Teshome 071/12 24413 Cs Deg We
Meseret Abuto 010/12 23147 Cs Deg We

Submitted to

Inst Kb ..
Questions
What is a server?
In simple terms, it’s a powerful computer that is used to serve information and software to
employees, customers, and other computers. For example, if you have five employees in an
office each working on a different computer, they should all be able to access the same software
and documents. These are served from a central computer rather than having multiple versions of
the files stored locally on each machine.
Types of servers
 Secure email hosting
 Website hosting
 Proxy servers
 Document storage
 Hosting line-of-business applications
 Data backup and recovery.
How to set up a server for a business
there are some common steps you will need to follow.

Prepare. Before you begin, document your network. Record the names of users, IP address, hostname of each computer,
serial numbers, and locations. Check both the hardware specifications and software requirements of your server. You may find
that you need to upgrade the operating systems of computers on the network in order to connect them to the server. You will also
need to gather any items you need for the installation such as an ethernet cable and external hard drive.
 Install your server. If your server came with an operating system preinstalled, you can connect it to the network and
begin configuration. If not, insert the installation media (DVD, USB, virtual media) and follow the instructions to set up your
particular operating system.


Configure your server. As soon as possible after installation, set the server backup (you may need an external hard
drive), set up remote access to the server, and set sharing options. Set the server as a domain controller to allow all computers in
the network to join the new centralized environment and to allow the server to authenticate user credentials.


Complete the setup. Add a local admin account to each PC or Mac and connect them to the server. Set up printers and
connect them to the print server. Organize and upload the data and applications you wish to have on the new server, for example,
your accounting software.
Then when I am going to the assignment question

The term web server can refer to hardware or software, or both of them working together.
On the hardware side, a web server is a computer that stores web server software and a website's
component files (for example, HTML documents, images, CSS style sheets, and JavaScript
files). A web server connects to the Internet and supports physical data interchange with other
devices connected to the web.
On the software side, a web server includes several parts that control how web users access
hosted files. At a minimum, this is an HTTP server. An HTTP server is software that understands
URLs (web addresses) and HTTP (the protocol your browser uses to view webpages). An HTTP
 server can be accessed through the domain names of the websites it stores, and it delivers the
content of these hosted websites to the end user's device.
To learn how to enable IIS and the required IIS components on Windows Server, see the
instructions below.
1. Open Server Manager and click Manage > Add Roles and Features. Click Next.
2. Select Role-based or feature-based installation and click Next.
3. Select the appropriate server. The local server is selected by default. Click Next.
4. Enable Web Server (IIS) and click Next.
5. No additional features are necessary to install the Web Adaptor, so click Next.
6. On the Web Server Role (IIS) dialog box, click Next.
7. On the Select role services dialog box, verify that the web server components listed
below are enabled. Click Next.
8. Verify that your settings are correct and click Install.
9. When the installation completes, click Close to exit the wizard.
Configure a Proxy Server
A proxy is a server that acts as an intermediary between a protected Local Area Network
(firewall) and the Internet. Some home networks, corporate intranets, and Internet Service
Providers (ISPs) use proxy servers. The proxy server ensures that all data transmission between
the Internet and a user on the LAN is authorized.
If you are behind a firewall, you can use the advanced preferences to customize your access. You
can choose from the following:
 Use the proxy server settings in Windows Internet Options
 Bypass the proxy server settings in Windows Internet Options
 Configure the proxy server settings
Before you configure a proxy server, obtain the host name and port number of your proxy server.
If you do not know the host name or port number of your proxy server, ask your firewall
administrator.
Steps
1. Select Account > Preferences.
2. Click the Advanced button.
The Advanced Settings dialog box appears.
3. Select the Use these proxy server settings option.
4. Enter your proxy Server Address.
The proxy server address can be the server's name or IP address.
5. Enter the Port number.
Typically, this number is 8080.
6. Enter your User Name, if required.
7. Enter your Password, if required.
8. Click OK twice to save the proxy preference settings.
1.1.1 HTTP Server Configuration Basics
An HTTP server is a computer (software) program (or even a software component included in an
other program) that plays the role of a server in a client–server model by implementing the server
part of the HTTP and/or HTTPS network protocol(s)
An HTTP server waits for the incoming client requests (sent by user agents like browsers, web
crawlers, etc.) and for each request it answers by replying with requested information, including
the sending of the requested web resource, or with an HTTP error message.
An HTTP server may also have bindings to manage protocol extensions to HTTP (i.e. WebDAV,
etc.) or messages of other protocols enveloped into HTTP messages (i.e. SOAP, etc.) in order to
allow program-to-program communications.
Implementations of an HTTP server may vary in complexity, from a manageable tiny component
to a full featured program implementation of HTTP and other protocols, which maybe can run in
background, as one or more processes, etc.
An HTTP server can be found in any kind of computer, including embedded systems and super
computers, also because it is a required component to run web interfaces (web applications),
etc…
Difference b/n Web server and HTTP Server
The difference between the term web server and the term HTTP server is very subtle because the
two terms are almost synonyms
The first term (web server) somehow predates the second one and it refers to the purpose of
serving web content in the context of a World Wide Web environment which is oriented to the
interaction with human beings. That term may refer not only to the HTTP server software
component but also to the whole system (hardware and software) required to run a website.
The second term (HTTP server) has a technical origin bound to the software implementation of
the server part of the protocol and so that term is used more to refer to it as a software component
which can be used for many other purposes besides hosting public websites in Internet or even
private websites in Intranets or Extranets

Setting up a New HTTP Server

Note
These instructions assume that you are setting up system as an Apache HTTP server.

To set up an HTTP server:

1. Install the Apache HTTP server package.

# yum install httpd

2. Create the directory where you will copy the full Media Pack DVD image, for
example /var/www/html/OSimage/OL6.6:
# mkdir -p /var/www/html/OSimage/OL6.6

Note
 create the directory under the /var/www/html directory hierarchy so that
the httpd_sys_content_t file type is set automatically on all the files in the repository.

3. Edit the HTTP server configuration file, /etc/httpd/conf/httpd.conf, as follows:

a. Specify the resolvable domain name of the server in the argument to ServerName.
ServerName server_addr:80

If the server does not have a resolvable domain name, enter its IP address instead.
For example, the following entry would be appropriate for an HTTP server with
the IP address 192.168.1.100.
ServerName 192.168.1.100:80

b. If the directory to which you will copy the DVD image in not
under /var/www/html, change the default setting of DocumentRoot.

In this example, the DVD image will be copied

to /var/www/html/OSimage/OL6.6 so the setting of DocumentRoot can remain
unchanged.
DocumentRoot "/var/www/html"

c. Verify that the <Directory> setting points to the same setting as DocumentRoot.
d. #
e. # This should be changed to whatever you set DocumentRoot to.
f. #
<Directory "/var/www/html">

g. If you want to be able to browse the directory hierarchy, verify that

the Options directive specifies the Indexes option, for example:
Options Indexes FollowSymLinks

Note The Indexes option is not required for installation.

h. Save your changes to the file.

4. Start the Apache HTTP server, and configure it to start after a reboot.
5. # service httpd start
# chkconfig httpd on

6. If you have enabled a firewall on your system, configure it to allow incoming HTTP
connection requests on TCP port 80.

For example, the following command configures iptables to allow incoming HTTP
connection requests and saves the change to the firewall configuration:
 # iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
# service iptables save

1.1.2 Virtual Hosting

Virtual hosting is a method for hosting multiple domain names (with separate handling of each
name) on a single server (or pool of servers). This allows one server to share its resources, such
as memory and processor cycles, without requiring all services provided to use the same host
name. The term virtual hosting is usually used in reference to web servers but the principles do
carry over to other Internet services.
One widely used application is shared web hosting. The price for shared web hosting is lower
than for a dedicated web server because many customers can be hosted on a single server. It is
also very common for a single entity to want to use multiple names on the same machine so that
the names can reflect services offered rather than where those services happen to be hosted.
There are two main types of virtual hosting, name-based and IP-based. Name-based virtual
hosting uses the host name presented by the client. This saves IP addresses and the associated
administrative overhead but the protocol being served must supply the host name at an
appropriate point. In particular, there are significant difficulties using name-based virtual hosting
with SSL/TLS. IP-based virtual hosting uses a separate IP address for each host name, and it can
be performed with any protocol but requires a dedicated IP address per domain name served.
Port-based virtual hosting is also possible in principle but is rarely used in practice because it is
unfriendly to users.
Name-based and IP-based virtual hosting can be combined: a server may have multiple IP
addresses and serve multiple names on some or all of those IP addresses. This technique can be
useful when using SSL/TLS with wildcard certificates.
For example, if a server operator had two certificates, one for *.example.com and one for
*.example.net, the operator could serve foo.example.com and bar.example.com off the same IP
address but would need a separate IP address for baz.example.net.
we will be creating the virtual host for
domains: <body>
<h1>Success! The test2 virtual host is
1. Test1.com
working!</h1>
2. Test2.com
Step 1: Create a Directory Structure </body>
The first step is to create a directory structure </html>
used to store the site data that we will be Step 4: To \create the New Files for Virtual Host
serving to site visitors, or we will accept data These are the files that are having the actual
from visitors. configuration of our hosts. As we have already
So we are going to make the directories installed Apache, it comes with a default virtual
structure as follows under our document root ( host file which is known as 000-default.conf, and
/var/www directory) we will be making use of it.
sudo mkdir -p
/var/www/test1.com/public_html
sudo mkdir -p
/var/www/test2.com/public_html
Step 2: Permissions
As we have seen that the directory structure
that we have created are owned by the root
user. So if you want to change it in order to
modify the files in the web directories, we can
do it by following:
sudo chown -R
$USER:$YOUR_USER_NAME
/var/www/test1.com /public_html
sudo chown -R $USER:$
YOUR_USER_NAME /var/www/test2.com
/public_html
Step 3: Create Sample (Demo) Pages for
Each of the Virtual Hosts
Let us first create the sample/test page for
test1.com.
Open it with a vi editor or any editor of your
choice and do some HTML things!
vi
/var/www/test1.com/public_html/index.html
Once it is open, please write some basic
HTML code, save the editor and close it.
<html>
<head>
<title>Home Page of Test1.com<title>
</head>
<body>
<h1>Success! The test1 virtual host is
working!</h1>
</body>
</html>
Let us first copy that apache conf file to our first
domain:
sudo cp /etc/apache2/sites-available/000-
default.conf /etc/apache2/sitesavailable/test1.conf
When this is done, please open it with your
favourite editor.
It should look something like below:
<VirtualHost *:80>
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log
combined
</VirtualHost>
Here we need to change the email to replace it
with the email of the server admin.
ServerAdmin admin@test1.com
The next thing is to add 2 directives: ServerName
(This should be your domain) and ServerAlias. It
is achieved as:
ServerName test1.com
ServerAlias www.test2.com Finally, please
change the location of the document root of our
domain.
It can be achieved through: DocumentRoot
/var/www/test1.com/public_html.
Similarly, please follow the above procedures for
our second domain as well.
Step 5: To Enable Files of Virtual Host
We have newly set up our virtual files, and now
we need to enable them. This can be done via the
below command:
sudo a2ensite test1.com.conf
sudo a2ensite test2.com.conf
Once it is done, please restart our apache server:
sudo service apache2 restart
Step 6: Test your Results
Similarly, we can create the HTML page for Now it is time to test your results. Open up a web
the other website, i.e. test.com. browser and fire up the domain name of your
vi websites one by one, and you should see pages
/var/www/test2.com/public_html/index.html like below:
Once it is open, please write some basic
HTML code, save the editor and close it.
<html>
<head>
<title>Home Page of Test2.com<title>
</head>

1.1.3 HTTP Caching

What is HTTP Caching?
HTTP Caching is the idea of storing some commonly or frequently used data at someplace that is
quick to access. With this, there is a very good chance that most needed data can be accessed
much faster because the computer doesn’t have to reach too far to get it. In the case of Web
Browsing, caching is considered when your web browsers, such as Chrome, store a copy of a
website or web app on the local storage. Once a website is cached, a web browser won’t have to
redownload all the server data, which will make browsing a lot faster.

For example, once a website’s CSS file is downloaded, a browser does not have to download it
for every page of the session. The same can be said for many JavaScript files, images (such as
the Logo of the site and Social Media icons), and even some dynamic content. Caching is
enabled by using Cache headers.

Cache Headers in HTTP

HTTP Caching has two major cache headers, the first one is called “Cache-Control,” and the
second one is called “Expire”.

1. Cache-Control
You can consider Cache-Control as a Switch to toggle the caching on in the user browser. Once
this header has been added in, it enables caching for all supported web browsers. If this header is
not present, no browser will keep a cache of the web page contents even if it supports caching.
The Cache-control has two types of privacy settings, the first one is Public, and the second one is
Private.
2. Expires
The Expires header is used when Cache-Control is present in the code. This is a simple HTTP
Cache header that sets a date from which any cache resource is considered invalid. Once the
cache is expired and the user loads the website, a web browser will simply request all content of
the page once again.
Below are some uses cases of HTTP Caching which are as follows:

1. For Static Assets

For static assets of a page such as images, JS Files, and any CSS files, you can opt to
aggressively cache the contents. Not having to load these files will result in impressive
performance improvement. For this use case, go for the Cache-Control Header with the max-age
value of more than a month or even a year.

Cache-Control:public; max-age=31536000

2. For Dynamic Contents

In the case of a page’s dynamic contents, you will need to think yourself for what files should the
browser cache and for how long. In case the content is changed frequently, you will need to
make sure that the time duration you pick for caching won’t result in any problem for the user.

3. Caching of Private Content

As we discussed in the Cache-Control section, in case the content of the page is private in nature,
you can prevent it from being cached by intermediate proxies such as CDNs by adding “Cache-
Control: private” in the header. Another safer approach is to not cache any private content at all.
In the case of the Public, the resources can be cached by any intermediate proxy
In this process, the browser sends some data about resources it has cached into its memory, and
after reading this data, the server decides if the data is outdated or not.

1. Time-Based Requests
In time-based requests, it is checked if the requested resource was changed on the server or not.
If the cached copy in the browser is the latest, the server will return code 304.
To set Conditional Requests on a time basis, you can use “Last-Modified” in the response
header.

Cache-Control:public, max-age=25998579
Last-Modified: Fri, 08 Jul 2018 15:25:00 GMT

2. Content-Based
In Content-Based requests, the MD5 Hash (or any other viable option) is checked for both server
copy and cache copy. This tells if the data is the same or not; in case the data is different, the
MD5 checksum will not match, and the server will send a fresh copy of resources.

This is done via “ETag” in the header. The value of it is the digest of resources.
Cache-Control:public, max-age=25998579
ETag: "496d7131f15f0fff99ed5aae”

1.1.4 Proxy Caching Server Configuration

Definition
Proxy caching allows a server to act as an intermediary between a user and a provider of web
content. When a user accesses a website, proxies interpret and respond to requests on behalf of
the original server.

Overview
For much of the modern web, requests sent to a web service are handled by an intermediate
server. This intermediate – or proxy – server processes requests to determine how they should be
handled. Proxy servers allow enterprises to structure and safeguard their networks while
transparently providing additional features to users.

Proxy caching is a feature of proxy servers that stores content on the proxy server itself, allowing
web services to share those resources to more users. The proxy server coordinates with the
source server to cache documents such as files, images and web pages.

How proxy caching works

Proxies act as a gateway between the user and the source server, storing (or caching) the server’s
resources. When the user attempts to access a resource, the proxy checks to see if it has a recent
copy of the resource on hand. If so, the resource is immediately delivered to the user. If not, the
resource is retrieved from the source and simultaneously cached to the proxy and delivered to the
user.

Step-by-step, here’s how proxy caching works:

A user opens a webpage containing static content such as media, JavaScript or CSS.
The user’s browser automatically connects to a proxy server. This could be a content delivery
network (CDN) which caches content in various locations around the world.
The browser requests resources from the proxy server. The proxy server checks to see if it not
only has the resource, but if the resource is recent. If the resource is old or missing, the proxy
fetches a new copy from the source.
The proxy delivers the resource to the browser. If the proxy had to fetch a new copy, it caches
the copy for future use.
Once a proxy refreshes a resource, it resets the resource’s “expiration date” to prevent it from
being reflagged as out-of-date. The resource will be delivered as-is until a certain time passes, at
which point the proxy server will re-check the source.
Proxy cache states
Objects requested from a proxy cache can exist in one of three states: fresh, stale or nonexistent.
These states are determined by the age and availability of the object on the proxy server as it
compares to the source.

Fresh objects
Fresh objects are ready to be served in place of the original content. Freshness is determined by
metadata which defines either an expiration date or the maximum age of the object. Freshness
can also be determined using an aging factor based on the object’s last modification date.

Stale objects
Stale objects are cached objects that are no longer usable. Objects that passed their expiration
date or age limit have to be re-cached from the source server before they can be served by the
proxy. After encountering a stale object, the proxy simultaneously caches the updated object
from the source system and sends it to the user.

Nonexistent objects
Objects that exist on the server but not on the proxy follow the same procedure as stale objects.
If an object exists on the proxy but not on the server, then the proxy doesn’t serve the cached
copy.
Procedure

1. Configure the object cache instance for size, disk offload location, and other such
capabilities, in the administrative console. Click Servers > Server Types > WebSphere
proxy servers > proxy_server_name > HTTP proxy server settings > Proxy cache
instance config.

Repeat these steps on any nodes that have a proxy server.

2. Select the proxy cache store instance and enable configuration attributes such as cache
size, disk offload, and cache replication.

For disk offload, it is recommended that the location be set to a dedicated disk partition.

3. Enable caching at the proxy server, in the administrative console. Click Servers > Server
Types > WebSphere proxy servers > proxy_server_name > HTTP proxy server
settings > Proxy settings page in the administrative console.
4. Select Enable caching and choose a cache instance from the drop-down box.
1.1.5 Proxy ACL
Access control list (ACL) files are text files containing lists that define who can access Proxy
Server resources. By default, the Proxy Server uses one ACL file that contains all of the lists for
access to your server. Multiple ACL files can also be created and referenced in the obj.conf file.
how to control access to the Administration Server and the data served by the Proxy Server.
Access can be restricted to all data served by the server, or to specific URLs it serves. For
example, you can specify that only certain people access specific URLs, or that everyone except
those people can see the files. You might allow all clients to access URLs for HTTP, but allow
only restricted access to FTP. You could also restrict URLs based on host names or domain
names, such as when you have a Proxy Server serving many internal web servers, but want only
specific people to access a confidential research project stored on one of those servers.

Before access control can be used on the Administration Server, you must enable distributed
administration and configure an administration group in your LDAP database. The information
in this chapter is based on the assumption that those tasks have been performed.
Configuring a Basic ACL Rule
Basic ACL rules are defined based on whether the packets are the first fragments, packets' source
IP addresses, and VPN instances to filter packets.
Procedure
1. Run system-view
The system view is displayed.
2. Run acl { name basic-acl-name { basic | [ basic ] number basic-acl-number } |
[ number ] basic-acl-number } [ match-order { config | auto } ]
The basic ACL view is displayed.
3. Run rule [ rule-id ] [ name rule-name ] { deny | permit } [ fragment-
type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first }
| source { source-ip-address { source-wildcard | 0 | src-netmask } | any } | time-range time-
name | [ vpn-instance vpn-instance-name | vpn-instance-any ] ] *
A rule is configured for the basic ACL.
 Adding new rules to an ACL will not affect the existing rules.
 When an existing rule is edited and the edited contents conflict with the original contents,
the edited contents take effect.

When you configure a basic ACL:

 If a source IP address is specified by configuring source, the system filters only packets
with this specified source IP address.
 If all source IP addresses are specified by configuring any, the system does not check
packets' source IP addresses and considers that all packets have matched the rule and
directly takes an action (deny or permit) on the packets.
 If a validity period is specified by configuring time-range, the time range name specified
by time-name must already exist. Otherwise, the rule configuration fails.
4. (Optional) Run rule description text
The description for an ACL rule is configured.
 The description of an ACL rule can contain the functions of the ACL rule. Configuring a
description for an ACL rule is recommended to prevent misuse of the rule in the following
situations:
 A large number of ACLs are configured, and their functions are difficult to identify.
 An ACL is used at a long interval, and its function may be left forgotten.
5. Run commit
The configuration is committed.

1.1.6 Proxy-Authentication Mechanisms

Proxy Authentication enables you to configure the authentication method used by the proxy.
This determines how client machines are validated when accessing the Internet. Proxy
Authentication must be enabled to be able to create new policies for users or groups. By default,
Proxy Authentication is disabled. When Proxy Authentication is disabled, you are only allowed
to configure new policies using IP addresses. For enhanced security we recommend using
Integrated Authentication. This method is more secure since unlike Basic Authentication it does
not transmit user credentials over the network.

NOTE The Configuration Wizard is launched automatically after installing GFI WebMonitor or
manually from the Settings menu.

Proxy authentication settings

To configure user authentication method:

1. Go to Core Settings > Connection Settings.

2. Click the Proxy Authentication switch to enable.
3. In the Proxy Authentication area, select one of the following options:
Option 1: Leave Proxy Authentication off if the user is not required to provide login credentials
when new Internet sessions are launched.

Option 2: If proxy authentication is required, select one of the following options:

Option Description

Basic Select if user is required to provide login credentials when new

authentication Internet sessions are launched. When using Basic authentication, the
browser prompts the user for a user name and password. This
information is transmitted across HTTP as plain text and considered
insecure.

Integrated (Recommended) This option enables GFI WebMonitor proxy to

authentication authenticate users by using the client machine access control service.
User is not prompted to provide login credentials when new Internet
sessions are launched. We recommend using Integrated authentication
in a Windows domain environment since this method of
authentication does not transmit user passwords across the network.
NOTE
Integrated authentication is disabled if the GFI
WebMonitor machine authenticates local users as Guest. The Guest
only network access model grants all users the same level of access to
system resources and so GFI WebMonitor proxy will not be able to
differentiate between the different users using a client machine.
4. [Optional] In the IP's that will bypass the authentication field, key in IP addresses to
exclude from proxy authentication. IP addresses specified in this field will not be prompted
to provide login credentials when new Internet sessions are launched.
5. Click Save.

1.1.7 Troubleshooting

What is a troubleshooting means?

Troubleshooting is a systematic approach to problem solving that is often used to find and
correct issues with complex machines, electronics, computers and software systems. The first
step in troubleshooting is gathering information on the issue, such as an undesired behavior or a
lack of expected functionality
 If we say about troubleshooting we will see some errors or problems and troubleshooting steps
of web and proxy servers

Proxy errors signify that an Internet user is not allowed to visit a specific website or URL. This
restriction is set by the Internet administrator of the organization or by the website/URL creator
to protect private content, which is only meant to be viewed by specific people.
How can I troubleshoot Unable to connect to proxy server?
1. Reset Internet options
According to users, sometimes this error message can appear due to your Internet settings. This
can happen if you manually change your settings, but sometimes other applications can make the
changes without your knowledge.
To fix the problem, you need to reset your settings to default by doing the following:
1. Press Windows Key + S and enter internet options. Select Internet options from the
menu.

2. When the Internet Properties window opens, navigate to the Advanced tab. Now click
the Reset button.

3. Check Delete personal settings and click the Reset button.

After doing that, your Internet settings will reset to default and the problem with the proxy server
should be resolved.
2. Disable proxy

If you’re getting Unable to connect to proxy server error message, you might want to try
disabling your proxy. This is rather simple and you can do it by following these steps:

1. Open Internet Options window.

2. Go to the Connections tab and click the LAN Settings button.

3. Uncheck Use a proxy server for your LAN option and click on OK to save changes.

How To Troubleshoot When your site is down

Step 1 : Check the server status

Step 2 : Monitoring your server
Step 3 : Check the Logs
Step 4 : Make sure your web server is running
Step 5 : Verifying the Syntax of Web server
Step 6 : Is your Database back-end running Fine
Step 7 : Verify if your Web/App server is able to connect to Database backend
Step 8 : Make sure the Ports are open
Step 9 : Verifying the DNS Setting
We hopes so we do our bests