Re: Multihomed Server Routing Woes: Two network segments can't com

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" <ELavidor@xxxxxxxxxxxxxxxxxxxxxxxxx> 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. Lavidor@xxxxxxxxxxxxxxxxxxxxxxxxx> 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.


.

Relevant Pages

  • Re: Security Update hosed box?
    ... All other machines on subnet are in same switch and working as usual. ... All outbound traffic (surf web, ...
    (microsoft.public.windows.server.active_directory)
  • Multihomed Server Routing Woes: Two network segments cant communi
    ... I'm having problems with a multihomed Windows 2003 server that I've ... Both NICs are connected to the same switch. ... and it's got a number of virtual machines on it with IPs of: ... Any other machine on 192.168.1.x cannot ping any machine on 170.34.179.x. ...
    (microsoft.public.windows.server.networking)
  • Re: two subnets on one network
    ... There's a big switch of 3comx5 configured to be one. ... Mainly it is used for 2003 domain of subnet 192.168.255.255. ... The router is for routing to the internet. ... Then you will need SOME router to allow the machines on different subnets ...
    (microsoft.public.windows.server.active_directory)
  • Re: RRAS ip routing and ISA
    ... You can run two subnets on one physical switch, ... Although the machines are connected to the same switch, ... subnet cannot communicate directly with machines in the other subnet. ... at NAT routing rather than using the proxy service in ISA. ...
    (microsoft.public.windows.server.networking)
  • Re: Routing Problem
    ... To be able to ping machines in the 172.16.7.0 subnet from the ... It also has a Linix Server ...
    (microsoft.public.win2000.ras_routing)
Loading