Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Oops. Need to rebuild original DHCP scopes
0 views
Skip to first unread message
Jeff Meaney
Apr 7, 1999, 3:00:00 AM4/7/99
to
While fiddling with some IP stuff, instead of deactivating, I stupidly
deleted the original DHCP scopes that SBS sets up. Is there a quick and easy
way to regenerate these? I did rebuild one, but I'm getting some weird
behavior at the clients; some work, some don't. Also, there appeared to be
two identical scopes (yes, I deleted them both); why?
deleted the original DHCP scopes that SBS sets up. Is there a quick and easy
way to regenerate these? I did rebuild one, but I'm getting some weird
behavior at the clients; some work, some don't. Also, there appeared to be
two identical scopes (yes, I deleted them both); why?
I was smart enough to write down all the info first, but for some reason,
the rebuilt one still doesn't work exactly right.
Thankful for any info.
Jeff Meaney
je...@jeffmeaney.com
Stephen King
Apr 7, 1999, 3:00:00 AM4/7/99
to
What problems are you getting on your clients? You may need to run WINIPCFG
(if Win95/98) on all of the workstations and renew all of the leases. Also -
you should exclude the address of your server - we'll assume 10.0.0.2 from
the scope. Your scope should be 10.0.0.1 - 10.0.0.255. I usually remove
10.0.0.1 - 10.0.0.20 from the scope for servers and 10.0.0.200 - 10.0.0.255
for printers. If this does not work, come back and we'll look at some other
options.
(if Win95/98) on all of the workstations and renew all of the leases. Also -
you should exclude the address of your server - we'll assume 10.0.0.2 from
the scope. Your scope should be 10.0.0.1 - 10.0.0.255. I usually remove
10.0.0.1 - 10.0.0.20 from the scope for servers and 10.0.0.200 - 10.0.0.255
for printers. If this does not work, come back and we'll look at some other
options.
Jeff Meaney wrote in message <7eg6l2$rub$1...@oak.prod.itd.earthlink.net>...
Jeff Meaney
Apr 8, 1999, 3:00:00 AM4/8/99
to
Thank you for your help. I revisited my changes, and realized that I had put
back 10.0.0.1 instead of 10.0.0.2 for my server IP address. 10.0.0.1 worked,
but it caused problem with Exchange connectivity. 10.0.0.2 seemed to fix
this. Also, until all the clients rebooted, there was some bizarred behavior
with some stations reporting that their assigned IP address was already in
use (even if these individual stations were rebooted; trying to renew lease
popped up the same "in use" address again and again). Again, once everyone
(10 users) rebooted, all was well. Thanks again. However, I do have one
question: why are there "two" scopes by default in the DHCP admin tool? In
reality, I realize that there is really only one, but it looks like it
appears under two different names. Just curious.
back 10.0.0.1 instead of 10.0.0.2 for my server IP address. 10.0.0.1 worked,
but it caused problem with Exchange connectivity. 10.0.0.2 seemed to fix
this. Also, until all the clients rebooted, there was some bizarred behavior
with some stations reporting that their assigned IP address was already in
use (even if these individual stations were rebooted; trying to renew lease
popped up the same "in use" address again and again). Again, once everyone
(10 users) rebooted, all was well. Thanks again. However, I do have one
question: why are there "two" scopes by default in the DHCP admin tool? In
reality, I realize that there is really only one, but it looks like it
appears under two different names. Just curious.
Best regards,
Jeff Meaney
Redmond, Washington, B.I.D.W.F.M. ("But I don't work for Microsoft")
Stephen King wrote in message ...
0 new messages