A network setup walkthrough covering both DHCP and static IP scenarios
A practical configuration guide for getting an office MFP onto the network reliably — when to use DHCP, when to switch to static IP, the exact device menu paths for major vendors, and what to verify before declaring success.
A new MFP gets pulled out of the carton, plugged into power, plugged into the wall Ethernet jack, and is expected to print from every desk in the office within the hour. Most of the time it works. When it does not, the troubleshooting takes longer than it should because the network configuration step was treated as a one-time button-press rather than a deliberate decision between two approaches. This walkthrough covers both DHCP and static IP configuration for office MFPs, the trade-offs that drive the choice, and how to verify the configuration before users start trying to print.
The DHCP versus static IP decision
Dynamic Host Configuration Protocol
The router or DHCP server assigns the MFP an IP address from a pool when the device joins the network. The address may change at lease renewal, which happens every 24 hours to 7 days depending on the lease time.
Setup is automatic — the device receives an address immediately on first boot. No manual configuration required.
Manually assigned address
The network administrator assigns a specific IP address that does not change. The device's address persists across reboots, network outages, and lease renewals indefinitely.
Setup requires the network admin to allocate an address from outside the DHCP pool and configure subnet, gateway, and DNS values manually.
Step-by-step setup — DHCP scenario
Connect Ethernet cable to the MFP and to the office network port
The MFP's network port is usually on the back, labelled with "LAN" or an Ethernet icon. The office port should be a live patch on the office switch — verify by plugging a laptop into the same port first and confirming it gets an IP address.
Power on the device and wait for the boot cycle to complete
Typical boot takes 3-8 minutes during which the MFP runs self-test and acquires a DHCP lease. The touchscreen indicates progress through "Initializing", "Acquiring address", and "Ready".
Verify the device received an address
From the touchscreen, navigate to System Settings → Network → TCP/IP. The IPv4 Address field shows the assigned address. If it shows 0.0.0.0 or 169.254.x.x, the DHCP request failed — see troubleshooting below.
Note the IP address and MAC address for documentation
Record both in the office's network inventory. The MAC address persists for the life of the device and is needed for DHCP reservations or firewall rules.
Optional: Set up a DHCP reservation
On the office DHCP server (typically the router or a Windows DHCP service), create a reservation tying the MFP's MAC address to a specific IP. The device continues to use DHCP but always receives the same address — combining the convenience of DHCP with the stability of static.
Step-by-step setup — static IP scenario
Coordinate with the network administrator before starting
Request: an unused IP address outside the DHCP range, the subnet mask, the default gateway, and the DNS server addresses for the office network. Document each value.
Connect the MFP to the network and power on as for DHCP
The device boots and likely acquires a temporary DHCP address — this is normal and provides initial connectivity until static configuration is applied.
Navigate to the network configuration menu
From the touchscreen: System Settings → Network → TCP/IP → IPv4 → IP Configuration. Change the mode from "DHCP" to "Manual" or "Static".
Enter the static IP, subnet, gateway, and DNS values
Example office values: IP 192.168.1.50, subnet 255.255.255.0, gateway 192.168.1.1, DNS 192.168.1.1 or 8.8.8.8. Specifics depend on the office network.
Save and reboot the device's network stack
Most devices apply changes immediately but some require a network restart or full device reboot. Wait for the device to indicate Ready before proceeding.
Verify connectivity by pinging from a workstation
From any laptop on the office network, open a terminal and run ping 192.168.1.50. Continuous successful responses confirm the device is reachable.
Vendor-specific menu paths
| Vendor | Touchscreen path to TCP/IP settings |
|---|---|
| HP | Settings → Network → Wired → IPv4 Settings |
| Konica Minolta | Utility → Administrator Settings → Network → TCP/IP Settings |
| Canon | Settings/Registration → Preferences → Network → TCP/IPv4 Settings |
| Ricoh | User Tools → System Settings → Interface Settings → IPv4 Address |
| Xerox | Device → Network → Connectivity → IPv4 |
| Kyocera | System Menu → System/Network → Network Settings → TCP/IP Settings |
| Brother | Settings → Network → Wired LAN → TCP/IP → IP Address |
| Epson WorkForce | Setup → Admin Settings → Network → TCP/IP Address |
The exact menu wording varies by firmware version but the path structure stays consistent across releases. If the touchscreen path differs, use the device's web admin interface instead — every major office MFP includes a browser-based admin console at the device's current IP address, and the network settings page is named consistently across vendors as "Network" or "TCP/IP Settings".
Verification steps after configuration
After completing either DHCP or static IP setup, run four verification steps. First, ping the device from a workstation — continuous successful responses confirm Layer 3 connectivity. Second, browse to the device's web admin interface at its IP — successful page load confirms HTTP service is reachable. Third, print a configuration page from the device's maintenance menu — visual confirmation of network parameters as the device sees them. Fourth, install the printer driver on one test workstation and submit a test print — end-to-end confirmation that print traffic reaches the device.
Troubleshooting common network setup issues
The most common network issues
- Device shows 169.254.x.x addressThis is the auto-IP fallback when DHCP fails. Check the Ethernet cable, the patch panel connection, and the switch port status. Try a different patch cable.
- Device gets DHCP address but cannot be pingedCheck that the workstation and MFP are on the same VLAN. Inter-VLAN routing may need explicit firewall rules.
- Print job submits but never completesThe print server's port 9100 (raw print) or 631 (IPP) may be blocked by a firewall between the workstation and MFP. Check intermediate firewall rules.
- Device hostname does not resolveThe DNS server may not have a record for the MFP's hostname. Either add an A record manually or use IP-based printer setup instead of name-based.
- Web admin interface times outThe device's HTTP service may be disabled by default for security. Enable it from the touchscreen System Settings → Web Service menu.
- Static IP conflicts with another deviceTwo devices with the same IP cannot both function. Verify the assigned IP is unused by pinging it before assignment — no response means the address is free.
The hybrid approach — DHCP reservation
For most Spanish office environments the cleanest configuration is DHCP with reservation rather than pure static IP. The MFP's MAC address ties to a specific reserved IP in the DHCP server, the device boots with DHCP enabled, and it always receives the same address. The advantage over manual static configuration: if the network range changes (when moving offices, restructuring the network, or migrating to a new router), the DHCP server's reservation table updates centrally instead of requiring the MFP to be reconfigured at the device itself.
DHCP reservations are supported by every modern router and DHCP server. The configuration is one entry per MFP tying MAC to IP. Even small offices with consumer routers (FRITZ!Box, Movistar router, ASUS, etc.) support reservations under names like "Static DHCP Assignment" or "Address Reservation".
IPv6 — when to enable, when to disable
Most Spanish office networks do not run IPv6 internally and most office MFPs default IPv6 to disabled. Leave it disabled unless the office network specifically uses IPv6 for internal connectivity. Enabling IPv6 without a corresponding network configuration introduces routing complexity without benefit. For offices that do run IPv6, enable it after IPv4 configuration is verified working, then validate IPv6 connectivity separately.
Print server versus direct print
The final architectural question is whether workstations print directly to the MFP's IP or through a central print server. Direct print is simpler but each workstation must be configured individually. Print server adds a server (typically Windows Print Server, CUPS on Linux, or a dedicated print management platform) that workstations submit to, and the server handles routing to physical devices. For offices of 15+ users, print server is almost always worth the additional complexity because of centralised driver management and queue control.