Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 456
  • Last Modified:

NT TCP/IP Routing problems with multiple network cards

I have two NT servers ('A' and 'B'),  each with 3 network cards. I have configured TCP addresses as below and have RIP installed on both servers, with IP forwarding enabled. The subnet mask is set to 255.255.255.0 on all interfaces, including the clients.

My problem is that machines can only see (ping) machines on the same subnet. Trying to ping C1 from C2 or C4 from A doesn't work reporting no route to host.


                                       'A'         192.168.2.x           'B'
192.168.1.x   C1  ---------+---------------------------------+---------  C4 192.168.4.x
                                        |                                           |
                                        | 192.168.5.x                       |  192.168.3.x
                                      C2                                        C3              

Server 'A' has NICs with addresses 192.168.1.1, 192.168.2.1 and 192.168.5.1
Server 'B' has NICs with addresses 192.168.3.1, 192.168.4.1 and 192.168.2.2
The clients are configured with an appropriate address for each subnet.

What should the correct subnet mask and default gateways be for each of  the NT server interfaces and the clients? Does the fact that I am using private IP addresses cause problems with the routing?

Thanks for any help,

Ron

0
omega1
Asked:
omega1
1 Solution
 
tonpCommented:
Your easiest solution here would be to make it a class B network, using 172.16.x.x and a netmask of 255.255.0.0. That way, they all have the same network number and are able to cummunicate with each other. (There's no need to change the IP number for this to work of course, so you can try this out with the 192.168.x.x numbers first).
If that's not what you want, is probably best to set up different routes for each netid. Using the route command (from a command prompt just type 'route') you can manually add the various gateways. For example, on machine A you need to add a route for 192.168.1.0 (255.255.255.0) with the exact IP number for the 192.168.1.x NIC (should also work with the 192.168.2.x address I guess). To reach machine B's 192.168.4.x, add a route specifying machine's B 192.168.2.x exact IP address for 192.168.4.0.

0
 
omega1Author Commented:
I think this may have worked, however I found that the problem was actually the default gateways on each of the NICS.

192.168.1.1 - Should have no gateway
192.168.5.1 - Should have no gateway
192.168.2.1 - Gateway 192.168.2.2
192.168.2.1 - Gateway 192.168.2.1
192.168.3.1 - Should have no gateway
192.168.4.1 - Should have no gateway


Having changed the settings to match these, the routing now works.

Thanks for the help.

0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now