Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
nas:menu_network [2016/03/25 23:04]
danaromero [2.1 TCP/IP] 		nas:menu_network [2016/03/25 23:06]
danaromero [2.5 Host]
Line 40: Line 40:
 **Blink button: ** This feature is used to help identify NIC ports. Upon clicking this button, the physical LED on the selected NIC port will flash. This helps the user identify the physical port for each NIC port. **Blink button: ** This feature is used to help identify NIC ports. Upon clicking this button, the physical LED on the selected NIC port will flash. This helps the user identify the physical port for each NIC port.
 ===== 2.2 DNS ===== ===== 2.2 DNS =====
-{{ :​nas:​2_2_network_dns.jpg |}}+{{ :​nas:​2_2_network_dns.jpg?​direct ​|}}
  
 DNS - **D**omain **N**ame **S**ystem (DNS) is a database system that translates a computer'​s fully qualified domain name into an IP address. The computer system that runs the DNS functions is called the DNS Server. DNS - **D**omain **N**ame **S**ystem (DNS) is a database system that translates a computer'​s fully qualified domain name into an IP address. The computer system that runs the DNS functions is called the DNS Server.
Line 64: Line 64:
 **__Click “Apply” button save settings __ ** **__Click “Apply” button save settings __ **
 ===== 2.3 Bonding (Teaming) ===== ===== 2.3 Bonding (Teaming) =====
-{{ :​nas:​2_3_network_bonding_teaming_.jpg |}}+{{ :​nas:​2_3_network_bonding_teaming_.jpg?​direct ​|}}
  
 **Bonding ** is sometimes referred to as **Teaming. ** Its purpose is to bond multiple NIC ports together under the same IP to increase bandwidth and/or provide path redundancy. **Bonding ** is sometimes referred to as **Teaming. ** Its purpose is to bond multiple NIC ports together under the same IP to increase bandwidth and/or provide path redundancy.
Line 103: Line 103:
  
 ===== 2.4 Routing ===== ===== 2.4 Routing =====
-{{ :​nas:​2_4_network_routing.jpg |}}+{{ :​nas:​2_4_network_routing.jpg?​direct ​|}}
  
 **This function/​page is dedicated for those sophisticated users who have had multiple networks and gateways in their network environments. For those who don’t have multiple networks/​gateways,​ please disregard.** **This function/​page is dedicated for those sophisticated users who have had multiple networks and gateways in their network environments. For those who don’t have multiple networks/​gateways,​ please disregard.**
Line 114: Line 114:
  
 ===== 2.5 Host ===== ===== 2.5 Host =====
-{{ :​nas:​2_5_network_host.jpg |}}+{{ :​nas:​2_5_network_host.jpg?​direct ​|}}
  
 The “**Host**” function allows the association of a network client’s name with its IP and store it locally within the NAS. When it comes to finding a network client’s name/ip resolution, the NAS will first look it up locally according to this “**Host**” information,​ then, go to the DNS server. It is typically useful to enter your ADS server’s info here if intent is to join the NAS System to an existing ADS server. The “**Host**” function allows the association of a network client’s name with its IP and store it locally within the NAS. When it comes to finding a network client’s name/ip resolution, the NAS will first look it up locally according to this “**Host**” information,​ then, go to the DNS server. It is typically useful to enter your ADS server’s info here if intent is to join the NAS System to an existing ADS server.