ellitech
asked on
BAD_ADDRESS
Hi,
On our network we started getting duplicate IP addresses handed out, we can no longer receive a DHCP IP address from our DHCP server.
We created a second scope to match the first one on a different server, deactivated the first one and activated the second one, same results.
We are constantly getting "BAD_ADDRESS" on the DHCP server, never seen this before...
Any ideas as to why this is happening?
Please respond back as soon as you are able as we are currently having major issues on the network.
Thanks...
ElliTech
On our network we started getting duplicate IP addresses handed out, we can no longer receive a DHCP IP address from our DHCP server.
We created a second scope to match the first one on a different server, deactivated the first one and activated the second one, same results.
We are constantly getting "BAD_ADDRESS" on the DHCP server, never seen this before...
Any ideas as to why this is happening?
Please respond back as soon as you are able as we are currently having major issues on the network.
Thanks...
ElliTech
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
detecting rogue dhcp server:
http://blogs.technet.com/b/teamdhcp/archive/2009/07/03/rogue-dhcp-server-detection.aspx (there is a tool to download at the end of the article)
Delete all the client leases on the DHCP server.
Monitor leases
When you get a BAS ADDRESS again, try to understand what machine caused it (sometimes it is a defective NIC that causes such issue).
Use Wireshark or MS Network Monitor to examine DHCP packets (filter on UDP 67 and UDP 68) and to understand what happens
http://blogs.technet.com/b/teamdhcp/archive/2009/07/03/rogue-dhcp-server-detection.aspx (there is a tool to download at the end of the article)
Delete all the client leases on the DHCP server.
Monitor leases
When you get a BAS ADDRESS again, try to understand what machine caused it (sometimes it is a defective NIC that causes such issue).
Use Wireshark or MS Network Monitor to examine DHCP packets (filter on UDP 67 and UDP 68) and to understand what happens
Please disable antivirus software completely, then delete all DHCP BAD_Address lease from console, restart DHCP service and check if it works
If this resolve your issue, you can check with AV vendor to resolve this issue permanently
Mahesh