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

What is the default gateway of the client workstations ? It must be the IP
address of NMS in their subnet for this to work.

ThePro

"E. Lavidor" <E. (E-Mail Removed)> wrote:
> 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.

The default gateway of clients on 192.168.1.x is actually 192.168.1.1, which
is our router. I've changed it on my workstation, and lo and behold, I can
access the machines on the 170.34.179.x network. That's great!

However, all of the machines on 170.34.179.x have 170.34.179.1 (NMS's 2nd
NIC IP) as their default gateway, and they can't talk back to the 192.168.1.x
network.

Any additional thoughts? Thanks very much for your help thus far.

Evan



"ThePro" wrote:

> What is the default gateway of the client workstations ? It must be the IP
> address of NMS in their subnet for this to work.
>
> ThePro
>
> "E. Lavidor" <E. (E-Mail Removed)> wrote:
> > 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.
>

One additional piece of information:

The Primary NIC (192.168.1.5) on NMS has a default gateway of 192.168.1.1
(our router)

The Secondary NIC (170.34.179.1) does not have a default gateway defined.
From my understanding of things, this is correct, but perhaps not...?

Thanks,

Evan


"E. Lavidor" wrote:

> The default gateway of clients on 192.168.1.x is actually 192.168.1.1, which
> is our router. I've changed it on my workstation, and lo and behold, I can
> access the machines on the 170.34.179.x network. That's great!
>
> However, all of the machines on 170.34.179.x have 170.34.179.1 (NMS's 2nd
> NIC IP) as their default gateway, and they can't talk back to the 192.168.1.x
> network.
>
> Any additional thoughts? Thanks very much for your help thus far.
>
> Evan
>
>
>
> "ThePro" wrote:
>
> > What is the default gateway of the client workstations ? It must be the IP
> > address of NMS in their subnet for this to work.
> >
> > ThePro
> >
> > "E. Lavidor" <E. (E-Mail Removed)> wrote:
> > > 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.
> >

"E. Lavidor" <(E-Mail Removed)> wrote:
> One additional piece of information:
>
> The Primary NIC (192.168.1.5) on NMS has a default gateway of 192.168.1.1
> (our router)
>
> The Secondary NIC (170.34.179.1) does not have a default gateway defined.
> From my understanding of things, this is correct, but perhaps not...?
>
This is correct.

You have to change the default gateway to all the computers in the
192.168.1.x subnet for the computers on the other subnet to access them.

ThePro

"E. Lavidor" <(E-Mail Removed)> wrote:
> The default gateway of clients on 192.168.1.x is actually 192.168.1.1,
> which
> is our router. I've changed it on my workstation, and lo and behold, I
> can
> access the machines on the 170.34.179.x network. That's great!
>
> However, all of the machines on 170.34.179.x have 170.34.179.1 (NMS's 2nd
> NIC IP) as their default gateway, and they can't talk back to the
> 192.168.1.x
> network.
>
> Any additional thoughts? Thanks very much for your help thus far.
>
> Evan
>
>
>
> "ThePro" wrote:
>
>> What is the default gateway of the client workstations ? It must be the
>> IP
>> address of NMS in their subnet for this to work.
>>
>> ThePro
>>
>> "E. Lavidor" <E. (E-Mail Removed)> wrote:
>> > 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.
>>