CHANGING TO NEW IP ADDRESS FROM SETUP ADDRESS

Hi All,

Just wondering if someone could tell me what kind of issues or problems that
might be involved in changing windows server over to a new ip addressing
scheme from the one that was used when the server was set up? i.e server
was all setup using 10.10.1.0 255.255.255.0 and going to say something like
11.11.1.0 255.255.255.0?

Just wondering if you can do this without hosing up the whole thing?

Thanks,

Jeff




Jeff

i maybe corrected here but if you change from 10.10.1.0 to 11.11.1.0 then
you are changing subnet .... so ether you :

1. change all other machines on the lan to the same subnet range.

or

2. use routing to bridge the subnet and pass traffic (i only know how to do
this with hardware sorry not with windows servers).

...... IMO.

Hope this helps.
Scott

It depends on what is running on it and what might be "tied" to the old IP#.
Web sites and FTP sites in IIS are one example of this.

It is very questionable that you would use 11.11.1.0 since that is a Public
Address set that is owned by somebody.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of my
employer or anyone else associated with me.
-----------------------------------------------------




"Jeff" <(E-Mail Removed)> wrote in message
news:kaLth.1695$(E-Mail Removed) ...
> Hi All,
>
> Just wondering if someone could tell me what kind of issues or problems that
> might be involved in changing windows server over to a new ip addressing
> scheme from the one that was used when the server was set up? i.e server was
> all setup using 10.10.1.0 255.255.255.0 and going to say something like
> 11.11.1.0 255.255.255.0?
>
> Just wondering if you can do this without hosing up the whole thing?
>
> Thanks,
>
> Jeff
>
>

Yes you are correct, sorry i miss typed i meant to type 10.11.1.0. Just
changing the second 10 to 11. I am having a VPN issue that i can not seem
to get around due to both sides being on the same ip addressing. I am not
sure how to do the "add route" statement so though that really the easiest
way would be to just change my IP scheme which should solve that problem,
but did not want to create a whole new set of problems on my working server
that I finally got running about the way I wanted it to.

Thanks for the help.

Jeff

"Phillip Windell" <@.> wrote in message
news:%23$(E-Mail Removed)...
> It depends on what is running on it and what might be "tied" to the old
> IP#. Web sites and FTP sites in IIS are one example of this.
>
> It is very questionable that you would use 11.11.1.0 since that is a
> Public Address set that is owned by somebody.
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> The views expressed are my own (as annoying as they are), and not those of
> my employer or anyone else associated with me.
> -----------------------------------------------------
>
>
>
>
> "Jeff" <(E-Mail Removed)> wrote in message
> news:kaLth.1695$(E-Mail Removed) ...
>> Hi All,
>>
>> Just wondering if someone could tell me what kind of issues or problems
>> that might be involved in changing windows server over to a new ip
>> addressing scheme from the one that was used when the server was set up?
>> i.e server was all setup using 10.10.1.0 255.255.255.0 and going to say
>> something like 11.11.1.0 255.255.255.0?
>>
>> Just wondering if you can do this without hosing up the whole thing?
>>
>> Thanks,
>>
>> Jeff
>>
>>
>
>

"Jeff" <(E-Mail Removed)> wrote in message
news:TUNth.1709$(E-Mail Removed) t...
> Yes you are correct, sorry i miss typed i meant to type 10.11.1.0. Just
> changing the second 10 to 11. I am having a VPN issue that i can not seem to
> get around due to both sides being on the same ip addressing. I am not sure
> how to do the "add route" statement so though that really the easiest way
> would be to just change my IP scheme which should solve that problem, but did
> not want to create a whole new set of problems on my working server that I
> finally got running about the way I wanted it to.

Aside from www and FTP issues with IIS, you are probably fine.
Since the Internal AD/DNS machine would be changing its address, that will have
to be reflected in the Clients TCP/IP Config. The same for any WINS Servers.
Most of it is just normal common-sense stuff.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of my
employer or anyone else associated with me.
-----------------------------------------------------

Thanks Phillip,

I was able to chnage over the ip scheme I believe successfully. The only
snag I ran intowas when i tried to change the ip address in scope1, it would
not let me. So i just deactivated that scope and created a new Scope2 with
the same information except with the new IP addresses, and that seemed to
take fine. Under server options I noticed that it added a couple of more
entries in there then what was in the scope1.

Atleast from remote desktop(as i am not at home at the moment) everything
seems to be working well, I can still get out to the internet, browse the
network(well what is left of it, I will have to reboot a couple of systems
when I get home to get the new IP). My friend was able to vpn in and was
able to successfully navigate.

So really the only thing left that I would like to figure out is how to get
my computers on the 192.168.1.0 network to be able to navigate to the
computers on the 10.11 network. The computers on the 10.11 network can get
to any of the computers on the 192.168 network either by name or ip, but i
just can not figure out how to get the 192.168 computers to get to the 10.11
network. Any ideas?

Thanks,

Jeff

"Phillip Windell" <@.> wrote in message
news:%23EhlNQ$(E-Mail Removed)...
> "Jeff" <(E-Mail Removed)> wrote in message
> news:TUNth.1709$(E-Mail Removed) t...
>> Yes you are correct, sorry i miss typed i meant to type 10.11.1.0. Just
>> changing the second 10 to 11. I am having a VPN issue that i can not
>> seem to get around due to both sides being on the same ip addressing. I
>> am not sure how to do the "add route" statement so though that really the
>> easiest way would be to just change my IP scheme which should solve that
>> problem, but did not want to create a whole new set of problems on my
>> working server that I finally got running about the way I wanted it to.
>
> Aside from www and FTP issues with IIS, you are probably fine.
> Since the Internal AD/DNS machine would be changing its address, that will
> have to be reflected in the Clients TCP/IP Config. The same for any WINS
> Servers. Most of it is just normal common-sense stuff.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> The views expressed are my own (as annoying as they are), and not those of
> my employer or anyone else associated with me.
> -----------------------------------------------------
>
>

"Jeff" <(E-Mail Removed)> wrote in message
news:r1Qth.1715$(E-Mail Removed). ..
> not let me. So i just deactivated that scope and created a new Scope2 with
> the same information except with the new IP addresses, and that seemed to take
> fine.

You can delete the old scope since those addresses don't exist on your LAN
anymore.

> So really the only thing left that I would like to figure out is how to get my
> computers on the 192.168.1.0 network to be able to navigate to the computers
> on the 10.11 network. The computers on the 10.11 network can get to any of
> the computers on the 192.168 network either by name or ip, but i just can not
> figure out how to get the 192.168 computers to get to the 10.11 network. Any
> ideas?

That depends on where things are physically located and what you currently did
to get the partial functionality that you have. I can make some assumptions and
try from there, but my assumptions may be wrong.

I am assuming:
1. Both segments (10.11 & 192.168) are at the same physical location.
2. You may have connected the segments using a broadband "router".
3. You have an Active Directory Domain

If this was a broadband "router",..you just simply can't do that. Those are not
"real" routers. People make this mistake all the time because they are called
"routers" on the store shelves, when in fact they are not routers but are
nothing but NAT Devices.

Once a true LAN Router is between the segments you then have every single client
on the LAN use the LAN Router as their Default Gateway,...they will use the
router IP# that faces their respective segment. Then, I assume, that one of
those segments connects to the Internet with some kind of NAT Device,...so that
NAT Device will then become the Default Gateway of the LAN Router (and only the
LAN Router). The Internet NAT Device would then have a Static Route added to it
that tells it to use the LAN Router as the "path" to get to the opposite
segment.

DNS (assuming an Active Directory Domain exists)
Every machine on the LAN (no matter what segment) must use the AD/DNS for the
DNS service in their TCP/IP Specs. Within the DNS service config on the DNS
Machine itself you will list the ISP's DNS in the Forwarders List. The AD/DNS
machine then needs the ability granted to it by the Internet Device to make
outbound DNS queries to at least the ISP's DNS.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of my
employer or anyone else associated with me.
-----------------------------------------------------