1. If you prepare carefully, that should be OK. For example, make sure no devices using static IP. Or there are some devices using the static, make changes manually. Also some software may have ini file using the IP. If this is the case, change it manually.
2. I would use class B if I had over 150 computers.
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Jeff" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Not real sure where to start here.
The network I administer now was setup with a "private" address space
of 201.x.x.x/24. Now I know this is a public address and I have no
idea why it was done that way. I'm sure the first thing I need to do
is get it on a real private range. From your experience are there
many issues changing the ip range with regard to dns, ad, and wins?
We are running a 2003 AD network with about 30 static addresses. The
dhcp server shows about 60 available addresses so I don't think that
changing from a 24 bit subnet is required and I don't think we will
ever have more that about 150 computers on the network any way. But I
am about to implement a vpn that will pull dhcp addresses and I don't
want to run out once that starts.
Any advice would be greatly appreciated.
Thanks.
Similar Threads
Linear Mode
