2 pc's 4 nics - sort of.

  • Thread starter Thread starter David Barber
  • Start date Start date
D

David Barber

My setup:



192.168.1.1 192.168.1.100 10.10.10.1

---------------------[PC 1]---------
| |
----[Internet(adsl)]--[Router] |
firewire
| |
(ethernet)
(ethernet) ---------------------[PC 2]---------

192.168.1.101 10.10.10.2

2 pcs both connected by ethernet(100) via a router and both connected
by firewire (unibrain.com) . I have had to resort this because I can
not transfer files over 40meg without corruption (including with error
checking).

What config should I have so that any packets for 10.10.10.1 go out on
10.10.10.2 and vice versa. I tried using the route command but i still
can't ping the other, if I disable the 192.168.* then it works?

Thank You
 
Configure internal side of router with a static address of 10.10.10.3 so it will be on same netjwork as PCs. PCs should already be set up with static address. Internet side of router is probably set up OK.
 
My setup:



192.168.1.1 192.168.1.100 10.10.10.1

---------------------[PC 1]---------
| |
----[Internet(adsl)]--[Router] |
firewire
| |
(ethernet)
(ethernet) ---------------------[PC 2]---------

192.168.1.101 10.10.10.2

2 pcs both connected by ethernet(100) via a router and both connected
by firewire (unibrain.com) . I have had to resort this because I can
not transfer files over 40meg without corruption (including with error
checking).

What config should I have so that any packets for 10.10.10.1 go out on
10.10.10.2 and vice versa. I tried using the route command but i still
can't ping the other, if I disable the 192.168.* then it works?

Thank You
Click to expand...

I'm sorry, but I don't understand your diagram.

There should be no config needed to make packets for 10.10.10.1 go out
on 10.10.10.2 and vice versa, provided that:

1. The network adapters with those IP addresses are connected to each
other, e.g. they belong to the FireWire adapters in both computers.

2. The subnet mask for those IP addresses is correct, such as
255.0.0.0, 255.255.0.0, or 255.255.255.0. An incorrect mask, such as
255.255.255.192, would cause traffic to be sent to the default
gateway, which is in the 192.168.1.x subnet.

If that doesn't help, please make a copy of the route table and
cut/paste it into a news group reply.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Sorry, the diagram overlaps on display.

Here are the (route prints), with this set up I can not ping
10.10.10.2 and 10.10.10.1, the packets seem to go out on the
192.168.x.x side?

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 10 b5 63 97 5b ...... Accton EN1207D-TX PCI Fast Ethernet
Adapter #2 - Packet Scheduler Miniport
0x3 ...00 41 8e e4 30 7e ...... Unibrain 1394 FireNet Adapter - Packet
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101
20
10.10.10.0 255.255.255.0 10.10.10.2 10.10.10.2
10
10.10.10.2 255.255.255.255 127.0.0.1 127.0.0.1
10
10.255.255.255 255.255.255.255 10.10.10.2 10.10.10.2
10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101
20
192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101
20
224.0.0.0 240.0.0.0 10.10.10.2 10.10.10.2
10
224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101
20
255.255.255.255 255.255.255.255 10.10.10.2 10.10.10.2
1
255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101
1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None

and

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 40 05 5e 53 97 ...... D-Link AirPlus Xtreme G DWL-G650
Adapter #6 - Packet Scheduler Miniport
0x3 ...00 41 5e b9 87 f2 ...... Unibrain 1394 FireNet Adapter - Packet
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.100
20
10.10.10.0 255.255.255.0 10.10.10.1 10.10.10.1
10
10.10.10.1 255.255.255.255 127.0.0.1 127.0.0.1
10
10.255.255.255 255.255.255.255 10.10.10.1 10.10.10.1
10
82.67.37.184 255.255.255.255 192.168.1.1 192.168.1.100
20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100
20
192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.1.255 255.255.255.255 192.168.1.100 192.168.1.100
20
224.0.0.0 240.0.0.0 10.10.10.1 10.10.10.1
10
224.0.0.0 240.0.0.0 192.168.1.100 192.168.1.100
20
255.255.255.255 255.255.255.255 10.10.10.1 10.10.10.1
1
255.255.255.255 255.255.255.255 192.168.1.100 192.168.1.100
1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None
 
Sorry, the diagram overlaps on display.

Here are the (route prints), with this set up I can not ping
10.10.10.2 and 10.10.10.1, the packets seem to go out on the
192.168.x.x side?

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 10 b5 63 97 5b ...... Accton EN1207D-TX PCI Fast Ethernet
Adapter #2 - Packet Scheduler Miniport
0x3 ...00 41 8e e4 30 7e ...... Unibrain 1394 FireNet Adapter - Packet
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 20
10.10.10.0 255.255.255.0 10.10.10.2 10.10.10.2 10
10.10.10.2 255.255.255.255 127.0.0.1 127.0.0.1 10
10.255.255.255 255.255.255.255 10.10.10.2 10.10.10.2 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 20
192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101 20
224.0.0.0 240.0.0.0 10.10.10.2 10.10.10.2 10
224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101 20
255.255.255.255 255.255.255.255 10.10.10.2 10.10.10.2 1
255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101
1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None

and

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 40 05 5e 53 97 ...... D-Link AirPlus Xtreme G DWL-G650
Adapter #6 - Packet Scheduler Miniport
0x3 ...00 41 5e b9 87 f2 ...... Unibrain 1394 FireNet Adapter - Packet
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.100 20
10.10.10.0 255.255.255.0 10.10.10.1 10.10.10.1 10
10.10.10.1 255.255.255.255 127.0.0.1 127.0.0.1 10
10.255.255.255 255.255.255.255 10.10.10.1 10.10.10.1 10
82.67.37.184 255.255.255.255 192.168.1.1 192.168.1.100 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100 20
192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.100 192.168.1.100 20
224.0.0.0 240.0.0.0 10.10.10.1 10.10.10.1 10
224.0.0.0 240.0.0.0 192.168.1.100 192.168.1.100 20
255.255.255.255 255.255.255.255 10.10.10.1 10.10.10.1 1
255.255.255.255 255.255.255.255 192.168.1.100 192.168.1.100 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None
Click to expand...

Thanks for posting the route tables, David.

The first one shows LAN IP addresses 192.168.1.101 and 10.10.10.2.
The second one shows LAN IP addresses 192.168.1.100 and 10.10.10.1.

The host routes for those addresses look fine, and the subnet routes
that use those addresses look fine. I can't explain why a 10.10.10.x
ping would try to use the wrong network adapter. What do you see that
tells you that it's doing that? What do the byte/packet counts for
each network connection show when you do the pings? Could there be a
firewall on either computer that's blocking 10.10.10.x access?

I don't see the need for the host route to 82.67.37.184 in the second
route table, since its gateway address is the default gateway address
(192.168.1.1). However, I don't think that it will cause any
problems.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Back
Top