- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- DHCP seems to have stopped working after IP adr ch...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2000 12:42 PM
тАО08-28-2000 12:42 PM
DHCP seems to have stopped working after IP adr changes
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2000 06:05 AM
тАО08-29-2000 06:05 AM
Re: DHCP seems to have stopped working after IP adr changes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2000 12:03 PM
тАО08-29-2000 12:03 PM
Re: DHCP seems to have stopped working after IP adr changes
Berlene
PHNE_19095 for 10.20
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2000 01:06 PM
тАО08-29-2000 01:06 PM
Re: DHCP seems to have stopped working after IP adr changes
BTW I don't have PHNE_19095 installed. I will do that next go round unless it is needed anyway.
Cheers
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2000 09:32 AM
тАО09-07-2000 09:32 AM
Re: DHCP seems to have stopped working after IP adr changes
Tony
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2000 09:58 AM
тАО09-07-2000 09:58 AM
Re: DHCP seems to have stopped working after IP adr changes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2000 04:00 PM
тАО09-07-2000 04:00 PM
Re: DHCP seems to have stopped working after IP adr changes
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...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2000 04:09 PM
тАО09-07-2000 04:09 PM
Re: DHCP seems to have stopped working after IP adr changes
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.