Re: Changing corporate network addressing


"Scott Micale" <smicale@xxxxxxxxxx> wrote in message
news:22C2131B-1CAC-4E8B-91EE-53A61D1056E0@xxxxxxxxxxxxxxxx

providers so I figured having everyone on DHCP with reservations it would
make the switch easier because I would just have to make a few tweaks in
my DHCP server for the gateway address and then be done.

It is a "different" way to do it,...not an "easier" way,...as you are
seeing. If machines require having the same address all the time then your
choice is Static or DHCP Reserved. If the address shceme changes, then you
are either recreating Reservations or manually reconfiguring the TCP/IP
specs of the machine,...you choice,...they are both a lot of work.

Personally I choose to not have my network infrastructure have its
"survival" dependent on if a DHCP Server remains "alive" and does die on me
someday. Machines that survive by Reservations are therefore dependent on
the DHCP Server,...but Static machines depend on no one. With only a few
Reservations, all of my servers, networking devices, and anything else tied
to the infrastructure run Static Addresses and will continue to survive even
with a total loss of DHCP,...yours will not. Yours is also suseptable to a
rogue DHCP Server being introduced into the system,...like some plugging in
a simple Linksys box into the LAN without disabling the DHCP Service first.
That would make quite a mess when it gives all your Servers and LAN Device
the wrong IP because it would not honor the Reservations.

that a shot later and hope that does it for me. How vacation? Go
anywhere nice?

I went to my backyard,...

.....striped the back wall of the house down to the wall studs,...removed the
electrical Power Service after the power company cut the power,..re-sheeted
the wall with new wood,...covered it with "house wrap" material,...replaced
two Window Assemblies,...installed new 100 amp Power Service equipment,..had
the power company reconnect the power,...

....in a raincoat,...in the pouring rain,...over a three day period.


I think I would have rather created DHCP Reservations.

:-)


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"Phillip Windell" <philwindell@xxxxxxxxxxx> wrote in message
news:#6lcNtHtIHA.1772@xxxxxxxxxxxxxxxxxxxxxxx
I just got back from vacation.
It's at the end of the day and I just now saw the posts. I have time for
a quick answer. We can look at it again tomorrow.

1. You can't change the mask in the Scope
2. Don't screw with the registry. I doubt you would get the results you
want but cannot verify that. But you might make a really cool mess
though.
3. If you have so many Reservations that this is a problem,...then,...you
have too many Reservations. The whole idea of Reservations is to only
have a few. If you have a lot,...then you should have statically
assigned the machines in the first place. Now would be an opportunity to
correct that.
4. Statically assign the machines and forget the Reservations. Determine
if some of the machines *really* need to always have the same IP#,...if
you can do without that then just let as many as you can switch to
Dynamic.
5. Create Reservations for the remaining machines that it would be too
much trouble to do otherwise.
6. Include Statically assigned addresses in the Exclusions Ranges.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or
Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Scott Micale" <smicale@xxxxxxxxxx> wrote in message
news:8D44B111-B009-42A7-894E-02A6EA233316@xxxxxxxxxxxxxxxx
Phillip,

Have you read any of my posts on the registry changes? is this possible
to make it work?

Thanks

"Phillip Windell" <philwindell@xxxxxxxxxxx> wrote in message
news:#Kii7FZmIHA.2328@xxxxxxxxxxxxxxxxxxxxxxx
"Anteaus" <Anteaus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0CC66019-C637-447C-9D0F-E9C77530C924@xxxxxxxxxxxxxxxx

Advice given is good, however I would add that you have ONE network at
present, not two. The 255.255.0.0 mask means that the 3rd and 4th
octets
combine to form one contiguous range of computer numbers.

Ah, yes, that's right.

So the whole migration could be done by moving all the machines into a
range of say 192.168.11.0--192.168.11.255 and since the mask is
255.255.0.0 everything should continue working.

When everything is moved then just change the mask to 255.255.255.0.
Everything will still be in the same segment and should still keep
working.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or
Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------






.

Quantcast