Need to Connect two Servers on different Networks

[arnold8]

Hi,

I have 2 networks setup... connected to 4 switches. Each network uses 2 switches. The server of network "A"uses IP addy of 192.168.10.1 and the other server on network "B" uses has an ip of 192.168.100.1
The LAN is not physically seperated.
Question 1) how can I get each server to conect to each other for file transfer ?
Question 2) How can I get clients on either network to connect to each other ?

The Server Machines are Win2000 Advanced Server.
Do I need WINS ? if yes how should it be configured ?

 

[brontosaurus]

assuming you're using a subnet mask of 255.255.255.0 , you'll need some sort of router to connect the networks. you could cheat and use a class B mask, which would make these addresses the same network...

 

[tekieVB]

Easy....

Server A - 1 NIC
Server B - 2 NICs

1. On Server B add a second NIC and set it up to route between the two networks.

2. Then on Server B you can turn on WINS or DNS.

3. Now depending on if you are using static ip or dhcp for your ip address assignment add the corresponding entries for DNS, WINS, and/or Default GW to be Server B.

Your in buisness....

Happy Holidays!

 

[arnold8]

hi Bronto,

You mean that by juz putting in a 255.255.0.0 on both the server machines this would solve the problem, or do I need to do this on all client machines too ?

and a reply to Jtb65, both servers currenty have 2 Nics as NATing is enabled of internet access to clients.
Should I put a third nic and enable it as a router to route traffic to the other network ?

 

[tekieVB]

Since you are using NAT for Internet, I would not recommend adding a third NIC. It is kind of puzzling why both servers are NATing for the Internet. I am guessing you did this because of the different ip networks?

How many clients does the two servers serve? If you do not have more than 252 client pc's/ip printers, I would make it all one network.

If you do have more than 252 ip enabled devices (Servers take two ip addresses already), I would just change the subnet mask on both servers and clients to a class B subnet mask.

What brontosaurus stated, might be easier for you.

Good Luck.....

 

[arnold8]

I have done this setup bec the company needed to have a seperate ip network. Initially I had one server with 3 Lan adapters and NAT for internet for the two networks.Now they wanted the servers to be seperate too ! I didn't understand what bronto meant! if I change the server subnet to 255.255.0.0 , then I will need to configure all the clients with these same settings. BTW I have arount 70 Clients on each network.

 

[tekieVB]

Yes, if you change the subnet mask to 255.255.0.0 you will need to change it on all of the workstations as well. Are you using DHCP? If so, the change is not that hard to implement.
If the outside NICS on both servers are on the same physical subnet why don't you just add routes to the server's routing tables so that they know about each others internal networks?

 

[arnold8]

Hello jtb65 can you pls help me further with this...
On which interface should I define the static routes ?
LAN or WAN ? and what would be their configuration.

I have one server with ip 192.168.10.1 and the other on 192.168.100.1.

 

[tekieVB]

on Server 192.168.10.1:
WAN......

route add 192.168.100.0 mask 255.255.255.0 (external ip of other server) -p

on Server 192.168.100.1:
route add 192.168.10.0 mask 255.255.255.0 (external ip of other server) -p

[ -p means persistent - stays after rebooting the servers ]

you can open a cmd prompt and type route /? to get more info.

Good Luck!
JTB65