Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How do I reconfigure DHCP on Windows 2003 Server from 192.168.0.X to 1 2
- Thread starter yohae
- Start date
-
1
- #2
SimonDavies
MIS
Well rather than changing the DHCP scope range you could just add a second card into your server and have that as your gateway, alternatively get your ISP to change the IP on their router so that it's using the 192.168.0.1 address (you're the customer you have every right to make that request).
If however you want to go with the new addressing scheme you should start reducing the lease time on the current DHCP scope to hours rather than days, ideally you should give it a 6 hour lease time, once you have reduced the lease time and ALL of the machines are getting their address based on the new lease time you can start to make the changes. The reason you want 6 hours is because this will allow you to make the changes one evening and have the new scope rolled out across the environment when you come back into the office the next day.
Now you 'should' be using reserved addresses for your servers as well as your workstations, if you are then what you're going to have to do is create your new scope using the new range and add the servers onto the reserved list (you will need the MAC address of all those machines).
If you have any routers\switches in your environment you're also going to have to change them to allow for the new range.
If you can't wait for the reduction in lease time then you can go down the route of the new scope now, what you would need to do however is stop the current scope and visit every single machine and do an ipconfig /release and /renew on it (some of the time a /renew won't do it first time which is why the /release is used first).
Simon
The real world is not about exam scores, it's about ability.
If however you want to go with the new addressing scheme you should start reducing the lease time on the current DHCP scope to hours rather than days, ideally you should give it a 6 hour lease time, once you have reduced the lease time and ALL of the machines are getting their address based on the new lease time you can start to make the changes. The reason you want 6 hours is because this will allow you to make the changes one evening and have the new scope rolled out across the environment when you come back into the office the next day.
Now you 'should' be using reserved addresses for your servers as well as your workstations, if you are then what you're going to have to do is create your new scope using the new range and add the servers onto the reserved list (you will need the MAC address of all those machines).
If you have any routers\switches in your environment you're also going to have to change them to allow for the new range.
If you can't wait for the reduction in lease time then you can go down the route of the new scope now, what you would need to do however is stop the current scope and visit every single machine and do an ipconfig /release and /renew on it (some of the time a /renew won't do it first time which is why the /release is used first).
Simon
The real world is not about exam scores, it's about ability.
TechyMcSe2k
Technical User
You say broadband IP of 10.38.16.x (private address) What do you mean? Your ISP provided you with a static in this range (which would make no since/need public only from them)? You have a router with an inside interface ip that is 10.38.16.1?
Just probing for more details. What is your network setup?
_______________________________________
I hope any help I give leads to great successes.
MCSE, MCSA, MCTS, CCA, VCP, CCNA
Just probing for more details. What is your network setup?
_______________________________________
I hope any help I give leads to great successes.
MCSE, MCSA, MCTS, CCA, VCP, CCNA
-
1
- #4
You can change the scope of the DHCP from the initial 192.x.x.x to the new 10.x.x.x
Simply unauthorize/deactivate the DHCP server, delete the 192.x.x.x scope, create the new 10.x.x.x scope and authorize the Server again. Do this while isolating from the network.
Simply unauthorize/deactivate the DHCP server, delete the 192.x.x.x scope, create the new 10.x.x.x scope and authorize the Server again. Do this while isolating from the network.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
