Operating System - HP-UX
1753765 Members
5963 Online
108799 Solutions
New Discussion юеВ

Re: DHCP seems to have stopped working after IP adr changes

 
Information Systems
Occasional Advisor

DHCP seems to have stopped working after IP adr changes

I just went through changing our ip address to a private class b. I now seem to be having problems with dhcp where static address work no problem but dynamic ones do not. I have two groups set up for the dynamic assignment, the first for 172.16.2.0/255.255.255.252 and the second for
172.16.3.0/255.255.255.252. They are limited to the C range in the dhcp configuration.

When I attempt to preview the assignment I get an error:
# dhcptools -p ht=1 ha=0060081666bc sn=172.16.2.0
dhcptools: BOOTP/DHCP server not responding.
Error processing dhcptools preview command. Error = -10: Block device required
(exit code = 15).

Any Ideas?
TIA
Mike
7 REPLIES 7
Antoanetta Naghiu
Esteemed Contributor

Re: DHCP seems to have stopped working after IP adr changes

Just as an idea: Check /etc/rc.config.d/netconf to see if DHCP_ENABLE[0]=0 (disable or =1 -enable)
Berlene Herren
Honored Contributor

Re: DHCP seems to have stopped working after IP adr changes

Mike, do you have an DHCP/bootpd patches installed? I seem to remember a problem where the DHCP server was failing to update the dhcpdb file, and this fixed it.

Berlene

PHNE_19095 for 10.20
http://www.mindspring.com/~bkherren/dobes/index.htm
Information Systems
Occasional Advisor

Re: DHCP seems to have stopped working after IP adr changes

Although I haven't had a chance to test this (I moved the DHCP server to an NT box), could there be a problem with the different groups having the same sub-net mask? What I want is to have the range from 172.16.2 1 through 254 and 172.16.3 1 through 254 assigned. I thought I could have two groups, one for each range and have both use the same mask (255.255.252.0). Is there a problem with this?

BTW I don't have PHNE_19095 installed. I will do that next go round unless it is needed anyway.

Cheers
Mike
Anthony deRito
Respected Contributor

Re: DHCP seems to have stopped working after IP adr changes

Mike, two groups are fine. You can have multiple groups defined. You say you moved the DHCP server to the NT box? So which is the current DHCP server, NY or UNIX and which one are you trying to troubleshoot?

Tony
Anthony deRito
Respected Contributor

Re: DHCP seems to have stopped working after IP adr changes

Sorry for the typo... NY should be NT.
Joseph T. Wyckoff
Honored Contributor

Re: DHCP seems to have stopped working after IP adr changes

There are LOTS of settings to be had in NT DHCP, and I think I would look there. NT doesn't do bootp, and if we are crossing a router, the router needs to be bootp/dhcp enabled and so forth. If you are crossing a router, check the settings there.

Do you have an NT box that will connect to (and get an address from your) NT DHCP server? I would try to get NT to work with NT before moving on to UX...

I note in the first entry the last octet of your subnet mask was .252 ...that set off alarm bells, that would be a subnet of 2 useful IP addresses. Elsewhere I see 252.0...that seems far more useful 1022 addresses...
Omniback and NT problems? double check name resolution, DNS/HOSTS...
Joseph T. Wyckoff
Honored Contributor

Re: DHCP seems to have stopped working after IP adr changes

My math is a little bit rusty here, but I think your subnetting may in fact be the problem...

In order for subnets 172.16.2.0, 172.16.3.0
to be distinct, the subnet mask would need to be tighter than you have (255.255.252.0)

More correct would be... any of the following...

255.255.255.0
255.255.255.128
255.255.255.192
255.255.255.224
...


The mask 255.255.252.0 for 172.16.0.0 implies all of the following...

172.16.0.0
172.16.1.0
172.16.2.0
172.16.3.0

(so be sure you aren't using 172.16.0.0, 172.16.1.0 elsewhere...)

Subnetting is a pain, and I may have gotten the details wrong here by a little bit, but I am pretty sure you need to revisit this...

Good Luck.
Omniback and NT problems? double check name resolution, DNS/HOSTS...