Network connection problem

Network connection problem

Post by Tom Edelbro » Thu, 05 Jul 2001 11:24:21



I have a 3com 3c509 that works great on eth0. I just installed a 3c905C and
built the scyld.com driver for it. If I down the eth0 interface and set up
eth1 so it is identical to what eth0 was (ie: I copy ifcfg-eth0 to
ifcfg-eth1 and change the eth0 to eth1 inside of the script) then I do an
"ifup eth1". It can ping it's own address (ie: ping 172.17.10.116), but if I
ping another server (ie: ping 172.17.10.100) I get the following:

PING 172.17.10.100 (172.17.10.100) from 172.17.10.116: 56(84) bytes of data.
From 172.17.10.116: Destination host is unreachable
From 172.17.10.116: Destination host is unreachable
From 172.17.10.116: Destination host is unreachable
From 172.17.10.116: Destination host is unreachable
From 172.17.10.116: Destination host is unreachable
From 172.17.10.116: Destination host is unreachable

But eth1 has the exact same configuration as the 3c509 had on eth0 a few
moments before. So why does the 3c509 work on eth0 and not the 3c905C on
eth1? If I run "tcpdump -i eth1" and ping the Linux box from the NT server
at 172.17.10.100 I can see that the Linux box recognizes something incoming,
yet at 172.17.10.100 it says that a time-out has occurred.

I am running Redhat 6.2 straight from the CD, (kernel 2.2.14-5.0).

Tom

 
 
 

Network connection problem

Post by Tom Edelbro » Thu, 05 Jul 2001 11:25:41


PS: I forgot to mention that I leave both NIC's in the Linux box
simultaneously. Because eth0 works with the 3c509 I simply adopt the eth0
parameters and use them for eth1 with the 3c905 as a test.

Tom


Quote:> I have a 3com 3c509 that works great on eth0. I just installed a 3c905C
and
> built the scyld.com driver for it. If I down the eth0 interface and set up
> eth1 so it is identical to what eth0 was (ie: I copy ifcfg-eth0 to
> ifcfg-eth1 and change the eth0 to eth1 inside of the script) then I do an
> "ifup eth1". It can ping it's own address (ie: ping 172.17.10.116), but if
I
> ping another server (ie: ping 172.17.10.100) I get the following:

> PING 172.17.10.100 (172.17.10.100) from 172.17.10.116: 56(84) bytes of
data.
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable

> But eth1 has the exact same configuration as the 3c509 had on eth0 a few
> moments before. So why does the 3c509 work on eth0 and not the 3c905C on
> eth1? If I run "tcpdump -i eth1" and ping the Linux box from the NT server
> at 172.17.10.100 I can see that the Linux box recognizes something
incoming,
> yet at 172.17.10.100 it says that a time-out has occurred.

> I am running Redhat 6.2 straight from the CD, (kernel 2.2.14-5.0).

> Tom


 
 
 

Network connection problem

Post by Tom Edelbro » Fri, 06 Jul 2001 22:29:42


I have the problem solved. It appears to be a driver problem with the 3COM
3C906C when used with Linux. I replace the card with an Intel Etherexpress
Pro 10/100 card and it works immediately using the same network
configuration as the 3COM had.

Tom


Quote:> I have a 3com 3c509 that works great on eth0. I just installed a 3c905C
and
> built the scyld.com driver for it. If I down the eth0 interface and set up
> eth1 so it is identical to what eth0 was (ie: I copy ifcfg-eth0 to
> ifcfg-eth1 and change the eth0 to eth1 inside of the script) then I do an
> "ifup eth1". It can ping it's own address (ie: ping 172.17.10.116), but if
I
> ping another server (ie: ping 172.17.10.100) I get the following:

> PING 172.17.10.100 (172.17.10.100) from 172.17.10.116: 56(84) bytes of
data.
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable
> From 172.17.10.116: Destination host is unreachable

> But eth1 has the exact same configuration as the 3c509 had on eth0 a few
> moments before. So why does the 3c509 work on eth0 and not the 3c905C on
> eth1? If I run "tcpdump -i eth1" and ping the Linux box from the NT server
> at 172.17.10.100 I can see that the Linux box recognizes something
incoming,
> yet at 172.17.10.100 it says that a time-out has occurred.

> I am running Redhat 6.2 straight from the CD, (kernel 2.2.14-5.0).

> Tom

 
 
 

1. Solaris 8: Network Connection Problem

Hey everyone I am having a problem. -

I am currently running solaris 8 on an intel (ibm 733 mhz) box. Last
week the processor died and I had to ship the computer back to ibm.
When doing so I removed the network card (because it did not come
with the computer) and returned it to ibm. I shipped the package on a
Friday and following Monday big blue return the computer with a
brand new processor. :) They did not format or reconfigure the hard
drive. They simply replaced the processor and upgraded the bios.
Since the hard drive (and Solaris) was still intact , I thought all I had to
do was insert the netword card  and I would be up and running.

Well.... I was wrong.

When it tries to setup up the network connection and initialize on the
network I get a slew of errors. They include but are not limited to:
ip_rput_dlpi(e1X10), dl_error_ack, No such interface, blah blah blah.
Since it cannot successfully connect to the network many of my other
services are not functioning properly.

What am I doing wrong? I reseated the network card (in the same
slot it was previously installed in before), I ran the coniguration
assistant and it successfully indentified the card and proper driver,
and I even checked my "/etc/inet" settings -- which are correct.

What gives?

I am a newbie so please assume nothing. :)

Thanks for your help.

-Frank

--
Posted via CNET Help.com
http://www.help.com/

2. Home network: Cpnnecting 2 PCs

3. Network connection problem

4. Access to Open System Standards

5. Network Connection Problem

6. ip masq: dumb question

7. HELP!!! - Network connection problem

8. copying files from unix to dos system in dos readable format

9. Abit KD7-RAID network connection problem

10. Network connection problem 7.2

11. Network connection problems

12. Linux network connection problem

13. SCO 5.04 NETWORK CONNECTION PROBLEMS