Why change the IP addresses at all? What is wrong with having the existing
remote site running in its own subnet?
If you move them so that they are all at the same site, what is wrong
with simply replacing the WAN link with a LAN router?
"Jo" <(E-Mail Removed)> wrote in message
news:12680815-7900-4B4B-9F6D-(E-Mail Removed)...
> Hello Guys,
>
> We are looking to collapse a remote Data Center back into the main and
> I wanted to get the recommendations on the best way to go about this. For
> ease of explanation I call the remote location , location X , and the main
> center we are collapsing into, location A.
>
> Location X currently hosts its own AD/WINS/DNS, Print, App, ISA, and
> Exchange Servers. They are running on a 10.5 subnet and connect to
> location A
> via Gig Fiber. Location A is currently running on the 10.20 network.
>
> What would be the recommended route to move the Servers over to
> location A ( 10.20.X.X Network ) from location X ( 10.5.X.X Network) ? Is
> it
> as easy as change the IP Settings on the NIC for the AD Servers, host
> record
> in DNS, and pointing the clients to the AD/DNS Server that has the new IP
> in
> the clients DNS Server entry ? Both the AD Servers are the DNS Servers
> for
> the Domain , so I assume if I change the IP Settings( IP Address, Mask,
> Gateway) on the Servers Nic, change the DNS Host Entry for that Server on
> that server, point all the clients to the new DNS Servers via their DNS
> Server IP address for the clients Network Config, the clients should be
> able
> to access the server on the new subnet ? Would changing the IP Address on
> the AD Servers mess anything up in AD, DNS, Wins ?
>
> Also, What would be the recommended route for the Exchange 2003 Server ?
>
>
|