- Printer + PIX DHCPD
- Posted by J1C on October 27th, 2005
After recently dropping a PIX in place of an old linksys router the
laster printer on the network can no longer get an IP address however
every other PC on the network can. Any ideas?
- Posted by J1C on October 27th, 2005
Also, the PCs have lease times MUCH longer than the printers NIC ...
192.168.1.109 0100.0ea6.ae5f.3f 74455 seconds
Automatic
192.168.1.110 0100.0c6e.1f7d.cc 54254 seconds
Automatic
192.168.1.112 0100.055d.d1ed.e9 75037 seconds
Automatic
192.168.1.130 0100.0e9b.24a0.5d 79367 seconds
Automatic
192.168.1.133 0001.e6b4.43ec 176 seconds
Automatic
- Posted by Merv on October 27th, 2005
Q1 What version of PIX software ?
Q2. The default lease time should be 3600 seconds. Try configuring the
lease time "dhcpd lease 3601"
Q3. Capture the DHCP packet exchange between printer and PIX using
Ethereal or equivalent to see if pIX is respond to DHCP request from
printer
- Posted by J1C on October 27th, 2005
A1. PIX Version 6.3(4)
A2. It's currently set to 86400 - I will try 3601
A3. Can I do that right from the PIX somehow?
- Posted by Merv on October 27th, 2005
try capturing and posting:
debug dhcpd packet
debug dhcpd event
- Posted by J1C on October 27th, 2005
Where is the debug text sent?
- Posted by Merv on October 27th, 2005
depends on how you configure logging
to see output on telnet session, configure:
logging monitor debugging
to save debug messages in internal logging buffer, configure:
logging buffered debugging
then show logging buffer
