Assign a DHCP Address to a BMC Using Deepin Remote Boot Manager
This archived procedure uses Deepin Remote Boot Manager V1.3 (NetbootM.exe) as a temporary DHCP server on a direct laptop-to-BMC connection. The BMC must already be configured for DHCP. If it has a known static address, use that address instead; this method does not override a static BMC configuration. The seven figures are English recreations of the source.
1. Prepare an isolated direct connection
Connect the laptop directly to the server’s dedicated IPMI/BMC management port. Configure the intended laptop adapter with an address in the planned service subnet. The first example uses 192.168.78.1 with mask 255.255.255.0; gateway and DNS fields are blank:
The source asks for firewall and antivirus shutdown. Use only the network access required by the verified tool on this isolated interface, following the local maintenance policy; a blanket security shutdown is not a prerequisite demonstrated by these images. Keep this temporary DHCP service disconnected from an office or production LAN.
2. Open the verified tool and check startup errors
Use a trusted, verified copy of the intended utility and run NetbootM.exe from its folder. No new third-party binary is downloaded or executed by this guide:
The source says to acknowledge a startup error, but its actual message is Could not bind socket. Address and port are already in use. This is not evidence that DHCP is working. Check which process/interface is using the required socket and resolve the conflict before relying on the tool:
3. Select the interface and verify DHCP options
Open Configuration → Options Configuration (the source highlights a toolbar icon). The existing machine-list rows in this picture are examples from other networks, not proof of a new lease for the directly connected BMC:
On DHCP Options, choose the intended laptop adapter in Local IP and review the address pool and options before confirming. The source’s next screenshot binds to 192.168.78.1 and shows a pool from 192.168.78.10 through 192.168.78.250:
Do not copy every field in that archived dialog: it displays 255.255.225.0 as the subnet mask, which is not a valid contiguous IPv4 subnet mask. Its 172.15.15.1 gateway is also outside the illustrated 192.168.78.0/24 network. The source DNS addresses 2.1.0.6 and 2.1.4.1 are not validated for your environment. Use a consistent mask, pool and any required gateway/DNS options for the actual isolated subnet; the first laptop screenshot’s /24 mask is 255.255.255.0.
4. Start DHCP and identify the actual BMC lease
Click the blue Start arrow. Wait for the BMC’s DHCP exchange and identify the real lease by its MAC address or other verified device identity. The source’s machine-list image instead shows 192.168.10.10 and 192.168.10.11, a different subnet from the preceding 192.168.78.x pool; do not assume those rows are the result of that configuration:
5. Open the BMC and close the temporary service
Enter the verified assigned BMC address into the browser address bar. Use the authorized account and the actual current password. The source’s factory-password value is deliberately omitted. The final illustration is a login form at 10.48.3.246 with a masked password, another separate address example; it is not proof of login or of a lease from the earlier pool:
When finished, disconnect the direct cable and explicitly exit the utility from its tray icon. Confirm that the temporary DHCP service has stopped before reconnecting the laptop to another network; leaving it running can interfere with that network’s DHCP clients.