2 Leased Machines, How do I configure Private Network

Hi
I'm really a software developer but we're leasing two machines in a datacentre to host our software.
They are both Windows 2003 servers and both have 2 network cards. 1 each to connect to the network and the other one connected with a cross cable to each other.
I want to be able to configure a private network between the two machines but I don't even know how to allocate an IP address to the private NIC cards. Each machine has 5 IP Addresses each. I would also like to at a later date to have VPN connections into this private network from our local machines.
Thanks for any help.

Rob
homedaqAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pseudocyberCommented:
On the two NICs connected to each other with a crossover cable, in the TCP/IP properties, enter a "static IP" - not dynamic.

On Machine1
172.16.0.1
255.255.255.0

On Machine2
172.16.0.2
255.255.255.0

This assumes you're not using a 172.16.0.0/24 network anywhere else.  I would not put a default gateway on them, because you don't want to do any default traffic out these interfaces, you only want traffic which is specifically going to the other machine.

That's all you have to do.  The machines will learn of directly attached networks and will be able to talk to each other.

If you want to make it a little easier for yourself, you could modify the hosts file at,
c:\windows\system32\drivers\etc\hosts
You could put in a name for the other machine and the IP address

172.16.0.2       Othermachinename

Then you could refer to the other machine by it's name "Othermachinename" instead of the IP - this is a better way to code - to request a variable name for the other machines and then have the code refer to that machine name - that way end users can change IP's without affecting code.

Hope this helps.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
homedaqAuthor Commented:
Should I use one of my allocated IP on each machine would this be safer in the long run.
pseudocyberCommented:
No.  

I'm assuming you're going to use your other allocated IP's on your other NIC's right?  Odds are they're in the same network.  

You want private IP's which the servers will know about and not route out their default gateways (your other NICs)


Example:
    -------------network-----------------
     |                                             |
Allocaed IP1                          Allocated IP2
192.168.1.1                          192.168.1.2

Server1                                    Server2

 PrivateIP1                                   PrivateIP2
172.16.0.1---- Crossover Cable---- 172.16.0.2
homedaqAuthor Commented:
Thanks for help.
pseudocyberCommented:
You're welcome.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.