manowar
In Runtime
- Messages
- 191
Hi all,
We have 4 VLANs at work, each VLAN is split into 10.48.96.x, 97.X, 98.x, 99.x ranges.
The network was recently rebuilt. We completely moved away from static IPs (which we used in abundance) and now all clients on the schools network obtain IPs via the DHCP.
We've noticed a lot of entries mingling in between client addresses on the DHCP server displaying as "BAD_ADDRESS" (address already in use). I've managed to trace these address back to random PCs on the domain.
So far, I've tried:
1. Looking for rouge DHCP servers on the LAN.
2. Leasing address for 2 hours, 8 hours, 10 hours even unlimited.
3. Deleting all DHCP addresses from the DHCP server at the end of the day, to clean up conflicts.
None of the solutions have sorted the problem. Could it be possible that some clients on the network are still using static IPs and are causing conflicts with the DHCP server?
Any help would be great. Cheers all.
We have 4 VLANs at work, each VLAN is split into 10.48.96.x, 97.X, 98.x, 99.x ranges.
The network was recently rebuilt. We completely moved away from static IPs (which we used in abundance) and now all clients on the schools network obtain IPs via the DHCP.
We've noticed a lot of entries mingling in between client addresses on the DHCP server displaying as "BAD_ADDRESS" (address already in use). I've managed to trace these address back to random PCs on the domain.
So far, I've tried:
1. Looking for rouge DHCP servers on the LAN.
2. Leasing address for 2 hours, 8 hours, 10 hours even unlimited.
3. Deleting all DHCP addresses from the DHCP server at the end of the day, to clean up conflicts.
None of the solutions have sorted the problem. Could it be possible that some clients on the network are still using static IPs and are causing conflicts with the DHCP server?
Any help would be great. Cheers all.