Linux Windows 2000 crossover cable

Hello all,

Need help with Linux and Windows 2000 networking using a crossover
cable. Fedora Core 4 machine has 3 network cards:
1) Connected to another network and receiving an IP through DHCP (eth2)
[regular patch cable]
2) 192.168.0.100/255.255.255.0 (eth0)
3) 192.168.0.200/255.255.255.0 (eth1) connected to Windows 2000
[Crossover cable]

Windows 2000 machine has 1 network card that is connected to Fedora
Core's eth1. This Windows machine has a static IP of
192.168.0.50/255.255.255.0 (no default gateway).

The crossover cable is in good condition (tested successfully with 2
Windows machines on the same subnet/workgroup). My immediate goal is to
allow both machines to exchange data (will configure samba later;
first, they need to ping one another). At a later time, I would like
Windows 2000 to surf the web through eth2's network.

Currently, both machines do not ping one another. I am missing
something obvious and hope someone could point out.

Thanks.

LinNet.

On 30 Sep 2006 15:28:58 -0700, LinNet wrote:
>Hello all,
>
>Need help with Linux and Windows 2000 networking using a crossover
>cable. Fedora Core 4 machine has 3 network cards:
>1) Connected to another network and receiving an IP through DHCP (eth2)
>[regular patch cable]
>2) 192.168.0.100/255.255.255.0 (eth0)
>3) 192.168.0.200/255.255.255.0 (eth1) connected to Windows 2000
>[Crossover cable]
>
>Windows 2000 machine has 1 network card that is connected to Fedora
>Core's eth1. This Windows machine has a static IP of
>192.168.0.50/255.255.255.0 (no default gateway).
>
>The crossover cable is in good condition (tested successfully with 2
>Windows machines on the same subnet/workgroup). My immediate goal is to
>allow both machines to exchange data (will configure samba later;
>first, they need to ping one another). At a later time, I would like
>Windows 2000 to surf the web through eth2's network.
>
>Currently, both machines do not ping one another. I am missing
>something obvious and hope someone could point out.

You have 1 network range (192.168.0.0/24) divided over 2 network cards.
If your linux computer wants to send an IP packet to 192.168.0.50, how
is it supposed to know which interface it should use?

Pick another range for eth0 or eth11 (e.g. 192.168.1.0/24) and it will
work just fine.

--
Maurice

Maurice Janssen wrote:
> On 30 Sep 2006 15:28:58 -0700, LinNet wrote:
> >Hello all,
> >
> >Need help with Linux and Windows 2000 networking using a crossover
> >cable. Fedora Core 4 machine has 3 network cards:
> >1) Connected to another network and receiving an IP through DHCP (eth2)
> >[regular patch cable]
> >2) 192.168.0.100/255.255.255.0 (eth0)
> >3) 192.168.0.200/255.255.255.0 (eth1) connected to Windows 2000
> >[Crossover cable]
> >
> >Windows 2000 machine has 1 network card that is connected to Fedora
> >Core's eth1. This Windows machine has a static IP of
> >192.168.0.50/255.255.255.0 (no default gateway).
> >
> >The crossover cable is in good condition (tested successfully with 2
> >Windows machines on the same subnet/workgroup). My immediate goal is to
> >allow both machines to exchange data (will configure samba later;
> >first, they need to ping one another). At a later time, I would like
> >Windows 2000 to surf the web through eth2's network.
> >
> >Currently, both machines do not ping one another. I am missing
> >something obvious and hope someone could point out.
>
> You have 1 network range (192.168.0.0/24) divided over 2 network cards.
> If your linux computer wants to send an IP packet to 192.168.0.50, how
> is it supposed to know which interface it should use?
>
> Pick another range for eth0 or eth11 (e.g. 192.168.1.0/24) and it will
> work just fine.
>
> --
> Maurice

Thanks for your suggestion, Maurice. Tried that, but still wont work.

Now I have:
eth0 set to 10.0.0.1/255.0.0.0
eth1 set to 192.168.0.200/255.255.255.0 [connected to Windows 2000]
eth2 set to DHCP [external network]

After `service network restart`, when I try pinging 192.168.0.50, I get
something like this:
PING 192.168.0.50 (192.168.0.50) 56(84) bytes of data.
>From 192.168.0.200 icmp_seq=1 Destination Host Unreachable
>From 192.168.0.200 icmp_seq=2 Destination Host Unreachable
>From 192.168.0.200 icmp_seq=3 Destination Host Unreachable

All the network cards run on 100-full.

"LinNet" <(E-Mail Removed)> writes:

>Hello all,

>Need help with Linux and Windows 2000 networking using a crossover
>cable. Fedora Core 4 machine has 3 network cards:
>1) Connected to another network and receiving an IP through DHCP (eth2)
>[regular patch cable]
>2) 192.168.0.100/255.255.255.0 (eth0)
>3) 192.168.0.200/255.255.255.0 (eth1) connected to Windows 2000
>[Crossover cable]

Why are you doing this?


>Windows 2000 machine has 1 network card that is connected to Fedora
>Core's eth1. This Windows machine has a static IP of
>192.168.0.50/255.255.255.0 (no default gateway).

Make the Linux machine the default gateway, unless you only ever want it to
solely connect to that linux machine.


>The crossover cable is in good condition (tested successfully with 2
>Windows machines on the same subnet/workgroup). My immediate goal is to
>allow both machines to exchange data (will configure samba later;
>first, they need to ping one another). At a later time, I would like
>Windows 2000 to surf the web through eth2's network.

>Currently, both machines do not ping one another. I am missing
>something obvious and hope someone could point out.

Cannot tell you . Not enough info

post the contents of
ifconfig -a
route -n
on the Linux machine.

You have almost certainly screwed up the routing on the Linux machine. It
should have
a specific host route to 192.168.0.50 on eth 3
and then a general net route to 192.168.0.0 netmask 255.255.255.0 on eth2



>Thanks.

>LinNet.

Unruh wrote:
> "LinNet" <(E-Mail Removed)> writes:
>
> >Hello all,
>
> >Need help with Linux and Windows 2000 networking using a crossover
> >cable. Fedora Core 4 machine has 3 network cards:
> >1) Connected to another network and receiving an IP through DHCP (eth2)
> >[regular patch cable]
> >2) 192.168.0.100/255.255.255.0 (eth0)
> >3) 192.168.0.200/255.255.255.0 (eth1) connected to Windows 2000
> >[Crossover cable]
>
> Why are you doing this?

I have a Windows 2000 box sitting with little use (has a gig of memory
and scsi drives). Thought of dumping some data from Linux to Windows
2000 on a regular basis. Added a couple of network cards on the Linux
box and am trying to network these 2 machines.

>
>
> >Windows 2000 machine has 1 network card that is connected to Fedora
> >Core's eth1. This Windows machine has a static IP of
> >192.168.0.50/255.255.255.0 (no default gateway).
>
> Make the Linux machine the default gateway, unless you only ever want it to
> solely connect to that linux machine.
>
>
> >The crossover cable is in good condition (tested successfully with 2
> >Windows machines on the same subnet/workgroup). My immediate goal is to
> >allow both machines to exchange data (will configure samba later;
> >first, they need to ping one another). At a later time, I would like
> >Windows 2000 to surf the web through eth2's network.
>
> >Currently, both machines do not ping one another. I am missing
> >something obvious and hope someone could point out.
>
> Cannot tell you . Not enough info
>
> post the contents of
> ifconfig -a
> route -n
> on the Linux machine.
>
> You have almost certainly screwed up the routing on the Linux machine. It
> should have
> a specific host route to 192.168.0.50 on eth 3
> and then a general net route to 192.168.0.0 netmask 255.255.255.0 on eth2

Thanks, Unruh. I am pretty good at screwed things up and perhaps thats
what happened. To avoid confusion, I removed one network card and
reseated the other one. Well, Fedora didnt want to boot because I
fiddled around with the network cards, but I was able to take care of
that scenario.

Currently, eth0 gets an IP from DHCP without a problem. eth1 is
192.168.0.200/24 and is pinging the Windows 2000 box 192.168.0.50/24.
The Windows 2000 box is pinging back too. Thanks for your comments,
Maurice and Unruh.

At a later time, I will try to get Windows 2000 access to the other
network/outside world through Fedora.

LinNet

You hae routing problems.

route -n

post it here.

"LinNet" <(E-Mail Removed)> writes:


>Maurice Janssen wrote:
>> On 30 Sep 2006 15:28:58 -0700, LinNet wrote:
>> >Hello all,
>> >
>> >Need help with Linux and Windows 2000 networking using a crossover
>> >cable. Fedora Core 4 machine has 3 network cards:
>> >1) Connected to another network and receiving an IP through DHCP (eth2)
>> >[regular patch cable]
>> >2) 192.168.0.100/255.255.255.0 (eth0)
>> >3) 192.168.0.200/255.255.255.0 (eth1) connected to Windows 2000
>> >[Crossover cable]
>> >
>> >Windows 2000 machine has 1 network card that is connected to Fedora
>> >Core's eth1. This Windows machine has a static IP of
>> >192.168.0.50/255.255.255.0 (no default gateway).
>> >
>> >The crossover cable is in good condition (tested successfully with 2
>> >Windows machines on the same subnet/workgroup). My immediate goal is to
>> >allow both machines to exchange data (will configure samba later;
>> >first, they need to ping one another). At a later time, I would like
>> >Windows 2000 to surf the web through eth2's network.
>> >
>> >Currently, both machines do not ping one another. I am missing
>> >something obvious and hope someone could point out.
>>
>> You have 1 network range (192.168.0.0/24) divided over 2 network cards.
>> If your linux computer wants to send an IP packet to 192.168.0.50, how
>> is it supposed to know which interface it should use?
>>
>> Pick another range for eth0 or eth11 (e.g. 192.168.1.0/24) and it will
>> work just fine.
>>
>> --
>> Maurice

>Thanks for your suggestion, Maurice. Tried that, but still wont work.

>Now I have:
>eth0 set to 10.0.0.1/255.0.0.0
>eth1 set to 192.168.0.200/255.255.255.0 [connected to Windows 2000]
>eth2 set to DHCP [external network]

>After `service network restart`, when I try pinging 192.168.0.50, I get
>something like this:
>PING 192.168.0.50 (192.168.0.50) 56(84) bytes of data.
>>From 192.168.0.200 icmp_seq=1 Destination Host Unreachable
>>From 192.168.0.200 icmp_seq=2 Destination Host Unreachable
>>From 192.168.0.200 icmp_seq=3 Destination Host Unreachable

>All the network cards run on 100-full.

Unruh wrote:
> You hae routing problems.
>
> route -n
>
> post it here.

192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
dev14633
x.x.x.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
dev14633
0.0.0.0 x.x.x.1 0.0.0.0 UG 0 0 0 eth0

x.x.x are first 3 octals of a class A IP.

The problem was solved once I reduced confusion arising with 3 network
cards on the machine. Your suggestion did help. Thank you, Unruh.

LinNet


>
> "LinNet" <(E-Mail Removed)> writes:
>
>
> >Maurice Janssen wrote:
> >> On 30 Sep 2006 15:28:58 -0700, LinNet wrote:
> >> >Hello all,
> >> >
> >> >Need help with Linux and Windows 2000 networking using a crossover
> >> >cable. Fedora Core 4 machine has 3 network cards:
> >> >1) Connected to another network and receiving an IP through DHCP (eth2)
> >> >[regular patch cable]
> >> >2) 192.168.0.100/255.255.255.0 (eth0)
> >> >3) 192.168.0.200/255.255.255.0 (eth1) connected to Windows 2000
> >> >[Crossover cable]
> >> >
> >> >Windows 2000 machine has 1 network card that is connected to Fedora
> >> >Core's eth1. This Windows machine has a static IP of
> >> >192.168.0.50/255.255.255.0 (no default gateway).
> >> >
> >> >The crossover cable is in good condition (tested successfully with 2
> >> >Windows machines on the same subnet/workgroup). My immediate goal is to
> >> >allow both machines to exchange data (will configure samba later;
> >> >first, they need to ping one another). At a later time, I would like
> >> >Windows 2000 to surf the web through eth2's network.
> >> >
> >> >Currently, both machines do not ping one another. I am missing
> >> >something obvious and hope someone could point out.
> >>
> >> You have 1 network range (192.168.0.0/24) divided over 2 network cards.
> >> If your linux computer wants to send an IP packet to 192.168.0.50, how
> >> is it supposed to know which interface it should use?
> >>
> >> Pick another range for eth0 or eth11 (e.g. 192.168.1.0/24) and it will
> >> work just fine.
> >>
> >> --
> >> Maurice
>
> >Thanks for your suggestion, Maurice. Tried that, but still wont work.
>
> >Now I have:
> >eth0 set to 10.0.0.1/255.0.0.0
> >eth1 set to 192.168.0.200/255.255.255.0 [connected to Windows 2000]
> >eth2 set to DHCP [external network]
>
> >After `service network restart`, when I try pinging 192.168.0.50, I get
> >something like this:
> >PING 192.168.0.50 (192.168.0.50) 56(84) bytes of data.
> >>From 192.168.0.200 icmp_seq=1 Destination Host Unreachable
> >>From 192.168.0.200 icmp_seq=2 Destination Host Unreachable
> >>From 192.168.0.200 icmp_seq=3 Destination Host Unreachable
>
> >All the network cards run on 100-full.