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
network:specifications [2017/11/13 14:46]
go [Network Specifications] 		network:specifications [2021/02/02 14:31] (current)
Line 1: Line 1:
 <- network:​heterogenous|DHD System in Heterogenous Network ^ network:​start|Network Specifications ^ network:​guidelines|Guidelines for DHD Networks -> <- network:​heterogenous|DHD System in Heterogenous Network ^ network:​start|Network Specifications ^ network:​guidelines|Guidelines for DHD Networks ->
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
  
  
Line 21: Line 34:
   - Put all DHD systems on their own, physically or logically (VLAN) isolated network (DHD network). Connect all PCs running DHD applications with the office network. Make sure, no "​non-DHD UDP traffic"​ gets into the DHD network. **Never connect a DHD system directly to an existing office network**.   - Put all DHD systems on their own, physically or logically (VLAN) isolated network (DHD network). Connect all PCs running DHD applications with the office network. Make sure, no "​non-DHD UDP traffic"​ gets into the DHD network. **Never connect a DHD system directly to an existing office network**.
   - Always use **Ethernet Switches**, do not use hubs for networking.   - Always use **Ethernet Switches**, do not use hubs for networking.
-  - **Never** use configurable switches, i.e. **Managed Switches**, for networking DHD systems. Always network DHD systems via **Unmanaged Switches** only. If the IT infrastructure should already base on **Managed Switches**, //​nonetheless(!)//​ network DHD systems with the aid of **Unmanaged Switches** and, if necessary, uplink a port to the existing network. Please find a number of network switches tested by DHD in this Documentation. +/*   - **Never** use configurable switches, i.e. **Managed Switches**, for networking DHD systems. Always network DHD systems via **Unmanaged Switches** only. If the IT infrastructure should already base on **Managed Switches**, //​nonetheless(!)//​ network DHD systems with the aid of **Unmanaged Switches** and, if necessary, uplink a port to the existing network. Please find a number of network switches tested by DHD in this Documentation. ​*/ 
-  - Anyway, avoid using connections with a speed of 10 Mbit/s.+  - Avoid using connections with a speed of 10 Mbit/s.
   - If you are connecting a PC to a DHD system via a cross-over network cable, make sure you set the speed of the network adapter to "Auto Detect"​.   - If you are connecting a PC to a DHD system via a cross-over network cable, make sure you set the speed of the network adapter to "Auto Detect"​.
   - UDP broadcasts are only transmitted within the same IP subnet. If different DHD systems and PCs need to communicate with each other, they must have IP addresses within the same subnet.   - UDP broadcasts are only transmitted within the same IP subnet. If different DHD systems and PCs need to communicate with each other, they must have IP addresses within the same subnet.
   - If DHD systems are located within different IP subnets, **they can not exchange data using the UDP protocol**. However, you can still access these devices with a DHD application software by directly using their IP address.   - If DHD systems are located within different IP subnets, **they can not exchange data using the UDP protocol**. However, you can still access these devices with a DHD application software by directly using their IP address.
   - If you use routers, firewalls etc. in the network, make sure data traffic on **ports 2008, 2009 and 3008** is carried both on **TCP and UDP**.   - If you use routers, firewalls etc. in the network, make sure data traffic on **ports 2008, 2009 and 3008** is carried both on **TCP and UDP**.

© 2024 DHD audio GmbH | | Imprint | Privacy Agreement | General Terms & Conditions

Specifications and design are subject to change without notice. The content of this document is for information only. The information presented in this document does not form part of any quotation or contract, is believed to be accurate and reliable and may be changed without notice. No liability will be accepted by the publisher for any consequence of its use. Publication thereof does neither convey nor imply any license under patent rights or other industrial or intellectual property rights.