Multihomed Server Routing Woes: Two network segments can't communi

Hi All,

I'm having problems with a multihomed Windows 2003 server that I've
inherited and is giving me some problems. I'd really appreciate any help or
insight on the issues below.

Here's the setup:

We have an internal server, named "NMS", which has two NICs, with IPs of
192.168.1.5 and 170.34.179.1. Both NICs are connected to the same switch.

A second server is connected to the switch, it's got an IP of 192.168.1.144,
and it's got a number of virtual machines on it with IPs of: 170.34.179.201,
170.34.179.132, and 170.34.179.63.

And then there are client workstations on the 192.168.1.x range also
connected to the same switch or an uplinked switch.

NMS has RRAS setup and enabled as a "router" for "LAN routing only".

Here's my problem symptoms:
- NMS can ping all addresses on 192.168.1.x and 170.34.179.x.
- Any other machine on 192.168.1.x cannot ping any machine on 170.34.179.x.
- All of the machines with 170.34.179.x addresses can ping each other, and
can ping NMS at both 170.34.179.1 and 192.168.1.5. They cannot ping anything
else on 192.168.1.x.

What I'd LIKE to happen is for any machines on 192.168.1.x to be able to
communicate freely with anything on 170.34.179.x. I'm not tied to this
happening via NMS's being multihomed. If there's an easier way to
accommodate this functionality, I'm all for it.


Lastly, here's the routing table for NMS:

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 12 79 d4 e5 92 ...... HP NC7782 Gigabit Server Adapter #2
0x10004 ...00 12 79 d4 e5 93 ...... HP NC7782 Gigabit Server Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.5 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
170.34.179.0 255.255.255.0 170.34.179.1 170.34.179.1 10
170.34.179.1 255.255.255.255 127.0.0.1 127.0.0.1 10
170.34.255.255 255.255.255.255 170.34.179.1 170.34.179.1 10
192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5 10
192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5 10
224.0.0.0 240.0.0.0 170.34.179.1 170.34.179.1 10
224.0.0.0 240.0.0.0 192.168.1.5 192.168.1.5 10
255.255.255.255 255.255.255.255 170.34.179.1 170.34.179.1 1
255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None




Any help or advice is greatly appreciated.

Thanks!

Evan
.

Relevant Pages

  • Re: Weird Network Connectivity Problem
    ... choose a different switch port than the one you've been using. ... When this happens x199 can ping anything on the ... local network EXCEPT the SBS server, ... I've changed NICs, workstation IP, all the simple ...
    (microsoft.public.windows.server.sbs)
  • Re: cant ping between 2 local computers
    ... One is a 2003 Server. ... The DHCP server for the XP Pro box is the firewall on .200, and the gateway is the same firewall. ... There are no rules that prevent pings from one part of the LAN to another on the firewall and all other machines on the same can ping each other just fine. ...
    (microsoft.public.win2000.networking)
  • Re: cant ping between 2 local computers
    ... One is a 2003 Server. ... firewall on .200, and the gateway is the same firewall. ... on firewall] can ping each other just fine. ... and the machines are on the same switch anyway. ...
    (microsoft.public.win2000.networking)
  • Re: Weird Network Connectivity Problem
    ... I would immediately replace the cable between the workstation and the wall, and also the one between the patch panel and the switch. ... also have a Terminal Services server and a Unix box. ... ping x199 returns "request timed out". ...
    (microsoft.public.windows.server.sbs)
  • Re: Server 2003. Problem: How to configure DHCP and PXE
    ... If you use one subnet like you do, the easiest part is to connect all machines to the switch, including the router. ... Then any machine can connect to each other, for the server choose only one NIC and disable the other or use some teaming software, which allows you to use both NIC's with one ip address. ...
    (microsoft.public.windows.server.general)