Problem routing 2 NICs on 1PC (WinXP)

[Guest]

Archived from groups: comp.os.ms-windows.networking.tcp-ip,microsoft.public.windowsnt.protocol.routing,microsoft.public.windowsnt.protocol.tcpip (More info?)

Hi,

I have 2 NIC on 1 PC running WinXP SP1. First NIC (10.0.0.100), using
DHCP, to go to the router (10.0.0.1) then to the modem onto the
Internet. The other NIC (192.168.0.100) is connected to another
router (192.168.0.1) and is used for internal connections to the LAN.

I want all traffic to 192.168.0.x to use the second NIC without going
onto the Internet. And all other traffic to go to the internet. So I
set up my NICs like so:

NIC 1
[DHCP]
IP: 10.0.0.100
Netmask: 255.255.255.0
Gateway: 10.0.0.1


NIC 2
[Static IP]
IP: 192.168.0.100
Netmask: 255.255.255.0
Gateway: 10.0.0.1 --> to route to the internet.


The problem is that all traffic keeps going to the 192.168.0.1
interface. And I cannot go to the internet.
nslookup, tracert, ping... all get stuck on the 192.168.0.1 router.

TIA

 

[Guest]

Archived from groups: comp.os.ms-windows.networking.tcp-ip,microsoft.public.windowsnt.protocol.routing,microsoft.public.windowsnt.protocol.tcpip (More info?)

Hi,


What's the default gateway you have for such PC? is it the 10.0.0.1
router? if you do a route print from DOS what comes up?

--

------------------------------------
Claudio Salazar
claudio23mx@yahoo.com.mx
jose_claudio_s@hotmail.com
------------------------------------

"r. t." <cidermania@yahoo.ca> wrote in message
news:15ee7405.0412081745.6db50942@posting.google.com...
> Hi,
>
> I have 2 NIC on 1 PC running WinXP SP1. First NIC (10.0.0.100), using
> DHCP, to go to the router (10.0.0.1) then to the modem onto the
> Internet. The other NIC (192.168.0.100) is connected to another
> router (192.168.0.1) and is used for internal connections to the LAN.
>
> I want all traffic to 192.168.0.x to use the second NIC without going
> onto the Internet. And all other traffic to go to the internet. So I
> set up my NICs like so:
>
> NIC 1
> [DHCP]
> IP: 10.0.0.100
> Netmask: 255.255.255.0
> Gateway: 10.0.0.1
>
>
> NIC 2
> [Static IP]
> IP: 192.168.0.100
> Netmask: 255.255.255.0
> Gateway: 10.0.0.1 --> to route to the internet.
>
>
> The problem is that all traffic keeps going to the 192.168.0.1
> interface. And I cannot go to the internet.
> nslookup, tracert, ping... all get stuck on the 192.168.0.1 router.
>
> TIA

 

[Guest]

Archived from groups: comp.os.ms-windows.networking.tcp-ip,microsoft.public.windowsnt.protocol.routing,microsoft.public.windowsnt.protocol.tcpip (More info?)

On 8 Dec 2004 17:45:31 -0800, cidermania@yahoo.ca (r. t.) wrote:

>
>NIC 2
>[Static IP]
>IP: 192.168.0.100
>Netmask: 255.255.255.0
>Gateway: 10.0.0.1 --> to route to the internet.
>
>
>The problem is that all traffic keeps going to the 192.168.0.1
>interface. And I cannot go to the internet.
>nslookup, tracert, ping... all get stuck on the 192.168.0.1 router.
>

It looks like when you added that gateway on nic2, it has added a
default route to your routing table (overriding the first one) which
is routing all non-LAN traffic out of the 192.168.0.1 (nic2)
interface.

It might be as simple as removing the gateway from nic2. Or you could
add a default route to the router at 192.168.0.1 to point to the other
router at 10.0.0.1 instead.

Jim.

 

[Guest]

Archived from groups: comp.os.ms-windows.networking.tcp-ip,microsoft.public.windowsnt.protocol.routing,microsoft.public.windowsnt.protocol.tcpip (More info?)

That makes senses. Only one interface should have a default gateway
configured.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.


<cidermania@yahoo.ca> wrote in message
news:1102647377.305101.219720@c13g2000cwb.googlegroups.com...
>
> James Egan wrote:
> >
> > It looks like when you added that gateway on nic2, it has added a
> > default route to your routing table (overriding the first one) which
> > is routing all non-LAN traffic out of the 192.168.0.1 (nic2)
> > interface.
> >
> > It might be as simple as removing the gateway from nic2. Or you could
> > add a default route to the router at 192.168.0.1 to point to the
> other
> > router at 10.0.0.1 instead.
> >
> > Jim.
>
> Thanks Jim and Claudio for your help.
>
> I got the problem solved. I don't exactly remember what I did earlier
> but the default gateway was always 192.168.0.1.
>
> What I just did, now, was to keep the default gateway on the 10.0.0.1
> interface and remove the default gateway on the 192 interface. I then
> added a route to the LAN and all worked well.
>
> Thanks again.
>