• Quick Installation Guide
  • Step by Step
  • Admin User Guide
01. Introduction
  • Presence of the Machine
02. Hardware Requirement
03. Acquire the Software
04. System Configuration
05. Recover System via RAID
06. FAQ

The Presence of the Running Machine on the Internet

Everything has a start, and has an end.

Deploying a server over the Internet is different from setting up a local server without being revealed to outside people. For a server to be unknown on the Internet by fully-qualified hostname, it requires some registration processes. Furthermore, since the server is known to the public, some security measures should have been taken to avoid the abuse of the server.

This package includes basic elements for network operation, for example, DNS, FTP, firewall, backup storage server, VPN (Virtual Private Network) and Email .

We start from the introduction on Domain name registration with the following diagram:

1. Purchase domain name from the “vendor for domain name registration”

The “Domain Name Registration Vendor” usually will provide a Web interface for you to query your desired domain name. You may find some of the domain names you like have been acquired by other people. It is necessary for you need to find a domain name that is not being occupied. And then make the purchase of the domain name from the “Domain Name Registration Vendor” to complete this step.

2. Purchase Internet bandwidth and obtain “static” IP addresses from your local ISP (internet service provider).

Usually, the ISP will give you a set of IP addresses that may include a list of public IP addresses, the netmask, and the default Gateway. This IP information will be used when you install the software and configure your server. You shall keep the information in a safe place once you obtain that from your ISP.

3. Find a legitimate “DNS host provider”

It is to host your domain name (which you get from step 2) and the associated static IP address (which you get from step 3) record so that everybody on Internet can use your domain name to reach your server. Usually, the “DNS host provider” will provide a Web interface to allow you to input your domain name and the mapped IP address record into their hosted server. This step is completed after you have entered the data into the web page.

4. Update the record at the “Domain Name Registration Vendor” server with the IP addresses of the “DNS host provider”.

At this step, you need to access the website provided by “Domain Name Registration Vendor”. If you do not know the DNS server’s IP addresses of your “DNS host provider”, you can do as follows at your Windows command prompt (the command prompt is reached through Start > Run > cmd), issue the command

  C:\>nslookup DNS-server- name-from-your-provider

The system will respond with the IP address of your “DNS host provider”. Usually, you need to find two IP addresses of the two DNS servers provided by “DNS host provider” (one is called primary DNS host server, the other is secondary DNS host server). The two IP addresses will be entered into the record in the place of “Domain Name Registration Vendor”. We suggest using primary DNS server and secondary server from different places. The Azblink server package also provides DNS server. But to allow people all over the world can query your domain, you should have your domain name placed in different DNS servers to alleviate the load.

5. Wait until it is in effect.

In general, it needs 24 hours to 72 hours to have your domain name record of the server populated across the world so that people can use domain name to access your server.
Those are the general steps as long as you want to have your own private server(s) on Internet.


Basic Web Setting

After the system installation be finished, take the CD out, reboot the machine, and then start the basic network setting for the system.

There are two modes to configure the host, one is console mode on the local host, and the other is Web interface mode on Client. You can choose the one you like or just by the network environment of that time.

Console Mode --- configure on local host

A. Input account and password to login into console configuration interface.


B. You will see 7 options after login in

 1. IP Address:
 2. Netmask:
 3. Default Gateway:
 4. Save and Reboot
 5. Reset to CD setting (DHCP) and Reboot
 6. View Current Active Values
 7. Exit without Saveing Changes

C. Is there any fixed ip ready for configuration?

  Yes, type fixed IP address, Netmask and Default Gateway into option 1.2.3. severally. You can use up
  and down arrow to choose the option who needs edit, and then press enter to configure. After option 1.2.3
  be correctly configured, you can use option 4 to save these changes and reboot the machine. (If you have
  no idea about the Netmask and Default Gateway, you can just refer to the Completion List provided by your

  No, if there is a DHCP server providing the IP assignment services in your network, you can just use option6
  to check the IP address assigned by the system. After checking eth0, please write down the IP address, and
  remember to use option 7 to quit the Console interface.

D. By the IP address you set or the one obtained from DHCP, you can view the configuration page of the
   system host via Web browser on remote Client.

※ DHCP server exists in your network, but if you find eth0 shown as IP when you check current system value, please check if your network cables plug into wrong place (eh0 and eth1 may been exchanged), or if there are some problems on other equipments. (Refer to Q&A in the manual)

Web interface Mode --- configure at sub-network

A. Is the host, which you installed system on, connected by other hosts?

  Yes, please confirm the host is the only DHCP sever (that is to say the network should not have other
  DHCP servers, e.g. IP distributor), and then start from C.

  No, please complete basic network configuration according to B’s instruction.

B. A network cable makes host’s eth1 port and the Hub connected. And use another cable to connect to
  Hub, let the other end of this cable link to a common Client computer.

C. Choose one Client computer from the sub-network which connected to the system host.

D. Open command prompt on the Client (suppose it’s a Windows machine), type “ipconfig” and then press
 “Enter” button, check whether the Default Gateway is or not?

  Yes, just close the command prompt, enter into next step.

  No, type “ipconfig/release” to release the old IP in your computer, and then type “ipconfig/renew” to get
  new assigned IP.
  (If you are still unable to obtain new IP, please check if the network has other DHCP sever or not, or maybe
  TCP/IP of this Client does not use the mode of “Obtain an IP Address Automatically”.)

E. Open your Browser, and type at the address bar to link. When you visit the page at the
  first time, you will see 4 items;

  Host Name:Please set Host Name for this host.
  Admin Password:Default password is admin123.
  New Admin Password:Please set new password.
  Confirm Password:Please confirm your new password.

F. After you enter into system page, go to System>>Network, choose Internet or PPPoE depending on the

  Choose Internet. At the Internet Interface, mostly, you should set the values for IP address / Netmask /
  Default Gateway and then submit, restart your machine and you will find it already connected to Internet.

  Choose PPPoE. If you use PPPoE, remember to check the checkbox of “Turn on PPPoE”. Fill in the account
  and password provided by ISP and submit, reboot your computer, then you can connect to the network.
  (Please refer to the sections of Configuration and Q&A in Quick Installation Guide if you have any questions.)



Let’s start with the following scenario. Assume your office network is protected by a firewall with NAT ( Network Address Translation ). The internet access interface of the firewall is with public IP addresses; on its access of the local office network, private IP addresses (,, ) are used.  This is a very typical case in the office.  While the box firewall resides does not have the capability to install other software, usually, we put the application ( e.g. Mail server ) is a separate box and use “port forwarding” to forward the associated traffic from internet to this box.

Since most of the firewalls earlier only support the manipulation of traffic up to the layer TCP/UDP/IP, it does not have processing logic on higher-layer application. In this case, the Mail Server in the diagram above usually accepts the traffic associated with TCP port 25 of a specific public IP address. The firewall just forwards the traffic with matched destination IP address of destination port TCP 25 to this Mail server; it does not process any email related protocols based on TCP port 25 ( known as SMTP ).

The scenario can work pretty well. But as time goes by, you have more and more users for that Mail Server. The response of that Mail Server turns out slower than before. Slower response of Mail Server could be due to network bandwidth issue, the processing power of Mail Server, or the storage space.  Usually, the network bandwidth issue on the local office network needs to re-partition the subnets carefully and put different people into different subnets. If it happens to the bandwidth of the internet access, you might think to upgrade the internet access of your office. However, for pure email application for your office people, it would be more often to have the need to add more processing power or storage space for email application.

Simply replacing the existing Mail Server by using more powerful machine does not make sense because the current machine is not broken yet. It still functions; it just can not take more load. To protect the existing investment, it would be reasonable to add one more machine and let the two machines work together. We will elaborate more on the solutions for this kind of problems.

Let’s put more requirements on that:  the firewall is only with 1 public IP address provided by ISP. And it is intended to add one more Email server in the office network inside the firewall. We just summarize the information as the following example:

-Domain name:  zzzzzz.com ( let’s assume this is a legal domain name )
-Public IP address:
-Since there is no other public IP address provided, the MX record of public access DNS server can only be set to .
-Private IP address of Mail server inside firewall:
- Port forwarding in firewall is turned on to forward the traffic with destination IP address TCP port 25 to .

With the existing information here, we will explore the possible solutions.


Possible Scalable Solutions

(Remember: Only 1 public IP address is available when thinking up solutions.)

Solution I: Email Alias ( + Internal DNS server )( Bad Solution )

Usually, “port forwarding” can only forward the traffic of specified IP address with TCP/UDP port only to one machine. In order to have emails distributed to several machines, we need processing logic in application layer ( on email protocols ).

Email Alias is one of the methods to forward an email arrived at a specific alias to one email account or many email accounts.

In Mail Server A, it might be possible to have n user email accounts already. Starting with (n+1)th user, the account is going to be added in Machine B. In Mail Server A, we need to have an alias ( for example, “user101” ) and this alias will have the following information:

Alias user101 at Mail Server A  à  user101 at machine B

Usually, it is just adding an email account to alias “user101” at Mail Server A. In old days, email accounts could be of the form  user101@ipaddress. ( e.g: user101@ ) . But nowadays, most of the email servers will not accept this kind of email account. Thus, at least, you should put an email address like user101@b.fakeddomain in the mail alias “user101” of Mail Server A.  This “fakeddomain”(e.g.: private.z  ) is something that can not be queried from the Internet DNS server; you only can put them into the DNS server for your private network.

It is not done yet.  Machine B also needs to be configured to accept email address like user101@b.private.z .

However, all of the users should not be aware of things like “b.private.z”; they will use their emails like  user101@zzzzzz.com to the users inside the company or other people’s email accounts on the internet.

Obviously, this is not a good solution; it involves with too many details and it is very difficult for maintenance. For example, how do the users in machine B send emails to Mail Server A ?  Each of the two machines is Mail server and recognizes itself as “zzzzzz.com”. You might need to do similar things by adding the users in Mail Server A to the alias list in machine B.

The following solution is what we suggest by using our Enterprise Email Server.

(Remember: Only 1 public IP address is available when thinking up solutions.)

Solution II: (recommended solution)

In the following diagram, Mail Server A is Azblink Enterprise Email Transport server. We are going to add a new servers for HR department and Engineering department.  The users at Mail Server A are with email account of the format  user@zzzz.com,  the users on Mail Server B are with email account of the form user@hr.zzzz.com , and users on Mail server C are with the format xxx@eng.zzzz.com.

Outside the firewall, zzzz.com ( or mail.zzzz.com ), hr.zzzz.com, and eng.zzzz.com  are pointing to the same IP address . And the port forwarding on the firewall is set as previous.  The newly-added server B for HR department is with private IP address inside the firewall; mail server C for Engineering department is with IP address

On machine B, the outgoing emails need to be configured as the address like user@hr.zzzzzz.com. This can be done by setting as follows in Azblink Enterprise Email server menu: Email->Basic->Domain/Host

Domain Name Specific for Sending Mail:  hr.zzzz.com
Host Name Specific for Sending Emails:   hr.zzzz.com

On machine A, it is
Domain Name Specific for Sending Mail:  zzzz.com
Host Name Specific for Sending Emails:   mail.zzzz.com
( if your original setting for mail server is as “mail.zzzz.com” in MX record of public DNS registry )

And you need to put all the host names or domain names that you allow this host to receive emails in the box “Hostname(s) or domain names to be used to receive emails”. It will receive emails with those domain names.

On machine C, it is

Domain Name Specific for Sending Mail:  eng.zzzz.com
Host Name Specific for Sending Emails:  eng.zzzz.com

It needs to do one more thing on machine A from Web management interface: Email->Advanced->Mail Transport:

Turn on “Transport to other host(s)”.

Add “Sub-domain” with “hr.zzzzzz.com” with private IP address “” and “eng.zzzz.com” with IP address into the list.  Then all the emails with the form XXX@hr.zzzz.com will reach machine A first, and then, machine A will transport those emails to machine B.  Similarly for those emails with address XXX@eng.zzzzz.com will be transported to machine C.

The benefit of this configuration is: when you add new users on machine B for HR department, you do not have to go back to machine A to add anything.

If you want to have another new server for Sales Department with email address like  XXX@sale.zzzz.com, you can just following the similar way to do it. Remember: this is under the condition that you only have one public IP address so that we have to distribute emails in this way.

(Remember: Only 1 public IP address is available when thinking up solutions.)

At the admin menu Email->Advanced->Mail Transport, there are some settings for Transport filter. It can be used to save emails being “received” or “sent via relay”. Spam email tagging and filtering to prevent from the spam email being propagated to the next mail hop are also there.  “Saved Pass-by Emails” can be found under the directory  /home/filter of the server where the Web UI is associated.


Mail Filter – spam tagging, filtering, or saving pass-by emails


Deploy a Mail Transport Filter in front of existing mail server

Azblink Enterprise Mail Server can be working as an independent mail filter for Spam Mail filtering and Virus Scan by deploying it along with other mail server. For example, in the following diagram, all the inbound emails will arrive at Mail Server A at first. And then, those inbound emails will be delivered to the final destination Mail Server B. In this case, A is acting a pure mail filter because it is not the “final destination” of any emails.

Assume that machine B is your “original mail server” without the functionalities for handling Spam Mails or Virus Scan; machine A can be introduced for handling the tasks for Virus Scan on emails or filtering Spam mails only. The users still interact with machine B directly for sending or receiving emails as usual and let the machine A handle Spam Filtering and Virus Scan for emails.

Assume that machine B is your “original mail server” without the functionalities for handling Spam Mails or Virus Scan, machine A can be introduced for handling the tasks for Virus Scan on emails or filtering Spam mails only. The users still interact with machine B directly for sending or receiving emails as usual and let the machine A handle Spam Filtering and Virus Scan for emails.

Mail Transport Filter for Multiple Mail Servers

In the diagram above, B, C, and D are mail servers. Letting A handle Spam Mail Filtering/Tagging seems a good choice. But Virus scanning shall be done on B, C, D to let the processing load be distributed to multiple servers.  There is no definite rule about which function shall be done in a specific place – it depends on the characteristics of the processing power and arrival rate of emails.  Usually, when one task can not be done in one server, we distribute that task to other machines and let multiple machines handle that task.

For example, if you turn on Spam Mail Filtering on and Virus Scanning on machine A, it might be working well when the volume of emails is light. However, it might take very long time to process the incoming emails if the arrival rate of emails is very high.  So, it is not appropriate to handle everything on A; it is necessary to distribute the processing load to other servers.

Use as Mail Logger to Save any pass-by Emails for Mail Auditing

Here we introduce a scenario for using “Save pass-by emails” for Mail Audit along with other network equipments provided with other vendors. In the diagram below, the firewall is provided by Checkpoint; followed by Mail Spam Border Control provided by Barracuda. After that Microsoft’s Exchange server is used to received emails. Barracuda’s box is to screen all the junk emails before those junk emails reach Microsoft’s Exchange Server. All the other users are interacting with MS Exchange server directly to send/receive emails.

The purpose is to use a separate box to save extra copy of any emails before those emails arrive at MS Exchange server so that those emails can be kept for auditing purpose.  To log all the arriving emails, we can deploy this “Mail Transport Filter” as “Mail logger” between Barracuda’s mail filter and MS Exchange.

So, previously, Barracuda’s mail filter delivered emails to MS Exchange Server; it needs to change its destination to Azblink’s box. Of course, you need to allow the box to receive emails from Barracuda’s machine with specifying correct domain names to receive emails ( it can be done via Email->Basic->Hostname/Domain name ).  In Azblink’s box, use “Email->Advanced->Mail Transport”. You can follow the instruction in our previous example to deliver the emails to MS Exchange server. To act as “Mail Logger”, click the checkbox on “Mail Transport filter” for “save pass-by emails”.  This is for Inbound emails.

For outbound emails, it is necessary to make sure the outgoing emails from MS Exchange server will go through Azblink’s box. It can be done by using “relay”. On MS Exchange server, it is acting as “relay client” to Azblink’s box by setting its relay host ( “Smart host” in its term ) on MS Exchange server.  In “Email->Advanced->Relay Control”, it should be set to allow emails coming from MS Exchange server.

Thus, all the outgoing/incoming emails have extra copy on the Mail Logger.

To view those saved emails, you can use user account “filter” from Webmail interface to view those saved emails. Those emails are arranged by YYYYMM/DD so that you can select those folders to browse the emails on a specific date. Furthermore, you can specify Search criteria with Sender and Receiver names on the mail header to find out the historical emails in the organization.

The account “filter” is also established in “Samba”. You can use it to copy the those folders for data backup and delete those folders on the Mail Logger. It is necessary to avoid the space of hard drive is filled up.

Web Mail Configuration

Web AP Proxy via directory

In the previous discussion, we did not mention anything about how to access those machines for users outside the firewall. The difficult is on that we work under the situation that only 1 public IP address is available.  Thus, those methods like “port forwarding” from firewall to multiple machines located inside firewall need the existence of multiple public IP addresses to forward the traffic to different machines given the same TCP port number ( SMTP or POP3 ).  Unless you want to use different ports for SMTP and POP3, that solution does not fit into this case.

This question shall be resolved by using the logic in application layer. The method introduced here to allow people access their email boxes located on different machines inside firewall is via the logic on http. The concept is quite simple: we map a host to a directory of another host which can be accessed via http from the network outside the firewall.

Let’s use the following diagram to explain more details. A, B, and C are three hosts located inside the firewall with private IP addresses,, and respectively.

For incoming Emails, we can use “Mail Transport” to distribute Emails to machine A, B, and C.  To let users access the mail boxes on A, B, or C from the network outside the firewall, we do the following mapping on http requests:

If the requests are of the type http://zzzzzz.com/hr, the http requests will go to machine A.  Similarly,

http://zzzzzz.com/eng  → ( )
http://zzzzzz.com/it → ( )

In other words, every URL stemmed from http://zzzzzz.com/hr will be processed by machine A.  For example if a person issues http://zzzzzz.com/hr/apps/ from the place outside firewall, the webpage being displayed to this person is the page located the web directory “/apps/” on A ( ). It looks like the content on machine A appears under a certain web directory of the web host zzzzzz.com via http://zzzzzz.com/dirName .

Azblink’s Enterprise platform is able to do this kind of mapping so that all the hosts behind the firewall can be mapped to web directories on a public access web server. So, this group of machines will look as one machine when you issue http request.  And it can be done via the following steps on Web GUI of firewall machine:

Browse via System->Web->Proxy Map :
Remote Web URL:
Mapped local web directory: /hr

Thus, the request http://zzzzzz.com/hr will go to machine A ( ) and the web page will be displayed back to the web browser you issue the request.

When you want to apply this approach to access web applications on the machines inside the firewall, the web applications shall avoid using http://machineName/path/ while trying to refer the webpage or action for the html form on the same host. Using “relative path” instead of “absolute path” to refer the web pages on the same host will make the web application work smoothly under this scenario.  Then, there is no tweak to be done for this web application to function well by using this method.

Web Mail Configuration under Web directory proxy

Unfortunately, Web Mail does not fulfill the requirement above by using “relative path”; it needs some tweak to function well under the scenario mentioned above.  On machine A, browse via Email->Advanced->Web Mail Proxy:

How do people access the host via that Web directory proxy method? “http://zzzzzz.com/hr” . Then, just type that information and press the checkbox to turn on adjustment and submit. So, the web mail on machine A can be accessed via


Similarly, B and C can be accessed via

Combining “Mail Transport” and Web mail via Directory Proxy, the 1-public-IP address solution for multiple machines inside firewall is complete.