Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Isolating a Server from the rest of the network for testing?
#1
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!
Reply


Messages In This Thread
Isolating a Server from the rest of the network for testing? - by Paul F. - 11-30-2009, 08:23 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)