*** From dhcp-server -- To unsubscribe, see the end of this message. ***
Are you SURE the thing is set up for DHCP mode of operation ?
My experience with older JetDirect cards is that they start up in BOOTP
mode and have to be explicitly configured for DHCP. You can do this either
thru the JetAdmin program, running on a PC, or by telnetting to the card
and setting it up on the linemode interface.
In all our machines, the only fields I use are the hardware type, hardware
address, subnet mask, gateway, ip address, the 'vendor magic number' set
to "rfc1048" (so the thing will know that it is an extended DHCP reply)
and the 144 generic tag set to the boot file the printer retrieves via
TFTP (full path to the chrooted file). I don't include a boot server,
since it is TFTP'ing off the same machine as the DHCP server.
Also, be very careful to telnet into each and every one of your printers
and give them a secure, non-obvious password. By default, the telnet
interface starts with no password and, in our previous days of innocent
ignorance, we've had the hackers change the IP address to match some of
the servers, with the corresponding mayhem on the LAN.
Hope this helps.
J.Courcoul
Monterrey Inst. of Technology
Queretaro Campus
Mexico
On Thu, 27 May 1999 [EMAIL PROTECTED] wrote:
> > I'm still having problems getting my newer printers
> to work with DHCP pl18. Similar scenario, works fine
> in bootp mode. Something that's not
> clear is what parameters are really required for the printer to work.
> Looking at the DHCP request, the printer wants:
>
> Tag
> 1 subnet mask
> 3 routers
> 7 log-servers
> 12 host-name
> 18 extensions-path
> 44 netbios-name-servers
> 51 dhcp lease time
> 54 dhcp-server-ident
> 58 dhcp-renewal-time
> 59 dhcp-rebinding-time
> 144 ?????
>
> I'm sending it (almost) everything it wants. Tag 144 is a configuration
> file option?
> I don't have any, do I need to send a null parameter of something?
> What happens is the server send the offer, printer sends the request, server
> sends the ack.....pause....printer sends discover, server sends offer,
> printer
> sends request, server sends ack....pause, etc. It also gets domain name
> and DNS servers since those are global in dhcp.conf file. Does the printer
> care if it gets stuff it didn't ask for?
>
> Looking at the config page printout confuses things worse. It shows
> NOT SPECIFIED for several of the things that are definitely being sent
> to the printer like subnet mask, and syslog server.
>
>
> --> Pete Clark
> Network Operations, EE, MCSE
> Naval Surface Warfare Center, Carderock Division
> > * mailto:[EMAIL PROTECTED]
> "Bringing the world to your desktop"
>
>
>
>
> > On Wed, 5 May 1999, Tom Limoncelli wrote:
> >
> > } *** From dhcp-server -- To unsubscribe, see the end of this message.
> > ***
> > }
> > } I have an HP 5 Si MX that bootp's fine with HP's software
> > } but doesn't work with ISC DHCP server pl27.
> > }
> > } Has anyone gotten this to work?
> > }
> > } Here is the relevent lines from the config file:
> > }
> > } host java.research.bell-labs.com {
> > } hardware ethernet 0:60:b0:27:c5:e0;
> > } fixed-address java.research.bell-labs.com;
> > } option host-name "java.research.bell-labs.com";
> > } always-reply-rfc1048 on;
> > } option option-144 "hpnp/zoo-printer.cfg";
> > } next-server frank.research.bell-labs.com;
> > } }
> > } (this has been attempted with and without the "always-reply-rfc1048
> > on;")
> >
> > Some options that I _know_ cause problems with older JetDirect
> > cards are:
> >
> > ##(HP)## option netbios-node-type 8;
> > ##(HP)## option netbios-name-servers lax.pe-nelson.com;
> > ##(HP)## option ntp-servers lax.pe-nelson.com;
> > ##(HP)## option broadcast-address 192.52.153.255;
> >
> > For the group of JetDirect interfaces, I also declare
> > "use-host-decl-names off;". But I thought 5Si/Mx's
> > were recent enough that they didn't fail to start
> > with the commented-off options listed above.
> >
> > After the printer fails, what errors are shown in its
> > test page? That's how I was able to eliminate those options:
> > One by one, I found out which option caused it to fail THAT time.
> >
> > There are also a couple of reports relating to problems passing
> > filenames with pl27. We've used that in the past (not for
> > printer config files), but not with pl27. We _are_ using
> > pl27, and all our printers start correctly.
> >
> > So I'd say the next step is to look at the test page from
> > the printer after it fails to get an IP address, and see
> > what it thinks is wrong.
> >
> > Jim
> > --
> > Jim Watt [EMAIL PROTECTED]
> > PE Corporation Voice (desk): +1 408 577 2228
> > PE Informatics Division Fax: +1 408 894 9307
> > 3833 North First Street Voice (main): +1 408 577 2200
> > San Jose CA 95134-1701
------------------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://www.isc.org/dhcp-lists.html
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] with the subject line of
'unsubscribe'.
Archives for this mailing list are available at:
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
