Solved: host unable to connect after DHCP exlcusion

nygenxny123 · ‎03-28-2008

One of the users asked that they be given a static IP for some apllications they are running on their desktop.

They had the dynamically assigned IP of 192.168.22.32

I excluded them from the dhcp pool, than

statically configured their pc to the excluded address...now they are unable to connect to the network...does this make sense?

ip cef

no ip dhcp use vrf connected

ip dhcp excluded-address 10.10.10.1

ip dhcp excluded-address 192.168.22.1 192.168.22.10

ip dhcp excluded-address 192.168.22.32

!

ip dhcp pool sdm-pool

import all

network 10.10.10.0 255.255.255.248

default-router 10.10.10.1

lease 0 2

!

ip dhcp pool sdm-pool1

import all

network 192.168.22.0 255.255.255.0

dns-server 192.168.1.27

default-router 192.168.22.1

netbios-name-server 192.168.119.2 192.168.117.15

netbios-node-type h-node

!

Edison Ortiz · ‎03-28-2008

Did they manually enter 192.168.22.32 and DNS 192.168.1.27 and default gateway 192.168.22.1 ?

Lots of thing are forgotten when manually entering IP information in a host device. That's the reason DHCP is the preferred choice for handing out IP address.

You could've configured this device with a static mapping in your DHCP server instead of trusting them to enter the correct information.

Please see:

http://www.cisco.com/en/US/docs/ios/12_4/ip_addr/configuration/guide/hipdhcps.html#wp1114732

HTH,

__

Edison.

View solution in original post

Edison Ortiz · ‎03-28-2008

Did they manually enter 192.168.22.32 and DNS 192.168.1.27 and default gateway 192.168.22.1 ?

Lots of thing are forgotten when manually entering IP information in a host device. That's the reason DHCP is the preferred choice for handing out IP address.

You could've configured this device with a static mapping in your DHCP server instead of trusting them to enter the correct information.

Please see:

http://www.cisco.com/en/US/docs/ios/12_4/ip_addr/configuration/guide/hipdhcps.html#wp1114732

HTH,

__

Edison.

nygenxny123 · ‎03-28-2008

Thx Edison!

and yes..i shouldnt have trusted them..

turns our they had the subnet mask wrong.

Ill review the doc to avoid further issues