winklez
asked on
my DHCP causes conflicts
hi all,
my questions are:
1) i am using a windows 2000 DHCP server on my network! now it is causing the IP conflict.how this can be resolved? ; i have given a second class IP scope or i have only 200 PCs connected at time otherwise i could assume it is caused by the luck of free IP
2)when installing windows 2000 advanced server clusters, Is it necessary to separate the Private cluster connection and the public cluster connection when both nodes are connected to a high speed LAN? i am asking this question because First i want to go for this technology but my two HP proliants Servers has one NIC each; second i really don't have much knowledge on windows Clusters
my questions are:
1) i am using a windows 2000 DHCP server on my network! now it is causing the IP conflict.how this can be resolved? ; i have given a second class IP scope or i have only 200 PCs connected at time otherwise i could assume it is caused by the luck of free IP
2)when installing windows 2000 advanced server clusters, Is it necessary to separate the Private cluster connection and the public cluster connection when both nodes are connected to a high speed LAN? i am asking this question because First i want to go for this technology but my two HP proliants Servers has one NIC each; second i really don't have much knowledge on windows Clusters
As a short-term fix, you should also enable "conflict detection" on the DHCP server. In the DHCP console, right-click the server, Properties, then Advanced. Set the number of pings: one should be enough, but maybe more if you serve a busy or WAN environment.
This will check an IP address before issuing it to a DHCP client by pinging it. If the address responds, then it is in use, and the DHCP server will record it as a BAD_ADDRESS in the active lease listing. After a few days you should have a list of these static addresses to follow up.
This will check an IP address before issuing it to a DHCP client by pinging it. If the address responds, then it is in use, and the DHCP server will record it as a BAD_ADDRESS in the active lease listing. After a few days you should have a list of these static addresses to follow up.
ASKER
Dschwartzer told to release all asigned leases on the DHCP server; how this can be done? u mean using IPCONFIG /release command? what about IP-SCAN?
ASKER
then what can u say about
when installing windows 2000 advanced server clusters, Is it necessary to separate the Private cluster connection and the public cluster connection when both nodes are connected to a high speed LAN? i am asking this question because First i want to go for this technology but my two proliants Servers has one NIC each; second i really don't have much knowledge on windows Clusters
when installing windows 2000 advanced server clusters, Is it necessary to separate the Private cluster connection and the public cluster connection when both nodes are connected to a high speed LAN? i am asking this question because First i want to go for this technology but my two proliants Servers has one NIC each; second i really don't have much knowledge on windows Clusters
You can release the leased from the DHCP server console - I don't hace one in front of me now, but as far as I remember, in the Address Leases section you'll see the active leases - which you can release by right clicking and selecting -> release (if my memory doesn't fail me).
As for the IP scan, you can either use Roly_Dee's suggestion, or try any of the free tools on the internet - the first one that the search returned was this:
http://www.ks-soft.net/ip-tools.eng/
As for the IP scan, you can either use Roly_Dee's suggestion, or try any of the free tools on the internet - the first one that the search returned was this:
http://www.ks-soft.net/ip-tools.eng/
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1) This problem can exist if some computers on your subnet have static IPs, while others DHCP. It it really is your network, you can first of all release all assigned leases, disable the scope, then ip-scan the subnet to receive the list of assigned/answering addresses.
When you have this list, you can add them to the exclustion scope of the DHCP server. Reenable the scope.
d