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



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

  • 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: Multihomed Server Routing Woes: Two network segments cant com
    ... The Primary NIC on NMS has a default gateway of 192.168.1.1 ... access the machines on the 170.34.179.x network. ... Both NICs are connected to the same switch. ... Any other machine on 192.168.1.x cannot ping any machine on ...
    (microsoft.public.windows.server.networking)
  • Re: Multihomed Server Routing Woes: Two network segments cant 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. ... access the machines on the 170.34.179.x network. ... Both NICs are connected to the same> switch. ... > - Any other machine on 192.168.1.x cannot ping any machine on ...
    (microsoft.public.windows.server.networking)
  • Re: 1 XP home machine cant access 1 XP Pro machines shares / printer sometimes
    ... are acting as servers for folders and printer shares. ... Everything has been fine with all the machines. ... B & F are on the same unmanaged switch with a single cat 5 cable ... CAN PING B FROM F ALL THE TIME AND F FROM B all the time. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Getting router to talk to client subnet/VLAN
    ... The machine I use to manage the network is called NMS and is on ... NMS can ping them as well. ... to ping the router. ...     no ip unreachables ...
    (comp.dcom.sys.cisco)