J
Jeremy Burkes
Everyone,
I get this error on one of my DC's which is also a GC, FSMO,
DNS, WINS, DHCP server. I only get this once every 3 to 4 days. The weird
thing is that it is coming from itself, ie it is like the server is trying
to register itself and rejecting the packet. However, I double checked and
the server is pointing to itself and their are all the appropriate records
it needs to function A, SOA, NS, etc.
I then surmised that the issue is a client machine getting
an ip address from the DHCP server running on this machine with a bad name,
and the DHCP server running on this machine is trying to register the
client's ip address on its behalf because I allow dynamic updates (DDNS).
However, I cannot find the culprit, I have checked WINS and there are no
unusual names there and have even checked network neighborhood to see if I
could find the NetBIOS/Host name that could be the culprit but with no luck.
Since the errors have only crept up recently and I know we
have some machines with Windows 98 and NT running around I am guessing this
is a client to dhcp to dns dynamic registration issue, but I am not certain
on that, anyone have any ideas?
TIA - Jeremy
I get this error on one of my DC's which is also a GC, FSMO,
DNS, WINS, DHCP server. I only get this once every 3 to 4 days. The weird
thing is that it is coming from itself, ie it is like the server is trying
to register itself and rejecting the packet. However, I double checked and
the server is pointing to itself and their are all the appropriate records
it needs to function A, SOA, NS, etc.
I then surmised that the issue is a client machine getting
an ip address from the DHCP server running on this machine with a bad name,
and the DHCP server running on this machine is trying to register the
client's ip address on its behalf because I allow dynamic updates (DDNS).
However, I cannot find the culprit, I have checked WINS and there are no
unusual names there and have even checked network neighborhood to see if I
could find the NetBIOS/Host name that could be the culprit but with no luck.
Since the errors have only crept up recently and I know we
have some machines with Windows 98 and NT running around I am guessing this
is a client to dhcp to dns dynamic registration issue, but I am not certain
on that, anyone have any ideas?
TIA - Jeremy