Thanks to
Jon Bidinger <jon@wgraphics.com>
"Timothy E. Neto" <neto@ncd.com>
Dave Miner <dave.miner@east.sun.com>
for kindly offering their help.
I ended up pursuing Jon's suggestion and downloaded and built dhcpd from
www.isc.org. It works great with the NCD explora pros.
I have also verified the Windows NT 4.0 dhcp server works fine with the
NCD explora pro terminals. I was more interested in finding a Unix
solution (for lots of reasons - I will spare you the details), and the
ISC version of dhcp satisfied my needs.
I am still interested to see Sun's dhcpd work with NCD clients.
There are some nice tools that come with sun's dhcp server (and with
WinNT version) to query current lease owners that are lacking in the ISC
version.
Thanks
Gautam.
Here are the original replies:
Jon Bidinger wrote:
>
> > Date: Thu, 16 Oct 1997 16:43:07 +0200 (IST)
> > From: Gautam Das <gautam@bwc.org>
> > Reply-to: Gautam Das <gautam@bwc.org>
> > Subject: dhcp problem with NCD ExploraPros.
> > To: Sun Managers <sun-managers@eecs.nwu.edu>,
> > Multiuser NT <multiuser-nt@ncd.com>
> > Cc: ydrori@netcom.co.il, Gautam Das <gautam@bwc.org>
>
> > Hi!
> >
> > We are running Solaris 2.6 dhcp. Win95 PCs are able to lease IP addresses
> > with no problems from the DHCP server.
> >
> > But NCD Explora-Pro terminals are failing. Below is the dhcpd debug output.
> >
> > root@chopin: /usr/lib/inet/in.dhcpd -d
> > Monitor (0005/hme0) started...
> >
> > Windows 95 PC scenario
> >
> > Datagram received on network device: hme0
> > Unicasting datagram to 192.115.146.103 address.
> > Adding ARP entry: 192.115.146.103 == 000087A03B99
> >
> >
> > NCD Explora-Pro scenario
> >
> > Datagram received on network device: hme0
> > Started ICMP thread 7 to validate IP 192.115.146.104, PENDING
> > ICMP thread 7 exiting, IP: 192.115.146.104 = plp->d_icmpflag: AVAILABLE...
> > Using ICMP validated address: 192.115.146.104
> > Unicasting datagram to 192.115.146.104 address.
> > Adding ARP entry: 192.115.146.104 == 0000A70219E4
> > Datagram received on network device: hme0
> > Found offer for: 192.115.146.104
> > (errno: 2) 0000A70219E4: REQUEST is missing requested IP option.
> >
> > What is this missing requested IP option? What do I need to do to make
> > this work?
> >
> > I have a 100 terminals to setup and I do not want to use RARP anymore as
> > we were doing in past.
> >
> > Any help will be appreciated.
>
> I'm not sure about Solaris 2.6 DHCP, but if you don't get the problem
> resolved you might want to look into the ISC DHCP server. Take a look
> at: http://www.isc.org/. I've been running it for several months
> without any problems on 2.5.1. However, I should state that I have a
> fairly simple network.
>
> >
> > Thanks.
> >
> > Gautam
> > > =========================== Jon Bidinger ============================
> Western Graphics, Inc. jon AT wgraphics DOT com
> 530 North Wheeler St. (612) 603-6472
> St. Paul MN 55104
--------------------------------------------------------------------
Subject:
Re: dhcp problem with NCD ExploraPros.
Date:
Thu, 16 Oct 1997 11:09:23 -0400
From:
"Timothy E. Neto" <neto@ncd.com>
To:
Gautam Das <gautam@bwc.org>
Hello Gautam,
Are there any error or warning messages reported by the
DHCP server when the NCD terminals fail to obtain a n IP?
Please try this. in the terminal's boot monitor's Network
setup menu's Terminal IP Field, place a valid address for the
terminal that is in the DHCP scope. I've noticed that this
has a positive effect.
I am currently working on a DHCP problem with NCD terminals
and NT 4.0 DHCP servers. I'm curious to know if this is
common to other DHCP server implementations. I do not obtain
the problem with a WinFrame 1.6 DHCP server.
Thank you.
Tim.
------------------------------------------------------------------------
Subject:
Re: dhcp problem with NCD ExploraPros.
Date:
Thu, 16 Oct 1997 15:25:58 -0400
From:
Dave Miner <dave.miner@east.sun.com>
To:
Gautam Das <gautam@bwc.org>
References:
1
The error message from the the server indicates that the NCD is not
conforming to the DHCP protocol, as it has omitted the option to request
an IP address as required by the RFC's. Call NCD and have them fix it,
I'd say.
Dave
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:06 CDT