Fedora Linux Support Community & Resources Center
  #1  
Old 26th July 2005, 04:14 PM
oxman's Avatar
oxman Offline
Registered User
 
Join Date: Aug 2004
Location: Umpqua National Forest
Age: 65
Posts: 36
Destination Host Unreachable

Any help is much appreciated.

netgear 4 port dual speed hub DS104

two computers with neatgear FA310TX NICs

Linux Fedora Core 3 on both boxes.

Box#1
Code:
[root@singingfalls /]# /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:A0:CC:50:38:C7
          inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:1 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:3204 (3.1 KiB)
          Interrupt:9 Base address:0x2000
Not sure what to do about the RX error:1



Box#2
Code:
[root@singingfalls /]# /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:A0:CC:3B:38:C2
          inet addr:192.168.10.2  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::2a0:ccff:fe3b:38c2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:1898 (1.8 KiB)
          Interrupt:5 Base address:0x2000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2033 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2033 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2154525 (2.0 MiB)  TX bytes:2154525 (2.0 MiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
The hub has a consistant recycling of flashing lights on one cable and I am unable to ping the other box from either computer. They are just not talking. I have tested AND switched cables.
I have the hub set for "normal".

This network system was purchased for me by a friend and it seemed simple to install. I have temporarily turned off the firewalls to facilitate the network install.
__________________
http://www.singingfalls.com
linux user #199890 the ox is grateful
asus a8n-sli deluxe
opteron (denmark-175)
2 gigs corsair ram
2 sata 250 hd
1 ide 40 gig hd
evga nvidia 7900 gto
soundblaster audigy2 sz
sony /cd/dvd rw
Reply With Quote
  #2  
Old 27th July 2005, 01:15 AM
kg4cbk Offline
Registered User
 
Join Date: Feb 2005
Posts: 675
An occasional TX or RX error is normal. If you get consistently increasing count of errors then there is a problem to be concerned about.

When you say that one port on the hub has a constent flashing liight that is on one port only?

What number ports are you using? On some netgear hubs the first port has a switch to change it to an uplink port from a standard port. At least in older hubs/switches they sold. Many switches now are able to auto detect and change depending on the cable that is connected.

You should look at the port settings on your linux systems using ethtool. Specifically look for speed and duplex settiings.

Example from one of my systems:

ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Reply With Quote
  #3  
Old 27th July 2005, 01:55 AM
oxman's Avatar
oxman Offline
Registered User
 
Join Date: Aug 2004
Location: Umpqua National Forest
Age: 65
Posts: 36
Thank you very much for the reply.

Quote:
Originally Posted by kg4cbk
An occasional TX or RX error is normal. If you get consistently increasing count of errors then there is a problem to be concerned about.
It is consistantly at least one error.

Quote:
When you say that one port on the hub has a constent flashing liight that is on one port only?
Yes only on ONE CABLE no matter which port I use.

Quote:
What number ports are you using? On some netgear hubs the first port has a switch to change it to an uplink port from a standard port. At least in older hubs/switches they sold. Many switches now are able to auto detect and change depending on the cable that is connected.
There are four cable ports on the hub. I'm using two. It also has an "uplink/normal" button on the face of the hub. I have it set at normal at the moment but did try it with uplink also.

Quote:
You should look at the port settings on your linux systems using ethtool. Specifically look for speed and duplex settiings.
Code:
root@singingfalls]# ethtool eth0
Settings for eth0:
No data available
That's what I get on both boxes. When booting up and shuting down the eth0 is acknowledged. Also, the Network Device and Connection utility says I am "active". As you can see the ethtool eth0 command gives me nothing on either box. Wierd?
__________________
http://www.singingfalls.com
linux user #199890 the ox is grateful
asus a8n-sli deluxe
opteron (denmark-175)
2 gigs corsair ram
2 sata 250 hd
1 ide 40 gig hd
evga nvidia 7900 gto
soundblaster audigy2 sz
sony /cd/dvd rw
Reply With Quote
  #4  
Old 27th July 2005, 02:13 AM
kg4cbk Offline
Registered User
 
Join Date: Feb 2005
Posts: 675
Not sure why you don't get any info from ethtool.

But based on your description you may have a bad cable. Can you try a different one that you know is good?

Most switches should have a steady led indicating good link integrity. Another led normally indicates port activity.

If all the leds are flashing then it may be an error indication. Make sure you have good cables and are using normal cables not cross over cables.
Reply With Quote
Reply

Tags
destination, host, unreachable

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Destination Host Unreachable kvvsrinivas Servers & Networking 3 14th October 2008 01:24 PM
Destination Host Unreachable :( skyy Servers & Networking 8 14th March 2006 05:15 PM
Destination Host Unreachable alin2 Servers & Networking 5 10th December 2004 12:40 AM


Current GMT-time: 15:12 (Friday, 24-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat