Private IP range not RFC.

Hello,

I have a private IP range of 200.10.0.0 /16. We use NAT on the LAN
interface of the router to gain access to the internet and so far have had
no problems. But what happens when we have to connect to a server on the
internet that has an address in our range? I imagine that it will fail. So
I have to change the range to one of the reserved ranges. I have some
servers that are set up for access by the internet using static NATs? If I
change the IP address on the server and have the ISP change the routers
config to point to the new address, will that be enough. Other than having
to renew the DHCP leases on the clients, is there anything else I need to
do?

TIA,

Jarryd

Hello,

Well it may or may not fail. If you are using a proxy server for your
internet access, the proxy server will translate the DNS name to an IP
address and essentially pull the pages for you.

The proxy server will resolve the ip address correctly, however when the
server requests those pages through your default gateway you may find it
sending requests to your internal LAN either directly or through your routing
infrastructure.

If you are going to change your IP range, you also need to sort out your
infrastructure such as WINS, DHCP and most importantly DNS. You will also
need to update your subnets in Sites and Services...

Basically its not a good idea to change your ip range afterwards and you
could end up with some turmoil before everything settles down.

Mark

"Jarryd" wrote:

> Hello,
>
> I have a private IP range of 200.10.0.0 /16. We use NAT on the LAN
> interface of the router to gain access to the internet and so far have had
> no problems. But what happens when we have to connect to a server on the
> internet that has an address in our range? I imagine that it will fail. So
> I have to change the range to one of the reserved ranges. I have some
> servers that are set up for access by the internet using static NATs? If I
> change the IP address on the server and have the ISP change the routers
> config to point to the new address, will that be enough. Other than having
> to renew the DHCP leases on the clients, is there anything else I need to
> do?
>
> TIA,
>
> Jarryd
>
>
>

"Mark Holland" <(E-Mail Removed)> wrote in message
news:7035E20E-24C9-40C4-9D0F-(E-Mail Removed)...
> Hello,
>
> Well it may or may not fail. If you are using a proxy server for your
> internet access, the proxy server will translate the DNS name to an IP
> address and essentially pull the pages for you.

No it will still fail because the request will never get processed by the
proxy. The Proxy will look at the destination IP and interpret it to be
within the LAN instead of on the Internet and will not process the request.


--

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

"Jarryd" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> no problems. But what happens when we have to connect to a server on the
> internet that has an address in our range? I imagine that it will fail.
So

It will definately fail.

> I have to change the range to one of the reserved ranges. I have some
> servers that are set up for access by the internet using static NATs? If
I
> change the IP address on the server and have the ISP change the routers
> config to point to the new address, will that be enough. Other than
having
> to renew the DHCP leases on the clients, is there anything else I need to

Well you recreate the Static Nat setups, delete and recreate the DHCP Scopes
according to the new addresses, and change the statically assigned machines.
Your WINS should probably just have the whole database deleted and let it
rebuild itself. The DNS could be a problem,..I'm not real sure about it,
but I would suspect that you would want to correct the entries for the DCs
but just delete the other records and let them rebuild. You might be able
to delete all the records and let them rebuild, but you may want a second
opinion.

--

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

Hi,

Well we don't use a proxy server, straight through the gateway. Well my
plan was the following over a weekend:

1. Change the IP address of all the servers with static IPs to use the new
range
2. Ask the ISP on the day to change the router config for the Exchamge, VPN
and Gateway static NAT mappings
3. Change the DHCP Scope to new range, leaving the DNS tab as default to
allow dynamic DNS updates.
4. Add some reserved addresses out the new range for WINS, DNS, Servers,
Gateway
5. Change the Scope Options with new Router, WINS and DNS address
6. Delete all active DHCP leases.
7. Delete all WINS registrations or maybe just uninstall WINS and DHCP and
set them up from scratch
8. Turn on clients one by one and renew DHCP leases (ipconfig/renew)
9. Pray to God that DNS updates all A records properly.

Apart from DNS what could go wrong? And with regards to DNS, there must be
a way to get it to update A records
with the new IP addresses because when a DHCP client lease expires and they
get a new IP address it can handle it. So
why is it differnet when the renewed address belongs to a different subnet
to the old address?

Please let me know your thoughts. I believe I need to do this to eliminate
it as a possible cause of problems connecting
to internet resources (mail/web servers, etc.)

TIA,

Jarryd

"Mark Holland" <(E-Mail Removed)> wrote in message
news:7035E20E-24C9-40C4-9D0F-(E-Mail Removed)...
> Hello,
>
> Well it may or may not fail. If you are using a proxy server for your
> internet access, the proxy server will translate the DNS name to an IP
> address and essentially pull the pages for you.
>
> The proxy server will resolve the ip address correctly, however when the
> server requests those pages through your default gateway you may find it
> sending requests to your internal LAN either directly or through your
> routing
> infrastructure.
>
> If you are going to change your IP range, you also need to sort out your
> infrastructure such as WINS, DHCP and most importantly DNS. You will also
> need to update your subnets in Sites and Services...
>
> Basically its not a good idea to change your ip range afterwards and you
> could end up with some turmoil before everything settles down.
>
> Mark
>
> "Jarryd" wrote:
>
>> Hello,
>>
>> I have a private IP range of 200.10.0.0 /16. We use NAT on the LAN
>> interface of the router to gain access to the internet and so far have
>> had
>> no problems. But what happens when we have to connect to a server on the
>> internet that has an address in our range? I imagine that it will fail.
>> So
>> I have to change the range to one of the reserved ranges. I have some
>> servers that are set up for access by the internet using static NATs? If
>> I
>> change the IP address on the server and have the ISP change the routers
>> config to point to the new address, will that be enough. Other than
>> having
>> to renew the DHCP leases on the clients, is there anything else I need to
>> do?
>>
>> TIA,
>>
>> Jarryd
>>
>>
>>

Jarryd

I need to do a similar job, because of IP addresses not being right. Let us
know how it goes! BTW what is your domain setup - are you on NT, 2k or 2k3?

SW

"Jarryd" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> Well we don't use a proxy server, straight through the gateway. Well my
> plan was the following over a weekend:
>
> 1. Change the IP address of all the servers with static IPs to use the new
> range
> 2. Ask the ISP on the day to change the router config for the Exchamge,
> VPN and Gateway static NAT mappings
> 3. Change the DHCP Scope to new range, leaving the DNS tab as default to
> allow dynamic DNS updates.
> 4. Add some reserved addresses out the new range for WINS, DNS, Servers,
> Gateway
> 5. Change the Scope Options with new Router, WINS and DNS address
> 6. Delete all active DHCP leases.
> 7. Delete all WINS registrations or maybe just uninstall WINS and DHCP and
> set them up from scratch
> 8. Turn on clients one by one and renew DHCP leases (ipconfig/renew)
> 9. Pray to God that DNS updates all A records properly.
>
> Apart from DNS what could go wrong? And with regards to DNS, there must
> be a way to get it to update A records
> with the new IP addresses because when a DHCP client lease expires and
> they get a new IP address it can handle it. So
> why is it differnet when the renewed address belongs to a different subnet
> to the old address?
>
> Please let me know your thoughts. I believe I need to do this to
> eliminate it as a possible cause of problems connecting
> to internet resources (mail/web servers, etc.)
>
> TIA,
>
> Jarryd
>
> "Mark Holland" <(E-Mail Removed)> wrote in message
> news:7035E20E-24C9-40C4-9D0F-(E-Mail Removed)...
>> Hello,
>>
>> Well it may or may not fail. If you are using a proxy server for your
>> internet access, the proxy server will translate the DNS name to an IP
>> address and essentially pull the pages for you.
>>
>> The proxy server will resolve the ip address correctly, however when the
>> server requests those pages through your default gateway you may find it
>> sending requests to your internal LAN either directly or through your
>> routing
>> infrastructure.
>>
>> If you are going to change your IP range, you also need to sort out your
>> infrastructure such as WINS, DHCP and most importantly DNS. You will also
>> need to update your subnets in Sites and Services...
>>
>> Basically its not a good idea to change your ip range afterwards and you
>> could end up with some turmoil before everything settles down.
>>
>> Mark
>>
>> "Jarryd" wrote:
>>
>>> Hello,
>>>
>>> I have a private IP range of 200.10.0.0 /16. We use NAT on the LAN
>>> interface of the router to gain access to the internet and so far have
>>> had
>>> no problems. But what happens when we have to connect to a server on
>>> the
>>> internet that has an address in our range? I imagine that it will fail.
>>> So
>>> I have to change the range to one of the reserved ranges. I have some
>>> servers that are set up for access by the internet using static NATs?
>>> If I
>>> change the IP address on the server and have the ISP change the routers
>>> config to point to the new address, will that be enough. Other than
>>> having
>>> to renew the DHCP leases on the clients, is there anything else I need
>>> to
>>> do?
>>>
>>> TIA,
>>>
>>> Jarryd
>>>
>>>
>>>
>
>

Will do.


"Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
news:uMJif$(E-Mail Removed)...
> Jarryd
>
> I need to do a similar job, because of IP addresses not being right. Let
> us know how it goes! BTW what is your domain setup - are you on NT, 2k or
> 2k3?
>
> SW
>
> "Jarryd" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi,
>>
>> Well we don't use a proxy server, straight through the gateway. Well my
>> plan was the following over a weekend:
>>
>> 1. Change the IP address of all the servers with static IPs to use the
>> new range
>> 2. Ask the ISP on the day to change the router config for the Exchamge,
>> VPN and Gateway static NAT mappings
>> 3. Change the DHCP Scope to new range, leaving the DNS tab as default to
>> allow dynamic DNS updates.
>> 4. Add some reserved addresses out the new range for WINS, DNS, Servers,
>> Gateway
>> 5. Change the Scope Options with new Router, WINS and DNS address
>> 6. Delete all active DHCP leases.
>> 7. Delete all WINS registrations or maybe just uninstall WINS and DHCP
>> and set them up from scratch
>> 8. Turn on clients one by one and renew DHCP leases (ipconfig/renew)
>> 9. Pray to God that DNS updates all A records properly.
>>
>> Apart from DNS what could go wrong? And with regards to DNS, there must
>> be a way to get it to update A records
>> with the new IP addresses because when a DHCP client lease expires and
>> they get a new IP address it can handle it. So
>> why is it differnet when the renewed address belongs to a different
>> subnet to the old address?
>>
>> Please let me know your thoughts. I believe I need to do this to
>> eliminate it as a possible cause of problems connecting
>> to internet resources (mail/web servers, etc.)
>>
>> TIA,
>>
>> Jarryd
>>
>> "Mark Holland" <(E-Mail Removed)> wrote in message
>> news:7035E20E-24C9-40C4-9D0F-(E-Mail Removed)...
>>> Hello,
>>>
>>> Well it may or may not fail. If you are using a proxy server for your
>>> internet access, the proxy server will translate the DNS name to an IP
>>> address and essentially pull the pages for you.
>>>
>>> The proxy server will resolve the ip address correctly, however when the
>>> server requests those pages through your default gateway you may find it
>>> sending requests to your internal LAN either directly or through your
>>> routing
>>> infrastructure.
>>>
>>> If you are going to change your IP range, you also need to sort out
>>> your
>>> infrastructure such as WINS, DHCP and most importantly DNS. You will
>>> also
>>> need to update your subnets in Sites and Services...
>>>
>>> Basically its not a good idea to change your ip range afterwards and you
>>> could end up with some turmoil before everything settles down.
>>>
>>> Mark
>>>
>>> "Jarryd" wrote:
>>>
>>>> Hello,
>>>>
>>>> I have a private IP range of 200.10.0.0 /16. We use NAT on the LAN
>>>> interface of the router to gain access to the internet and so far have
>>>> had
>>>> no problems. But what happens when we have to connect to a server on
>>>> the
>>>> internet that has an address in our range? I imagine that it will
>>>> fail. So
>>>> I have to change the range to one of the reserved ranges. I have some
>>>> servers that are set up for access by the internet using static NATs?
>>>> If I
>>>> change the IP address on the server and have the ISP change the routers
>>>> config to point to the new address, will that be enough. Other than
>>>> having
>>>> to renew the DHCP leases on the clients, is there anything else I need
>>>> to
>>>> do?
>>>>
>>>> TIA,
>>>>
>>>> Jarryd
>>>>
>>>>
>>>>
>>
>>
>
>

Thanks.
We have already run into a problem because of this IP range being wrong. But
it was because a server on our network had the same name as a domain on the
internet, not the same IP address. I solved it temporarily by using hosts
files, but I've got to set up DNS properly when I've changed the IP
addresses otherwise I think I'll still have the same problem.

SW

"Jarryd" <(E-Mail Removed)> wrote in message
news:O%(E-Mail Removed)...
> Will do.
>
>
> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
> news:uMJif$(E-Mail Removed)...
>> Jarryd
>>
>> I need to do a similar job, because of IP addresses not being right. Let
>> us know how it goes! BTW what is your domain setup - are you on NT, 2k or
>> 2k3?
>>
>> SW
>>
>> "Jarryd" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Hi,
>>>
>>> Well we don't use a proxy server, straight through the gateway. Well my
>>> plan was the following over a weekend:
>>>
>>> 1. Change the IP address of all the servers with static IPs to use the
>>> new range
>>> 2. Ask the ISP on the day to change the router config for the Exchamge,
>>> VPN and Gateway static NAT mappings
>>> 3. Change the DHCP Scope to new range, leaving the DNS tab as default to
>>> allow dynamic DNS updates.
>>> 4. Add some reserved addresses out the new range for WINS, DNS, Servers,
>>> Gateway
>>> 5. Change the Scope Options with new Router, WINS and DNS address
>>> 6. Delete all active DHCP leases.
>>> 7. Delete all WINS registrations or maybe just uninstall WINS and DHCP
>>> and set them up from scratch
>>> 8. Turn on clients one by one and renew DHCP leases (ipconfig/renew)
>>> 9. Pray to God that DNS updates all A records properly.
>>>
>>> Apart from DNS what could go wrong? And with regards to DNS, there must
>>> be a way to get it to update A records
>>> with the new IP addresses because when a DHCP client lease expires and
>>> they get a new IP address it can handle it. So
>>> why is it differnet when the renewed address belongs to a different
>>> subnet to the old address?
>>>
>>> Please let me know your thoughts. I believe I need to do this to
>>> eliminate it as a possible cause of problems connecting
>>> to internet resources (mail/web servers, etc.)
>>>
>>> TIA,
>>>
>>> Jarryd
>>>
>>> "Mark Holland" <(E-Mail Removed)> wrote in message
>>> news:7035E20E-24C9-40C4-9D0F-(E-Mail Removed)...
>>>> Hello,
>>>>
>>>> Well it may or may not fail. If you are using a proxy server for your
>>>> internet access, the proxy server will translate the DNS name to an IP
>>>> address and essentially pull the pages for you.
>>>>
>>>> The proxy server will resolve the ip address correctly, however when
>>>> the
>>>> server requests those pages through your default gateway you may find
>>>> it
>>>> sending requests to your internal LAN either directly or through your
>>>> routing
>>>> infrastructure.
>>>>
>>>> If you are going to change your IP range, you also need to sort out
>>>> your
>>>> infrastructure such as WINS, DHCP and most importantly DNS. You will
>>>> also
>>>> need to update your subnets in Sites and Services...
>>>>
>>>> Basically its not a good idea to change your ip range afterwards and
>>>> you
>>>> could end up with some turmoil before everything settles down.
>>>>
>>>> Mark
>>>>
>>>> "Jarryd" wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I have a private IP range of 200.10.0.0 /16. We use NAT on the LAN
>>>>> interface of the router to gain access to the internet and so far have
>>>>> had
>>>>> no problems. But what happens when we have to connect to a server on
>>>>> the
>>>>> internet that has an address in our range? I imagine that it will
>>>>> fail. So
>>>>> I have to change the range to one of the reserved ranges. I have some
>>>>> servers that are set up for access by the internet using static NATs?
>>>>> If I
>>>>> change the IP address on the server and have the ISP change the
>>>>> routers
>>>>> config to point to the new address, will that be enough. Other than
>>>>> having
>>>>> to renew the DHCP leases on the clients, is there anything else I need
>>>>> to
>>>>> do?
>>>>>
>>>>> TIA,
>>>>>
>>>>> Jarryd
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>>
>
>