Configure Server Network Settings

Last updated 7 August 2026

Configure your Brainsalt server's network adapters, hostname, and management controller (BMC) network settings. You can do this from the Brainsalt Hub Desktop App — even when the server's IP is currently wrong — or from the server's System Management web interface once it is reachable on the network.

Watch: Video: IP Setup, Network and Host Name

Before you start

  • The Brainsalt Hub Desktop App is installed on your workstation, or you can reach the server's System Management web interface at https://<server>
  • You have administrator credentials for the server (factory default: ADMIN / ADMIN2!!)
  • You know the IP address, subnet mask, and gateway you want to assign (for static IP), or your network provides DHCP

Steps

1. Open the network settings

There are two ways to reach the network settings, depending on whether the server is already reachable on your network:

  • Hub IP Config — In the Brainsalt Hub Desktop App, select the server in the server list and click IP Config. A dialog opens showing the server's hostname, all its network adapters (one section per adapter, identified by MAC address), and a BMC section.

  • System Management Network page — Browse to https://<server>, sign in, and select Network under Configure in the sidebar. The page shows the same three sections: Host name, Host adapters, and BMC (management controller).

Use the Hub IP Config path when the server's IP is wrong or on a different subnet. It works below the IP stack and does not require the server to be reachable by normal network means.

2. Set a static IP address on a host adapter

For the adapter you want to configure:

  1. Make sure DHCP is unchecked (Hub) or Mode is set to Static (System Management).

  2. Enter the desired IP address, Subnet mask, Gateway, and DNS server.

  3. Click Apply.

In the Hub, a status message confirms success or failure. If the address you entered is on a local subnet, the server becomes reachable at that address within a few seconds.

3. Switch to DHCP (alternative)

To let the server obtain its address from a DHCP server instead:

  1. Check DHCP (Hub) or set Mode to DHCP (System Management). The IP fields are disabled.

  2. Click Apply. The server requests an address from the DHCP server. The new IP appears once assigned.

In production AV installations, use static IPs. DHCP leases can change between reboots, breaking automation, control system integrations, and observer/sync links.

4. Rename an adapter

Each adapter has an editable name (Connection name in the Hub, Adapter name in System Management). Change the name and click Rename to relabel the adapter on the server. This helps identify adapters by role — for example, "MEDIA" or "CONTROL". The change takes effect immediately.

5. Change the hostname

The Host name field (Hub) or Computer name field (System Management) lets you rename the server. Enter the new name and click Apply (Hub) or Rename computer (System Management).

A reboot is required for the new hostname to take effect. The System Management page offers to reboot immediately after applying.

6. Configure BMC network settings

The BMC (management controller) has its own network interface, separate from the server's host adapters. Configure it in the IPMI / BMC section (Hub) or the BMC (management controller) section (System Management).

  1. Set DHCP or Static for the BMC.

  2. If static, enter the BMC IP address, Subnet mask, and Gateway.

  3. Optionally enable VLAN tagging and set the VLAN ID (1–4094).

  4. Click Apply (Hub) or Apply BMC settings (System Management).

BMC settings are applied via IPMI, which is slower than host adapter changes. The BMC may briefly reset its network interface during the update.

Options explained

Setting

Description

Values / Range

Host name / Computer name

The Windows computer name for this server. Labelled Host name in the Hub and Computer name in System Management. Requires a reboot to take effect.

Text (Windows hostname rules)

DHCP / Mode

When enabled, the adapter obtains its IP from a DHCP server. When disabled, you set a static IP.

Checkbox (Hub) / Static, DHCP dropdown (System Management)

IP address

The IPv4 address to assign to this adapter. The Hub highlights addresses that are not on any of your workstation's local subnets.

Dotted IPv4 (e.g. 192.168.1.10)

Subnet mask

The subnet mask for the IP address.

Dotted IPv4 (e.g. 255.255.255.0)

Gateway

The default gateway for the adapter.

Dotted IPv4

DNS server

DNS server address. In System Management, multiple addresses can be comma-separated. Can be left empty if DNS is not needed on this network.

Dotted IPv4 (optional)

Connection name / Adapter name

The Windows network connection name for this adapter. Rename to identify adapters by role.

Text

VLAN

BMC only. Enables VLAN tagging for the management controller's network port.

Checkbox (Hub) / Off, On dropdown (System Management)

VLAN ID

BMC only. The VLAN tag for the management controller's network port. Only active when VLAN is enabled.

1–4094

Common Mistakes

  • Using DHCP in production — DHCP addresses can change between reboots, breaking control system integrations, timecode sync, observer links, and automation scripts. Always use static IPs for production installations.

  • Changing the IP of the adapter you are connected through — If you change the IP of the adapter the System Management session runs on, the session drops. Reconnect at the new address. The Hub IP Config path does not have this limitation because it operates below the IP stack.

  • Forgetting to reboot after changing the hostname — The new hostname takes effect only after a reboot. The server continues to respond to the old name until then.

Tips

  • The Hub highlights IP addresses that are not on any of your workstation's local subnets with a warning color. This is a quick way to spot misconfigured servers.

  • Use the Hub IP Config path to rescue a server with a completely wrong IP — it works even when the server is unreachable by normal network means.

  • Rename adapters by role (e.g. "MEDIA", "CONTROL") to make multi-NIC servers easier to manage.

  • The BMC IP is separate from the host adapter IPs. Setting up the BMC IP enables out-of-band management features such as the KVM console, power control via Redfish, and hardware health monitoring.

Discover Servers on the Network — how the Hub finds servers on the network, even when their IP is wrong.

Sign In to a Server for the First Time — how to sign in to a server's web interface for the first time.

Use the Brainsalt Hub Desktop App — the full Brainsalt Hub Desktop App guide.

Access the BMC KVM Console from Brainsalt Hub — how to access the BMC KVM console for remote desktop access.