<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DHCP doesn't reply to Bootp in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683523#M53641</link>
    <description>Since no specifics were mentioned, here a checklist on troubleshooting your bootp problem.&lt;BR /&gt;1. Make sure that bootp services are enabled in the /etc/services file. The entries should look like this:&lt;BR /&gt;bootps     67/udp         # Bootstrap Protocol Server&lt;BR /&gt;bootpc     68/udp         # Bootstrap Protocol Client&lt;BR /&gt;&lt;BR /&gt;2. Check that bootp service is enabled in the /etc/inetd.conf file. The entry looks like this:&lt;BR /&gt;bootps     dgram  udp wait  root /etc/bootpd   bootpd&lt;BR /&gt;&lt;BR /&gt;If the entry is commented; uncomment it and run inetd -c to re-read the config file.&lt;BR /&gt;&lt;BR /&gt;3. Test bootp's ability to respond to the test address 080009000000 (found in the default /etc/bootptab or /etc/newconfig//bootptab file.  The form of the command line is:&lt;BR /&gt;&lt;BR /&gt;bootpquery  080009000000 -s &lt;MACHINE&gt;&lt;BR /&gt;&lt;BR /&gt;where &lt;MACHINE&gt; is the host name, typically the machine where bootp testing is taking place.  Two responses typical responses:&lt;BR /&gt;&lt;BR /&gt;bootpquery: Bootp servers not responding!&lt;BR /&gt;&lt;BR /&gt;if the bootp daemon is not working (see steps 1 and 2), or&lt;BR /&gt;&lt;BR /&gt;Received BOOTREPLY from x.x.x.com&lt;BR /&gt;&lt;BR /&gt;followed other test data from the /etc/bootptab file.&lt;BR /&gt;&lt;BR /&gt;4. Start inetd logging operations with:&lt;BR /&gt;&lt;BR /&gt;inetd -l&lt;BR /&gt;&lt;BR /&gt;Detailed service logging will begin in the file /usr/adm/syslog at which point the bootpquery test can be run again, or the device needing bootp services can be powered on or restarted for bootp service.&lt;BR /&gt;&lt;BR /&gt;Then look at the end of the syslog file as in:&lt;BR /&gt;&lt;BR /&gt;tail /usr/adm/syslog&lt;BR /&gt;&lt;BR /&gt;Typical bootpquery logging might be:&lt;BR /&gt;&lt;BR /&gt;machine bootpd[39]: request from hardware address 080009000000&lt;BR /&gt;machine bootpd[39]: sending RFC1048-style reply&lt;BR /&gt;&lt;BR /&gt;(the date stamp was not shown above) which indicates bootpquery and bootp ran correctly.&lt;BR /&gt;&lt;BR /&gt;  5. The bootp daemon may be run manually with the command:&lt;BR /&gt;&lt;BR /&gt;           bootpd -s -d 3&lt;BR /&gt;&lt;BR /&gt;     In this case, bootpd will never exit.  The -d 3 option sets the&lt;BR /&gt;     debugging level to 3 (highest level of information).  Using the&lt;BR /&gt;     -s option causes bootpd to not terminate, thereby bypassing the&lt;BR /&gt;     automatic scheduling of bootp by inetd.   Verify that bootpd is&lt;BR /&gt;     running with:  ps -ef|grep bootpd.&lt;BR /&gt;&lt;BR /&gt;  6. To verify that bootpd is listening for bootp requests, type&lt;BR /&gt;&lt;BR /&gt;           netstat -a |grep boot&lt;BR /&gt;&lt;BR /&gt;     and the line:&lt;BR /&gt;&lt;BR /&gt;           udp        0      0  *.bootps               *.*&lt;BR /&gt;&lt;BR /&gt;     should be shown, indicating that bootpd is responding to any&lt;BR /&gt;     bootp network requests.&lt;BR /&gt;&lt;/MACHINE&gt;&lt;/MACHINE&gt;</description>
    <pubDate>Thu, 14 Mar 2002 18:50:24 GMT</pubDate>
    <dc:creator>S.K. Chan</dc:creator>
    <dc:date>2002-03-14T18:50:24Z</dc:date>
    <item>
      <title>DHCP doesn't reply to Bootp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683520#M53638</link>
      <description>I have a system(C360 with HPUX 10.20) that doesn't reply to any bootp requests. It replies to DHCP requests. I also enabled the Bootp option from network services in SAM but no luck. Can anybody know the solution ?</description>
      <pubDate>Thu, 14 Mar 2002 18:24:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683520#M53638</guid>
      <dc:creator>mehul_1</dc:creator>
      <dc:date>2002-03-14T18:24:38Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP doesn't reply to Bootp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683521#M53639</link>
      <description>what does your /etc/bootptab look like?&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Thu, 14 Mar 2002 18:41:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683521#M53639</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-03-14T18:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP doesn't reply to Bootp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683522#M53640</link>
      <description>&lt;BR /&gt;This is my dhcp file. 192.168.0.8 is my second LAN card on C360. and the directory img_2.2.* is in /home/tftpdir with all the permissions to all.&lt;BR /&gt;&lt;BR /&gt;#-----------------&lt;BR /&gt;# Clearlake&lt;BR /&gt;#-----------------&lt;BR /&gt;dhcp_pool_group: pool-name=Clearlake: addr-pool-start-address=192.168.0.80: addr-pool-last-address=192.168.0.89: allow-bootp-clients=TRUE: lease-time=120: lease-policy=accept-new-clients: call-on-assignment=/home/jd/dev/nautilus/product/nautilus/release/bin/dhcpcall: hn: bf=img_2.2.04_release/bootImage: yd=img_2.2.04_release: nt=192.168.0.8: gw=192.168.0.8: subnet-mask=255.255.255.0&lt;BR /&gt;#-----------------&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Mar 2002 18:50:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683522#M53640</guid>
      <dc:creator>mehul_1</dc:creator>
      <dc:date>2002-03-14T18:50:22Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP doesn't reply to Bootp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683523#M53641</link>
      <description>Since no specifics were mentioned, here a checklist on troubleshooting your bootp problem.&lt;BR /&gt;1. Make sure that bootp services are enabled in the /etc/services file. The entries should look like this:&lt;BR /&gt;bootps     67/udp         # Bootstrap Protocol Server&lt;BR /&gt;bootpc     68/udp         # Bootstrap Protocol Client&lt;BR /&gt;&lt;BR /&gt;2. Check that bootp service is enabled in the /etc/inetd.conf file. The entry looks like this:&lt;BR /&gt;bootps     dgram  udp wait  root /etc/bootpd   bootpd&lt;BR /&gt;&lt;BR /&gt;If the entry is commented; uncomment it and run inetd -c to re-read the config file.&lt;BR /&gt;&lt;BR /&gt;3. Test bootp's ability to respond to the test address 080009000000 (found in the default /etc/bootptab or /etc/newconfig//bootptab file.  The form of the command line is:&lt;BR /&gt;&lt;BR /&gt;bootpquery  080009000000 -s &lt;MACHINE&gt;&lt;BR /&gt;&lt;BR /&gt;where &lt;MACHINE&gt; is the host name, typically the machine where bootp testing is taking place.  Two responses typical responses:&lt;BR /&gt;&lt;BR /&gt;bootpquery: Bootp servers not responding!&lt;BR /&gt;&lt;BR /&gt;if the bootp daemon is not working (see steps 1 and 2), or&lt;BR /&gt;&lt;BR /&gt;Received BOOTREPLY from x.x.x.com&lt;BR /&gt;&lt;BR /&gt;followed other test data from the /etc/bootptab file.&lt;BR /&gt;&lt;BR /&gt;4. Start inetd logging operations with:&lt;BR /&gt;&lt;BR /&gt;inetd -l&lt;BR /&gt;&lt;BR /&gt;Detailed service logging will begin in the file /usr/adm/syslog at which point the bootpquery test can be run again, or the device needing bootp services can be powered on or restarted for bootp service.&lt;BR /&gt;&lt;BR /&gt;Then look at the end of the syslog file as in:&lt;BR /&gt;&lt;BR /&gt;tail /usr/adm/syslog&lt;BR /&gt;&lt;BR /&gt;Typical bootpquery logging might be:&lt;BR /&gt;&lt;BR /&gt;machine bootpd[39]: request from hardware address 080009000000&lt;BR /&gt;machine bootpd[39]: sending RFC1048-style reply&lt;BR /&gt;&lt;BR /&gt;(the date stamp was not shown above) which indicates bootpquery and bootp ran correctly.&lt;BR /&gt;&lt;BR /&gt;  5. The bootp daemon may be run manually with the command:&lt;BR /&gt;&lt;BR /&gt;           bootpd -s -d 3&lt;BR /&gt;&lt;BR /&gt;     In this case, bootpd will never exit.  The -d 3 option sets the&lt;BR /&gt;     debugging level to 3 (highest level of information).  Using the&lt;BR /&gt;     -s option causes bootpd to not terminate, thereby bypassing the&lt;BR /&gt;     automatic scheduling of bootp by inetd.   Verify that bootpd is&lt;BR /&gt;     running with:  ps -ef|grep bootpd.&lt;BR /&gt;&lt;BR /&gt;  6. To verify that bootpd is listening for bootp requests, type&lt;BR /&gt;&lt;BR /&gt;           netstat -a |grep boot&lt;BR /&gt;&lt;BR /&gt;     and the line:&lt;BR /&gt;&lt;BR /&gt;           udp        0      0  *.bootps               *.*&lt;BR /&gt;&lt;BR /&gt;     should be shown, indicating that bootpd is responding to any&lt;BR /&gt;     bootp network requests.&lt;BR /&gt;&lt;/MACHINE&gt;&lt;/MACHINE&gt;</description>
      <pubDate>Thu, 14 Mar 2002 18:50:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683523#M53641</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2002-03-14T18:50:24Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP doesn't reply to Bootp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683524#M53642</link>
      <description>Hi S.K.Chan&lt;BR /&gt;&lt;BR /&gt;I am running all commands from super user and after trying "bootpd -s -d 3"  it says bootpd not found. I checked in /etc and it's there. Permissions on bootpd are lr-xr--r-T and link is /usr/lbin/bootpd&lt;BR /&gt;&lt;BR /&gt;what else I should try ? Actually I donot want bootpserver to reply bootprequests but I want DHCP server to reply all bootp and dhcp requests. Is it possible ? and how ?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Mar 2002 19:12:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dhcp-doesn-t-reply-to-bootp/m-p/2683524#M53642</guid>
      <dc:creator>mehul_1</dc:creator>
      <dc:date>2002-03-14T19:12:54Z</dc:date>
    </item>
  </channel>
</rss>

