Hank
Mon Jun 16 02:06:04 PDT 2008
Thanks, Anthony. I'll add it to the file I'll use if I ever get up the
nerve.....
--
Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
Anthony [MVP] wrote:
> Hank,
> I don't think it is really that big a problem to do.
> The basic idea will be to set up an additional VLAN, and make sure that
> there is unrestricted communication between the two (e.g use WINS).
> Then you can start to migrate resources into the new VLAN. A (very) few
> services will hard code an IP address into a configuration file, but most
> should be OK. Firewall rules will ned to be rewritten. DHCP can server both
> VLAN's.
> Hope that helps,
> Anthony
>
http://www.airdesk.co.uk
>
>
>
> "Hank Arnold (MVP)" <rasilon@aol.com> wrote in message
> news:Ojr2VotzIHA.5832@TK2MSFTNGP02.phx.gbl...
>> I've had problems over the past 6 years that were caused by the original
>> "consultants" who set up the primary subnet to be 192.168.1.nnn. An
>> obvious problem is connecting to a users personal computer (on a router)
>> to our network using a VPN. We have to get the user's router reconfigured
>> to a different subnet since most default to the same one.
>>
>> I'm curious as to what it would take to change our internal IP subnet. to
>> something different. Any thoughts as to what would be impacted would be
>> appreciated. I'm not likely to do it, but it might help explain why we
>> don't do it....
>> --
>>
>> Regards,
>> Hank Arnold
>> Microsoft MVP
>> Windows Server - Directory Services
>
>