DHCP/DNS changing to public IP from private

We have a flat simple network, no routers no nothing.

We are running DNS/DHCP on NT box and a secondary DNS/DHCP on 2000 and the
NT is in one domain and the 2000 is in another but both servers on site. We
are not in AD but the goal is we are working towards it. The first goal is I
have to get rid of private ip 172...... and go to public IP on everything
internal 166............

I have the 2000 server with everyone on it using our NAT IP's - no one is
getting their IP from the NT box now, except for a couple of static IP's.

So the next step is I add the 166.20.x.x address to the 2000 box (adding
the new public IP to the nic as well as keeping the old one for now). Then I
set up 3 new scopes and address pools using a range of the new public IP's
called 121,122 and 123. The subnet mask is 255.255.255.0. Our current
subnet is 255.255.0.0. So once the workstations start picking up the new
public range I decrease the private range or even disable so the next time
they check in they'll get the new one on the 2000 box. - this is a problem it
didn't work???


Next step Once PC's are getting the new public IP's - DNS is on both NT and
2000 box I make sure both servers are in sync, then demote NT to secondary
DNS - then promote the 2000 to primary. Shut down the NT box and add the
address of 172.24.2.1 to the NIC on 2000 giving me 172.24.x.x and 166.x.x.x
bound to the NIC, removing 172.24.x.Y that is currently assigned to the
server. By giving the 2000 box the NT IP I can take a little extra time
getting the hardcode IP's of 172.24.x.x off the workstations.

Problem is I did these steps; the only thing that worked was the 2000 box is
handing out IP's. The DNS did not work, I thought it did but as the leases
expired on the workstations I was screwed and had to back things out.

What did I miss here? Is it the servers are on different domains? Is it I
missed a step or steps, is it I have no idea what I'm doing :-) ????
NT and 2000 don't play well together?
Could it be because I'm going from one subnet to another?

I'd be grateful for some instructions on how to get dns/dhcp off of NT and
on to 2000 using new public IP's but for now I have to run on both subnets

I'm thinking maybe there is a setting I forgot to change in DNS to make the
2000 primary and the NT secondary.

I wouldn't think changing IP's on the inside would be a big deal, I don't
need them to talk to the outside yet just internally

thanks so much

"jessiemc12" <(E-Mail Removed)> wrote in message
news:18E7ECD8-1622-4D04-A930-(E-Mail Removed)...
> We have a flat simple network, no routers no nothing.
>
> We are running DNS/DHCP on NT box and a secondary DNS/DHCP on 2000 and the
> NT is in one domain and the 2000 is in another but both servers on site. We
> are not in AD but the goal is we are working towards it. The first goal is I
> have to get rid of private ip 172...... and go to public IP on everything
> internal 166............

That is insane. The industry has been trying for years ever since the screwup
of the oringinal exposure of the Internet to the general public to get Networks
*off* of public IP#s and to move them to RFC Private IP#s behind firewalls or
proxys. You are wanting to go the opposite direction,...and create a Active
Directory Domain in the process!!??

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------

I don't have a choice I'm being directed to do so, I agree it is insane but
with no choice how do I make it work

"Phillip Windell" wrote:

> "jessiemc12" <(E-Mail Removed)> wrote in message
> news:18E7ECD8-1622-4D04-A930-(E-Mail Removed)...
> > We have a flat simple network, no routers no nothing.
> >
> > We are running DNS/DHCP on NT box and a secondary DNS/DHCP on 2000 and the
> > NT is in one domain and the 2000 is in another but both servers on site. We
> > are not in AD but the goal is we are working towards it. The first goal is I
> > have to get rid of private ip 172...... and go to public IP on everything
> > internal 166............
>
> That is insane. The industry has been trying for years ever since the screwup
> of the oringinal exposure of the Internet to the general public to get Networks
> *off* of public IP#s and to move them to RFC Private IP#s behind firewalls or
> proxys. You are wanting to go the opposite direction,...and create a Active
> Directory Domain in the process!!??
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft, or
> anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

"jessiemc12" <(E-Mail Removed)> wrote in message
news:36FBB329-739B-427E-B850-(E-Mail Removed)...
>I don't have a choice I'm being directed to do so, I agree it is insane but
> with no choice how do I make it work

Well, I thought about this a bit,..and I just don't want to even get involved in
helping someone do this to themselves. You can tell those making you do this
that someone didn't want to get involved for those reasons maybe it will get
them to think about their foolishness.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------