How to Cross Connect 2 Servers?

[SQLDog]

I am trying to create a reporting server. I have 2 hosted servers (windows 2003) each with 2 nic cards. I am trying to setup the cross connect between the two so I can sync data directly. Can anyone help with how to set this up or point me to some resource on how to do this?

The two servers already have the crossover cable installed on the second cards. I was told to just add an IP address to each and use the same subnet mask (and to leave the gateway blank). I did this but am having no luck communicating between the two.

TIA for any help!
Mike

 

[Stevehewitt]

If you are not using a hub or switch, then you are correct - you need a cross-over cable. After that's in place then it really is a case of assigning a unique IP to both servers and place them in the same subnet.

E.G.

NIC 1 on Server 1 = 192.168.1.1
NIC 1 on Server 2 - 192.168.1.2
Subnet = 255.255.255.0

Presuming that server 1 is the 'main' server, then give it another IP on NIC 2 of something like 192.168.1.100, and then disable NIC 2 on server 2.

If this is the configuration you are currently using then let me know if there is still a problem.




Steve.

"They have the internet on computers now!" - Homer Simpson

 

[SQLDog]

Thanks for the response Steve!
Before I go messing with my production server, let me make sure I get this right.

SERVER 1 (Main)
NIC 1
IP 192.168.1.1
Subnet 255.255.255.0
NIC 2
IP 192.168.1.100
Subnet 255.255.255.0

Server 2
NIC 1
IP 192.168.1.2
Subnet 255.255.255.0
NIC 2 (Disabled)

I also want to add that the cross-over cable is between the NIC 2 cards on each server.

Thanks again,
Mike

 

[DTracy]

Look at your drawing, you've disabled the NIC2 card on Server2. Connecting the servers via x-over through NIC2 will fail.

 

[SQLDog]

That is why I was a bit confused with Steve's post. He says "...and then disable NIC 2 on server 2."

I figured it was because I wasn't clear with my initial post that the cross-connect was between the NIC 2s on each server.

Mike

 

[kmcferrin]

The above config will not work. The example that you gave shows both NICs on the first server with addresses on the 192.168.1.0/24 network. The server sees them on the same subnet and will get confused.

For your second NIC use an IP address range that is not in use elsewhere on your network. I would recommend using 192.168.0.1 and 192.168.0.2 and then use a subnet mask of 255.255.255.252. Since you're only using this as a connection between two machines you don't need to allocate an entire /24 network. If you were planning to connect these machines to a switch on the secondary NIC later on, potentially with additional servers on the same network, then you might want a /24.

 

[kmcferrin]

Sorry...

For your example you would have:

Server1:
NIC 1: whatever your usual IP address is
NIC 2: Set to 192.168.0.1 with a mask of 255.255.255.252

Server2:
NIC 1: whatever your usual IP address is
NIC 2: Set to 192.168.0.2 with a mask of 255.255.255.252

On the servers above, NIC1 is connected to your usual network switch. NIC2 is connected to the other server's NIC2 via a crossover cable. NIC2 should not have a default gateway set.