Isolating a Server from the rest of the network for testing?

[Paul F.]

I've been playing with this idea in my head... I'm just not quite getting the pieces to fit together.

Heres what I have, and what I'd like to do;

A network, served by a router over which I do not have control. The router is the DHCP server.
I have an OS X Server with a fixed IP number 192.168.1.10.
I can't change this Servers IP without disrupting network use.

I have a SECOND OS X Server that I am setting up to REPLACE the first server. It will have the same address.
Over the Holiday week, I set up DNS and OpenDirectory services on the "new" server.

What I'd LIKE to do is (with a router, or my "old" OS X Server), isolate the NEW server on it's own mini-network, and NOT have to change the IP address of the NEW server, so I can have it up for testing purposes...
Maybe using NAT...

And I think, maybe, with that, I might have just answered my own question...

I need an old router that I can assign a fixed IP on my network, with a DHCP server on the "inside" of that router (the outside being my existing network), and the new server with it's fixed IP?

Does this sound right?
Or am I about to foul things up on a biblical scale? :-)

(this "other" router would probably be an old D-Link with finicky wireless that I have at home...).

I know this is possible... I just need to know if it's possible with essentially zero cost, and as little blood-loss as possible!

[mikebw]

Yeah, you could make a network inside a network, that's essentially what the router who is serving you is doing. Not sure if this is of any use- http://en.wikipedia.org/wiki/Subnetwork

[Paul F.]

Sort of of use.. yes.
Thanks.

As I was typing my post, I think I clarified my idea some more..
I'm going to round up that old D-Link and poke around it's settings and see if I can get it set up so the "new" server will "think" it's on the regular network, when in fact it's on a sub-network... so that the existing Server doesn't freak out ( it doesn't know it's day are numbered...).

[C(-)ris]

What is your goal for the other server? Are you just trying to get it internet access? If you put that other router in and Double NAT it, you will get on the internet, but that new server won't see anything on the other network.

[Paul F.]

Mostly, I'm trying to get it internet access, while at the same time letting me get into it via Apple Remote Access, and being able to continue configuring things like Automounts, sharepoints, and such... without disturbing the main network by having it use the same IP number as my primary server.

[C(-)ris]

To get ARD you will have to configure port forwarding on that router to the server and then you put in that routers IP address on ARD. So yes, it will work for you.

[Paul F.]

Cool... now I just have to find that old router! :-)