DHCP no longer responsive

willemgrooters · Post by **willemgrooters** » Wed Mar 20, 2024 1:26 am

My AXP machine has been serving DHCP services to my LAN for years, even after planned or unplanned downtime, but after a clean shutdown and start up afterwards, none of the systems on my LAN receive their configuration; Forcing my PC's to release and renew their configuration, the request times out. I stopped and restarted the service several times, even reboot of the server didn't solve the issue so in the end, I stopped the service. Nothing found in the logfile - except DDNS errors but these happened before as well:

Code: Select all

$ type tcpip$dhcp_run.log;-1/page
$ Set NoOn
$ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))
JOIN Server Release 4.1.0f-DECsrc  for Alpha with OpenVMS
Copyright 1992-1998 Competitive Automation, Inc.  All Rights Reserved.


JOIN server startup  on Monday March 11 14:21:42
JOIN Server Release 4.1.0f-DECsrc  for Alpha with OpenVMS
Copyright 1992-1998 Competitive Automation, Inc.  All Rights Reserved.

Acquiring lock on resource "TCPIP$DHCP_SERVER"...
Acquired lock on resource "TCPIP$DHCP_SERVER"
server.sock after  socket(TCPIP$C_AUXS, 0, 0) = -1
final server.sock 3
server dns domain name           = grootersnet.local
server nis/nis+ domain name      = grootersnet.local
canonical server IP address      = 192.168.1.2
canonical server name            = diana
debug level                      = 0
ignored interfaces               = none
default lease duration           = 86400
finite bootp auto extension      = 0 secs
ttl of provisional lease         = 60 secs
timeout on ICMP echo             = 1000 msecs
minimum legal bootp packet       = 280 bytes
name service                     = dns
name service updateable          = true
naming policy                    = by hw address
accept client name               = true
ignore name ownership            = false
DNS expiration tracks DHCP lease = true
update NS on every transaction   = false
free list length                 = 16
bootp support                    = true
bootp addr from pool             = false
registered clients only          = false
listen on ppp interfaces         = false
Microsoft RAS support            = false
ping bootp clients               = true
reply when relay on same net     = true
send options in offer            = false
auto-reread modified dhcpcap     = true
validate bootp client net#       = false
auto synchronise disk database   = true
token ring source routing        = false
release ip when client moves     = true
expand BOOTP packet ?            = false
send bootfile in 'file' field    = false
ignore hardware type             = false
force broadcast reply            = false
use MAC addr as client ID        = false

syncing databases

Netmasks:
Net              Mask
192.168.1.0      255.255.255.0

network 192.168.1.0
        IPaddress ranges administered:
                192.168.1.192 - 192.168.1.254
        first free IP address = 192.168.1.192
Listening on interfaces (name  ip  mask  bdcast):
         WE1  10.0.0.1          255.0.0.0         10.255.255.255
         WE0  192.168.1.200     255.255.255.0     192.168.1.255
         WE0  192.168.1.2       255.255.255.0     192.168.1.255

1710166903.523360 Packet arrived   on Monday March 11 14:21:43

DHCPDISCOVER from HW 5c:0f:fb:29:9a:d8 : new lease on 192.168.1.242
1710166904.527202 Packet arrived   on Monday March 11 14:21:44

DHCPDISCOVER from HW 5c:0f:fb:29:9a:d8 : new lease on 192.168.1.242
1710166905.540809 Packet arrived   on Monday March 11 14:21:45

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710166906.543948 Packet arrived   on Monday March 11 14:21:46

DHCPDISCOVER from HW 5c:0f:fb:29:9a:d8 : network not administered by server
1710166906.554690 Packet arrived   on Monday March 11 14:21:46

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710166907.557555 Packet arrived   on Monday March 11 14:21:47

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710166908.561397 Packet arrived   on Monday March 11 14:21:48

DHCPREQUEST(selecting) from HW 5c:0f:fb:29:9a:d8 for IP 192.168.1.242: new lease
DDNS failed to create 192.168.1.242 PTR LocalNet.grootersnet.local :
1710166908.698107 Packet arrived   on Monday March 11 14:21:48
....
1710166912.334593 Packet arrived   on Monday March 11 14:21:52

DHCPREQUEST(selecting) from HW 5c:0f:fb:29:9a:d8 for IP 192.168.1.242: extended lease
DDNS failed to create 192.168.1.242 PTR LocalNet.grootersnet.local :
1710166912.371700 Packet arrived   on Monday March 11 14:21:52

DHCPREQUEST(selecting) from HW 5c:0f:fb:29:9a:d8 for IP 192.168.1.242: old lease
DDNS failed to create 192.168.1.242 PTR LocalNet.grootersnet.local :
1710166912.380489 Packet arrived   on Monday March 11 14:21:52

DHCPREQUEST(selecting) from HW 5c:0f:fb:29:9a:d8 for IP 192.168.1.242 NAK'd : wrong IP for network 192.168.1.0
sendto: network is down
1710166912.382442 Packet arrived   on Monday March 11 14:21:52

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710166913.712448 Packet arrived   on Monday March 11 14:21:53

DHCPREQUEST(selecting) from HW 5c:0f:fb:29:9a:d8 for IP 192.168.1.242: extended lease
DDNS failed to create 192.168.1.242 PTR LocalNet.grootersnet.local :
1710166913.727095 Packet arrived   on Monday March 11 14:21:53

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710166914.729973 Packet arrived   on Monday March 11 14:21:54
...
DHCPDISCOVER from HW 36:40:eb:44:4d:7b : old lease on 192.168.1.243
1710168701.556489 Packet arrived   on Monday March 11 14:51:41

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710168702.559367 Packet arrived   on Monday March 11 14:51:42

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710168703.561542 Packet arrived   on Monday March 11 14:51:43

DHCPDISCOVER from HW 5c:0f:fb:29:9a:d8 : old lease on 192.168.1.242
1710168704.794885 Packet arrived   on Monday March 11 14:51:44

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710168705.797752 Packet arrived   on Monday March 11 14:51:45

DHCPDISCOVER from HW 5c:0f:fb:29:9a:d8 : old lease on 192.168.1.242
1710168706.800630 Packet arrived   on Monday March 11 14:51:46

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710168707.803508 Packet arrived   on Monday March 11 14:51:47

DHCPDISCOVER from HW 5c:0f:fb:29:9a:d8 : old lease on 192.168.1.242
1710168708.806387 Packet arrived   on Monday March 11 14:51:48

DHCPDISCOVER from HW b8:16:5f:f6:fa:94 : old lease on 192.168.1.221
1710168709.809264 Packet arrived   on Monday March 11 14:51:49

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710168710.812143 Packet arrived   on Monday March 11 14:51:50

DHCPDISCOVER from HW 5c:0f:fb:03:dd:18 : old lease on 192.168.1.233
1710168711.815020 Packet arrived   on Monday March 11 14:51:51

DHCPDISCOVER from HW 5c:0f:fb:29:9a:d8 : old lease on 192.168.1.242
exiting on signal
SIGTERM
JOIN server shutdown on Monday March 11 14:51:51
%TCPIP-W-DHCP_SIGNAL, going down on signal
  TCPIP$DHCP   job terminated at 11-MAR-2024 14:51:51.94

  Accounting information:
  Buffered I/O count:              22860      Peak working set size:      11648
  Direct I/O count:                 9786      Peak virtual size:         185600
  Page faults:                       698      Mounted volumes:                0
  Charged CPU time:        0 00:00:02.63      Elapsed time:       0 00:30:11.25

I finally shutdown the service and let DHCP be handled by my router, but I want the service back on my VMS server.
Any idea what may cause this behaviour? As it seems that the service accepts requests but fails to send the answer in time. It might be a network issue as well because some services are sluggish as well (not all)