02-13-2003 10:11 AM - edited 03-02-2019 05:04 AM
OK I can't seem to get this to work. Im ashamed!!
I have an 827-4V router that connects me to ADSL Internet service. The router is configured to automatically assign IP addresses via DHCP.
I would like my home PC to always have the address of 192.168.0.1 assigned but I can't make this happen.
The relevant config is as follows:
ip dhcp pool HOMEPC
host 192.168.0.1 255.255.255.0
hardware-address 0100.105a.ddc5.31
client-name home01
!
ip dhcp pool default
network 192.168.0.0 255.255.255.0
dns-server 213.120.62.104 213.120.62.97
default-router 192.168.0.254
If I set my client to have an IP address assigned by DHCP I get the next one in the pool rather than the one I have statically assigned, as follows:
Router#sh ip dhcp bind
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type
Hardware address/
User name
192.168.0.1 0100.105a.ddc5.31 Infinite Manual
192.168.0.2 0100.105a.ddc5.31 Feb 14 2003 06:04 PM Automatic
The reason I want this to work is I plan to statically assign an IP address to my laptop which is set up to get its address from a DHCP server. I want to statically NAT some ports to it without having to input the IP address everytime I bring it back from the office.
Any help gratefully appreciated.
Solved! Go to Solution.
02-13-2003 06:08 PM
If it's a Microsoft OS PC, please try the "client-identifier xx.xx.xx" command instead of the "hardware-address xx.xx.xx"
Thanks, Mak.
02-13-2003 10:04 PM
While trying client identifier command do clear ip dhcp binding * and try
again .
Sniffer traces will help lot
Run following command :
debug ip dhcp server packet
debug ip dhcp detail
02-13-2003 06:08 PM
If it's a Microsoft OS PC, please try the "client-identifier xx.xx.xx" command instead of the "hardware-address xx.xx.xx"
Thanks, Mak.
02-13-2003 10:04 PM
While trying client identifier command do clear ip dhcp binding * and try
again .
Sniffer traces will help lot
Run following command :
debug ip dhcp server packet
debug ip dhcp detail
02-14-2003 12:44 AM
Thanks people.
As well as the above I also cleared the arp entries for 192.168.0.2 (the dynamic address I had been assigned)
I had done the debugs before along with sniffer traces and couldn't work out what was wrong as the MAC address was correct.
Working now!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide