We have a PIX 515 at a remote office. It is connected to a cable modem. We had a VPN up and running with no problems. The cable company did an upgrade and now the PIX will not get a DHCP address from the cable modem.
I have talked to them multiple times and they are telling me that it is a problem with our PIX. Before the upgrade we had a "sticky IP" so we always got the same IP address. They changed their entire IP scheme and I am thinking they have a reservation on their DHCP server that is no longer valid.
If I connect a broadband router to the cable modem and the PIX then the PIX will pick up an address from the router (192.168.x.x) but I need the PIX to have a public address. If I connect a PC to the cable modem the PC gets an public address, which is why they are telling me it is my PIX.
I ran debug dhcpc detail and this a sample from the output
DHCP get addr: existing ip lease str = 0xecec6c
DHCP: new ip lease str = 0xdd5194packet
DHCP client msg received, fip=10.8.x.x, fport=67
DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124
DHCP client msg received, fip=10.8.x.x, fport=67
DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124
DHCP: QScan: Purging entry
DHCP: deleting entry dd4e54 0.0.0.0 from list
Temp IP addr: 0.0.0.0 for peer on Interface: unknown
Temp sub net mask: 0.0.0.0
DHCP Lease server: 0.0.0.0, state: 8 Purging
DHCP transaction id: 0x114A1
Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs
No timer running
Retry count: 0 Client-ID:
DHCP: SDiscover attempt # 2 for entry:
Temp IP addr: 0.0.0.0 for peer on Interface: outside
Temp sub net mask: 0.0.0.0
DHCP Lease server: 0.0.0.0, state: 1 Selecting
DHCP transaction id: 0x20D04
Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs
Next timer fires after: 2 seconds
Retry count: 2 Client-ID: cisco-0013.mmmm.mmmm-outside
DHCP: SDiscover: sending 278 byte length DHCP packet
DHCP: SDiscover 278 bytes
DHCP Broadcast to 255.255.255.255 from 0.0.0.0
DHCP: SDiscover attempt # 3 for entry:
Temp IP addr: 0.0.0.0 for peer on Interface: outside
Temp sub net mask: 0.0.0.0
DHCP Lease server: 0.0.0.0, state: 1 Selecting
DHCP transaction id: 0x20D04
Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs
Next timer fires after: 2 seconds
Retry count: 3 Client-ID: cisco-0013.mmmm.mmmm-outside
DHCP: SDiscover: sending 278 byte length DHCP packet
DHCP: SDiscover 278 bytes
DHCP Broadcast to 255.255.255.255 from 0.0.0.0
DHCP: QScan: Timed out Selecting state
DHCP: QScan: Purging entry
DHCP: deleting entry eceacc 0.0.0.0 from list
Temp IP addr: 0.0.0.0 for peer on Interface: unknown
Temp sub net mask: 0.0.0.0
DHCP Lease server: 0.0.0.0, state: 8 Purging
DHCP transaction id: 0x15EF1
Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs
No timer running
Retry count: 0 Client-ID:
I have changed their DHCP server's IP and the MAC address of the PIX. The PIX seems to be getting an DHCP offer but it says "not for us". Any ideas?
