10-11-2007 05:09 PM - edited 03-11-2019 04:24 AM
I can't seem to change the IP of the Inside Interface or the range of the DHCP server.
When I try to change one or both I get this error:
-----------------------
[OK] hostname PIC506E
[ERR]ip address inside 172.22.210.2 255.255.255.0
Interface address is not on same subnet as
DHCP pool
[ERR]dhcpd address 172.22.210.100-172.22.210.155
inside
Address range subnet is not the same as inside
interface
[OK] write memory
-------------------------
I have tried disabling the DHCP server but I still get an error.
Our Cisco guy is overseas for a few months and I feel I must be missing something very simple.
Using Pix Device Manager 3.0(4)
PIX firewall Version 6.3(5)
Solved! Go to Solution.
10-11-2007 05:38 PM
first remove the DHCP pool, then reip the interface, once that is done recreate your new pool.
issue " no dhcpd address 172.22.210.100-172.22.210.155 " then change your inside interface ip.
HTH
Jorge
10-11-2007 05:38 PM
first remove the DHCP pool, then reip the interface, once that is done recreate your new pool.
issue " no dhcpd address 172.22.210.100-172.22.210.155 " then change your inside interface ip.
HTH
Jorge
10-11-2007 07:52 PM
Thanks Jorge, that was it.
PIC506E(config)# no dhcpd address 192.168.1.2-192.168.1.254 inside
PIC506E(config)# show dhcpd
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
PIC506E(config)# ip address inside 172.22.210.2 255.255.255.0
PIC506E(config)# show ip address
System IP Addresses:
no ip address outside
ip address inside 172.22.210.2 255.255.255.0
Current IP Addresses:
no ip address outside
ip address inside 172.22.210.2 255.255.255.0
PIC506E(config)# dhcpd address 172.22.210.55-172.22.210.155 inside
PIC506E(config)# dhcpd enable inside
PIC506E(config)# show dhcpd
dhcpd address 172.22.210.55-172.22.210.155 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
------------------------------------------------------
http server enable
http 172.22.210.0 255.255.255.0 inside
10-11-2007 08:01 PM
Glad is resolved, after config always "write mem" to not loose config if pix reboots.
11-28-2007 07:30 AM
I tried that and changed the IP scheme from 192.168.1.0 to 192.168.5.0 and was unable to contact the PIX 506E. I could ping it, but could not access the PDM.
11-28-2007 08:33 AM
make sure the source IP you are accessing PDM from is allow in PIX for administration.
e.g
where x is your PC IP address
http 192.168.5.x 255.255.255.255 inside
telnet 192.168.5.x 255.255.255.255 inside
or allow the entire inside subnet
http 192.168.5.0 255.255.255.0 inside
telnet 192.168.5.0 255.255.255.0 inside
or allow any subnets from behind the pix
http 0.0.0.0 0.0.0.0 inside
telnet 0.0.0.0 0.0.0.0 inside
See if that works.
HTH
Jorge
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: