Discover Servers and Set a Server's IP Address
Discover Servers and Set a Server's IP Address
Use the Brainsalt Hub app to find every Brainsalt server on your network and set or correct its IP address. This works even when a server's current IP is wrong or on the wrong subnet.
[USER-ACTION-REQUIRED: Attach a screenshot of the Brainsalt Hub app showing the server list with at least one discovered server, including the IP Config button]
Before you start
- The Brainsalt Hub app is installed on your workstation (Windows)
- Your workstation is connected to the same physical network (Ethernet) as the target server
- You have administrator credentials for the target 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 Brainsalt Hub app and sign in
Launch the Brainsalt Hub app on your workstation. Sign in with the username and password configured on your servers. If the servers are fresh out of the box, click Skip to sign in with the factory default credentials.
Your Hub login must match a user account on the servers. This is the same username and password you would use to log in to a server's System Management web interface.
2. Find your server in the list
The Hub automatically discovers every Brainsalt server on the local network. Each server appears as a row showing its hostname, IP address(es), and a status indicator:
-
Green dot — core software running.
-
Dark dot — core software not responding (server is on but software is not running, or it is unreachable).
-
"not on a local subnet" warning — the server was discovered but its current IP is on a different subnet than your workstation. You can still change the IP.
Discovery uses a raw Ethernet mechanism (BSMD protocol) that operates below the IP stack. This is why the Hub finds servers even when their IP address is misconfigured, on the wrong subnet, or completely unreachable by normal means.
3. Open IP Config
Select the server, then click the IP Config button in the action bar. A dialog opens showing the server's hostname, all its network adapters (one section per adapter, identified by MAC address), and a BMC section.
[USER-ACTION-REQUIRED: Attach a screenshot of the IP Config dialog showing the adapter fields and the Apply button]
4. Set a static IP address
For the adapter you want to configure:
-
Make sure the DHCP checkbox is unchecked.
-
Enter the desired IP address, Subnet mask, Gateway, and DNS server.
-
Click Apply.
The change is sent over the discovery channel, authenticated with your Hub credentials. A status message confirms success or failure. If the IP address and subnet you entered are on a local subnet, the "not on a local subnet" warning clears on the next discovery cycle (within a few seconds).
5. Switch to DHCP (alternative)
To let the server obtain its address from a DHCP server instead:
-
Check the DHCP checkbox. The IP fields are disabled.
-
Click Apply. The server requests an address from the DHCP server. The new IP appears in the server list once assigned.
In production AV installations, use static IPs. DHCP leases can change between reboots, breaking automation, control system integrations, and observer/sync links.
6. Rename the adapter (optional)
Each adapter shows a Connection name field with the Windows network connection name. Change the name and click Rename to relabel the adapter on the server (for example, "MEDIA" or "CONTROL"). This takes effect immediately.
7. Change the hostname (optional)
The Host name field at the top of the IP Config dialog lets you rename the server. Enter the new name and click Apply. A reboot is required for the new hostname to take effect.
Options explained
|
Setting |
Description |
Values / Range |
|---|---|---|
|
Host name |
The Windows computer name for this server. Requires a reboot to take effect. |
Text (Windows hostname rules) |
|
DHCP |
When checked, the adapter obtains its IP from a DHCP server. When unchecked, you set a static IP. |
Checkbox |
|
IP address |
The IPv4 address to assign to this adapter. Highlighted with a warning if the address is 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 |
Default gateway for the adapter. |
Dotted IPv4 |
|
DNS server |
DNS server address. Can be left empty if DNS is not needed on this network. |
Dotted IPv4 (optional) |
|
Connection name |
The Windows network connection name for this adapter. Rename to identify adapters by role (e.g. "MEDIA", "CONTROL"). |
Text |
Common Mistakes
-
Server not appearing in the list — The discovery protocol requires Ethernet. It does not work over Wi-Fi. Make sure your workstation is on the same physical Ethernet network as the server. If you are on a different VLAN with no Layer 2 path, the broadcast cannot reach the server.
-
"No challenge response" error when applying — The server's System Management Service may not be running. Check that the server has fully booted and the service is active. On a fresh server, wait for the boot sequence to complete.
-
IP Config button is missing for a server — The button only appears for servers found via the BSMD discovery protocol. If the server is added manually or only visible via SSDP, IP Config is not available. In that case, use the server's System Management web interface (Network page) to change the IP.
-
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.
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 before opening IP Config.
-
Each server row in the list shows one entry per host, not per adapter. All of a server's adapters appear inside the IP Config dialog.
-
You can copy a MAC address from the IP Config dialog by clicking the copy button next to it. Useful when coordinating with network administrators.
-
The standalone
BSMDeviceDiscovery.execommand-line tool uses the same protocol and can serve as a fallback if the Hub is unavailable. -
The IP Config dialog also supports configuring the BMC (IPMI) IP address and VLAN settings, which is useful for setting up out-of-band management on a fresh server.
Related
How to Access the BMC KVM Console from Brainsalt Hub — How to access the BMC KVM console for remote desktop access to a server.
How to Control a PTZ Camera from Brainsalt Hub — How to control a PTZ camera from the Brainsalt Hub app.
