When setting up a local server in a DHCP-enabled network, you need to ensure clients can reliably access it. DHCP-assigned addresses may change, causing connection issues. The solution involves assigning a static IP while preventing DHCP conflicts.

The most reliable method combines two steps:

1. Reserve the desired IP (e.g., 192.168.1.66) in your router's DHCP exclusion range
2. Manually configure this IP on your server's network interface

# Example Linux static IP configuration (/etc/network/interfaces)
auto eth0
iface eth0 inet static
    address 192.168.1.66
    netmask 255.255.255.0
    gateway 192.168.1.1
    dns-nameservers 8.8.8.8 8.8.4.4

While any private IP can be static, these conventions help:

• Common DHCP ranges: 192.168.1.100-192.168.1.254
• Typical static IP ranges: 192.168.1.2-192.168.1.99
• Router usually occupies 192.168.1.1

Your router's behavior suggests:

• DHCP might be handled by another device (192.168.1.5)
• The router maintains a client database showing "static" for remembered leases
• The narrow DHCP range (33-35) indicates possible misconfiguration

For Windows Server, use PowerShell:

# Set static IP on Windows
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 192.168.1.66 
    -PrefixLength 24 -DefaultGateway 192.168.1.1

# Set DNS servers
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" 
    -ServerAddresses ("8.8.8.8","8.8.4.4")

Then configure your router's DHCP scope to exclude 192.168.1.66. For Cisco routers:

ip dhcp excluded-address 192.168.1.66
ip dhcp pool LAN_POOL
   network 192.168.1.0 255.255.255.0
   default-router 192.168.1.1
   dns-server 8.8.8.8
   lease 7

After configuration:

1. Run ipconfig /all on Windows or ifconfig on Linux
2. Ping the static IP from other devices
3. Check router's DHCP lease table for conflicts

When setting up local development environments, we often need servers to maintain persistent IP addresses while coexisting with DHCP clients. The key challenge lies in properly managing address allocation without causing IP conflicts.

The router configuration example shows several important details:

// Typical router DHCP settings
Enable DHCP on LAN : Off
DHCP range : 192.168.1.33 - 192.168.1.35

Despite DHCP being disabled, devices still obtain IPs dynamically. This suggests:

• The router maintains a DHCP-like IP assignment table
• It likely uses MAC address binding for persistent assignments
• Additional DHCP servers might be present (e.g., the observed 192.168.1.5)

For reliable server configuration:

# Windows static IP configuration (PowerShell)
New-NetIPAddress -InterfaceAlias "Ethernet" 
                 -IPAddress 192.168.1.100 
                 -PrefixLength 24 
                 -DefaultGateway 192.168.1.1

# Linux static IP configuration (Ubuntu)
network:
  version: 2
  ethernets:
    eth0:
      addresses: [192.168.1.100/24]
      gateway4: 192.168.1.1
      nameservers:
        addresses: [8.8.8.8, 8.8.4.4]

For environments where you control the DHCP server:

# Example ISC DHCP server reservation
host dev-server {
  hardware ethernet 00:11:22:33:44:55;
  fixed-address 192.168.1.100;
}

Verify IP availability before assignment:

# Windows
arp -a | find "192.168.1.100"

# Linux
arp -an | grep "192.168.1.100"

# Cross-platform ping test
ping -n 1 192.168.1.100

For complex environments, consider VLAN separation:

// Router configuration snippet
vlan 100 {
  name "DEV-SERVERS"
  ip 192.168.100.1/24
  dhcp-range 192.168.100.50-192.168.100.100
}

Regularly audit your network assignments:

# Windows: List all active leases
Get-DhcpServerv4Lease -ComputerName 192.168.1.5

# Linux: Parse DHCP logs
journalctl -u isc-dhcp-server | grep "DHCPACK"

Don't overlook IPv6 configuration:

# Linux IPv6 static config
  eth0:
    addresses:
      - 2001:db8::100/64
    gateway6: 2001:db8::1