Hi All

We have experienced wierd issues with our machines in one vlan not
booting past the pxe screen. Also these pc's have random trouble
releasing and renewing their IP's.

Below is an extract from our dhcpsrvr log file:-

****
2006/12/05 13:58:27 <DHCPREQUEST> packet received from client
<0:13:72:D8:51:86>, client requested IP address = <172.16.36.26>.
2006/12/05 13:58:27 DHCP Warning: There is no matching entry
configured for client <0:13:72:D8:51:86>.
Get type:5, IPAddr:172.16.36.26, LeaseTime:0, MacIndx:53011,
pIP:9ADDDE40
AMAGet(): requested IP addr not found. IPAddr found= 172.16.46.145,
IPAddr req = 172.16.36.26, type= 5
AMAGet() exit err:8, subnet:172.16.0.0, addr:172.16.36.26
2006/12/05 13:58:27 <DHCPREQUEST> packet received from client
<0:13:72:D8:51:86>, client requested IP address = <172.16.36.26>.
2006/12/05 13:58:27 DHCP Warning: There is no matching entry
configured for client <0:13:72:D8:51:86>.
Get type:5, IPAddr:172.16.36.26, LeaseTime:0, MacIndx:53011,
pIP:9ADDDE40
AMAGet(): requested IP addr not found. IPAddr found= 172.16.46.145,
IPAddr req = 172.16.36.26, type= 5
AMAGet() exit err:8, subnet:172.16.0.0, addr:172.16.36.26
2006/12/05 13:58:27 <DHCPREQUEST> packet received from client
<0:13:72:D8:51:86>, client requested IP address = <172.16.36.26>.
2006/12/05 13:58:27 DHCP Warning: There is no matching entry
configured for client <0:13:72:D8:51:86>.
Get type:5, IPAddr:172.16.36.26, LeaseTime:0, MacIndx:53011,
pIP:9ADDDE40
AMAGet(): requested IP addr not found. IPAddr found= 172.16.46.145,
IPAddr req = 172.16.36.26, type= 5
AMAGet() exit err:8, subnet:172.16.0.0, addr:172.16.36.26

*****

The above message shows only three entries but the log has loads against
the same machine. Also, other machines are doing the same so i do not
believe it is machine specific.

Other configured vlans appear fine, also nothing has changed on our core
routers and they are behaving ok for the other configured subnets we have.

One thing of note is, i noticed a -625 error on the replica for the DHCP
server, when i came in monday morning. A reboot fixed that, so it looks
like there may have been some comms issue or still is.

Any ideas would be great.

Cheers
Julian.