2 NICs and routing

I reduced this question for easier reading...
I have 2 NICS on two sep. networks (w2k3 svr) and one wrkstation on each
cable connected to the server.
On the SERVER:
NIC1 192.168.2.102 255.255.255.0
NIC2 172.18.6.102 255.255.255.0

On WrkStation1:
NIC 192.168.2.55
On WrkStation2:
NIC 172.18.6.55

I need to route info from one to the other network. (ping the wrkstation IP
on the other network. (Ex Ping 192.168.2.55 from the workstation 172.18.6.55
and get reply..)
I setup 2 static routes on server.
INTERFACE NIC1
Dest: 172.18.6.0 NM:255.255.255.0 Gate:192.168.2.102 Metric 1
INTERFACE NIC2
Dest: 192.168.2.0 NM:255.255.255.0 Gate:172.18.6.102 Metric 1

Doesnt work.. any ideas.. Thanks...

Hi,

Did you enable routing on server? It is disabled by default. Open registry
editor (Regedit) and drill down

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters

Here look for REG_SZ "IPEnableRouter" Change the value from 0 to 1.

I hope this helps,

Mike

"bucrepus" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I reduced this question for easier reading...
> I have 2 NICS on two sep. networks (w2k3 svr) and one wrkstation on each
> cable connected to the server.
> On the SERVER:
> NIC1 192.168.2.102 255.255.255.0
> NIC2 172.18.6.102 255.255.255.0
>
> On WrkStation1:
> NIC 192.168.2.55
> On WrkStation2:
> NIC 172.18.6.55
>
> I need to route info from one to the other network. (ping the wrkstation
IP
> on the other network. (Ex Ping 192.168.2.55 from the workstation
172.18.6.55
> and get reply..)
> I setup 2 static routes on server.
> INTERFACE NIC1
> Dest: 172.18.6.0 NM:255.255.255.0 Gate:192.168.2.102 Metric 1
> INTERFACE NIC2
> Dest: 192.168.2.0 NM:255.255.255.0 Gate:172.18.6.102 Metric 1
>
> Doesnt work.. any ideas.. Thanks...
>
>

The router doesn't need routes added. It has routes already because it is
directly connected to each network segment.

On the client machines, they need either a specific, subnet, or default
route in order to know where to send the packet for further processing.

[A]-------------------[ Router ]---------------------[B]
192.168.2.102 172.18.6.102

[Router]
just needs IP Forwarding enabled. Windows already has routes for each
network setup in the IP stack because the router has interfaces on each
subnet ( so the router already knows how to get to each )

[A]
Route add 172.18.6.0 mask 255.255.255.0 192.168.2.102

[B]
Route Add 192.168.2.0 mask 255.255.255.0 172.18.6.102

Also note that if you are going from a Private address scheme into a public
one, then you need to NAT the packets.

( 172.18.6.102 is a public address scheme )


--
--
Dusty Harper
Microsoft Corporation
----------------------------------------------------------------------------
This posting is provided "AS IS", with NO warranties and confers NO rights
----------------------------------------------------------------------------

"bucrepus" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I reduced this question for easier reading...
> I have 2 NICS on two sep. networks (w2k3 svr) and one wrkstation on each
> cable connected to the server.
> On the SERVER:
> NIC1 192.168.2.102 255.255.255.0
> NIC2 172.18.6.102 255.255.255.0
>
> On WrkStation1:
> NIC 192.168.2.55
> On WrkStation2:
> NIC 172.18.6.55
>
> I need to route info from one to the other network. (ping the wrkstation
IP
> on the other network. (Ex Ping 192.168.2.55 from the workstation
172.18.6.55
> and get reply..)
> I setup 2 static routes on server.
> INTERFACE NIC1
> Dest: 172.18.6.0 NM:255.255.255.0 Gate:192.168.2.102 Metric 1
> INTERFACE NIC2
> Dest: 192.168.2.0 NM:255.255.255.0 Gate:172.18.6.102 Metric 1
>
> Doesnt work.. any ideas.. Thanks...
>
>

You have to enable routing on the box. That is best done using RRAS.

There are *no* static routes to add,...remove whatever you added.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"bucrepus" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I reduced this question for easier reading...
> I have 2 NICS on two sep. networks (w2k3 svr) and one wrkstation on each
> cable connected to the server.
> On the SERVER:
> NIC1 192.168.2.102 255.255.255.0
> NIC2 172.18.6.102 255.255.255.0
>
> On WrkStation1:
> NIC 192.168.2.55
> On WrkStation2:
> NIC 172.18.6.55
>
> I need to route info from one to the other network. (ping the wrkstation
IP
> on the other network. (Ex Ping 192.168.2.55 from the workstation
172.18.6.55
> and get reply..)
> I setup 2 static routes on server.
> INTERFACE NIC1
> Dest: 172.18.6.0 NM:255.255.255.0 Gate:192.168.2.102 Metric 1
> INTERFACE NIC2
> Dest: 192.168.2.0 NM:255.255.255.0 Gate:172.18.6.102 Metric 1
>
> Doesnt work.. any ideas.. Thanks...
>
>

Hi Dusty,

172.18.6.102 is not a public address. It is within 172.16.0.0/12 private
range (172.16.0.0 -172.31.255.255)

Mike

"Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> The router doesn't need routes added. It has routes already because it is
> directly connected to each network segment.
>
> On the client machines, they need either a specific, subnet, or default
> route in order to know where to send the packet for further processing.
>
> [A]-------------------[ Router ]---------------------[B]
> 192.168.2.102 172.18.6.102
>
> [Router]
> just needs IP Forwarding enabled. Windows already has routes for each
> network setup in the IP stack because the router has interfaces on each
> subnet ( so the router already knows how to get to each )
>
> [A]
> Route add 172.18.6.0 mask 255.255.255.0 192.168.2.102
>
> [B]
> Route Add 192.168.2.0 mask 255.255.255.0 172.18.6.102
>
> Also note that if you are going from a Private address scheme into a
public
> one, then you need to NAT the packets.
>
> ( 172.18.6.102 is a public address scheme )
>
>
> --
> --
> Dusty Harper
> Microsoft Corporation
> --------------------------------------------------------------------------
--
> This posting is provided "AS IS", with NO warranties and confers NO rights
> --------------------------------------------------------------------------
--
>
> "bucrepus" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I reduced this question for easier reading...
> > I have 2 NICS on two sep. networks (w2k3 svr) and one wrkstation on each
> > cable connected to the server.
> > On the SERVER:
> > NIC1 192.168.2.102 255.255.255.0
> > NIC2 172.18.6.102 255.255.255.0
> >
> > On WrkStation1:
> > NIC 192.168.2.55
> > On WrkStation2:
> > NIC 172.18.6.55
> >
> > I need to route info from one to the other network. (ping the wrkstation
> IP
> > on the other network. (Ex Ping 192.168.2.55 from the workstation
> 172.18.6.55
> > and get reply..)
> > I setup 2 static routes on server.
> > INTERFACE NIC1
> > Dest: 172.18.6.0 NM:255.255.255.0 Gate:192.168.2.102 Metric 1
> > INTERFACE NIC2
> > Dest: 192.168.2.0 NM:255.255.255.0 Gate:172.18.6.102 Metric 1
> >
> > Doesnt work.. any ideas.. Thanks...
> >
> >
>
>

DOH! Brain Fart. you're right 172.18.6.0 does fall within the private IP
ranges
--
--
Dusty Harper
Microsoft Corporation
----------------------------------------------------------------------------
This posting is provided "AS IS", with NO warranties and confers NO rights
----------------------------------------------------------------------------

"Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Dusty,
>
> 172.18.6.102 is not a public address. It is within 172.16.0.0/12 private
> range (172.16.0.0 -172.31.255.255)
>
> Mike
>
> "Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > The router doesn't need routes added. It has routes already because it
is
> > directly connected to each network segment.
> >
> > On the client machines, they need either a specific, subnet, or default
> > route in order to know where to send the packet for further processing.
> >
> > [A]-------------------[ Router ]---------------------[B]
> > 192.168.2.102 172.18.6.102
> >
> > [Router]
> > just needs IP Forwarding enabled. Windows already has routes for each
> > network setup in the IP stack because the router has interfaces on each
> > subnet ( so the router already knows how to get to each )
> >
> > [A]
> > Route add 172.18.6.0 mask 255.255.255.0 192.168.2.102
> >
> > [B]
> > Route Add 192.168.2.0 mask 255.255.255.0 172.18.6.102
> >
> > Also note that if you are going from a Private address scheme into a
> public
> > one, then you need to NAT the packets.
> >
> > ( 172.18.6.102 is a public address scheme )
> >
> >
> > --
> > --
> > Dusty Harper
> > Microsoft Corporation
>
> --------------------------------------------------------------------------
> --
> > This posting is provided "AS IS", with NO warranties and confers NO
rights
>
> --------------------------------------------------------------------------
> --
> >
> > "bucrepus" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > I reduced this question for easier reading...
> > > I have 2 NICS on two sep. networks (w2k3 svr) and one wrkstation on
each
> > > cable connected to the server.
> > > On the SERVER:
> > > NIC1 192.168.2.102 255.255.255.0
> > > NIC2 172.18.6.102 255.255.255.0
> > >
> > > On WrkStation1:
> > > NIC 192.168.2.55
> > > On WrkStation2:
> > > NIC 172.18.6.55
> > >
> > > I need to route info from one to the other network. (ping the
wrkstation
> > IP
> > > on the other network. (Ex Ping 192.168.2.55 from the workstation
> > 172.18.6.55
> > > and get reply..)
> > > I setup 2 static routes on server.
> > > INTERFACE NIC1
> > > Dest: 172.18.6.0 NM:255.255.255.0 Gate:192.168.2.102 Metric 1
> > > INTERFACE NIC2
> > > Dest: 192.168.2.0 NM:255.255.255.0 Gate:172.18.6.102 Metric 1
> > >
> > > Doesnt work.. any ideas.. Thanks...
> > >
> > >
> >
> >
>
>