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
18 years ago
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?
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 AutomaticQ1 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
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?
try capturing and posting:
debug dhcpd packet
debug dhcpd event
Where is the debug text sent?
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
Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.