dhcp: How do u configure scopes in superscope to lease ips from both scopes.
I am working for a merchant bank.
Scope A = 194.16.1.2 - 194.16.1.254
Scope B = 194.16.2.2 - 194.16.2.254
Both use default sub mask.
1 dc is on the network with the ip 194.16.1.1 (static). This DC is sole dhcp and dns server.
I have created a superscope.
Currently scope B has no address leases. When will scope B begin lease addresses, because scope A has already reached over 90% of avaliable addresses?
How do you configure each scope to lease ips to any, or specific groups of clients eg all comps on the 2nd floor?
I do not want to add another dhcp on scope B but am willing to use a relay agent 2 nic's if nessesary?
Please could an expert help?
Scope A = 194.16.1.2 - 194.16.1.254
Scope B = 194.16.2.2 - 194.16.2.254
Both use default sub mask.
1 dc is on the network with the ip 194.16.1.1 (static). This DC is sole dhcp and dns server.
I have created a superscope.
Currently scope B has no address leases. When will scope B begin lease addresses, because scope A has already reached over 90% of avaliable addresses?
How do you configure each scope to lease ips to any, or specific groups of clients eg all comps on the 2nd floor?
I do not want to add another dhcp on scope B but am willing to use a relay agent 2 nic's if nessesary?
Please could an expert help?
Hmm - bs-baffle engaged! SystmProg is totally wrong. DHCP is a broadcast system whereby the first server to respond wins! The defined scope only comes into play AFTER the request has been satisfied.
How have you defined your supersope? It seems a bit strange that a DHCP server wouldn't be responding.
Have you set your lease time low enough to force a migration of computers from one DHCP server to the other? Clients will renew their address at 50% of the lease time so, if the original DHCP server is available, they will never migrate. You might try dropping the lease time to something small (1 hour) and disabling the primary DHCP server. The clients should renew from the other server.
How have you defined your supersope? It seems a bit strange that a DHCP server wouldn't be responding.
Have you set your lease time low enough to force a migration of computers from one DHCP server to the other? Clients will renew their address at 50% of the lease time so, if the original DHCP server is available, they will never migrate. You might try dropping the lease time to something small (1 hour) and disabling the primary DHCP server. The clients should renew from the other server.
Sorry - what is the subnet mask you are using for your superscope?
ASKER
Submask = 255.255.255.0 on scope A and the same for scope B.
I deactivated scope A and forced ipconfig release/renew on a client and the client was leased an ip from subnet B but now I cannot ping my DC by host name or ip from the client machine.
How can this be resolved?
I deactivated scope A and forced ipconfig release/renew on a client and the client was leased an ip from subnet B but now I cannot ping my DC by host name or ip from the client machine.
How can this be resolved?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks! How you solved it? Please let us know.
Your assumption is wrong towards DHCP server. DHCP server can serve the client request only from the scope for which client is member. Client member for the scope is identified by the subnet mask for which this scope been created. So client will receive the ip address only from the scope for which he is member of the scope. And also creating Supercope doesn't mean that it will service client requests comming from any subnet and from any scope. So scenario is: -
Scope A-------will service client requests comming from 192.16.1/24 Subnet
Scope B-------will service client requests comming from 192.16.2/24 Subnet