"G. Kapetanios" wrote:
> 
> Thanks for the reply
> 
> ifconfig gives the followng
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Bcast:127.255.255.255
>           Mask:255.0.0.0
>           UP BROADCAST LOOPBACK RUNNING  MTU:3584  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
> eth0      Link encap:Ethernet
>          HWaddr 00:00:E8:CC:28:7D
>        inet addr:194.81.117.61  Bcast:194.81.117.255
>         Mask:255.255.255.0
>       UP BROADCAST RUNNING MULTICAST  MTU:1500  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           Interrupt:3 Base address:0x300
> 
> route -n gives
> 
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 194.81.117.0    0.0.0.0         255.255.255.0   U     0      0        1
> eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 0.0.0.0         194.81.117.1    0.0.0.0         UG    1      0        1
> eth0
> 
> Notice that 194.81.117.1 is the gateway I have given in the configuration
> 
This info looks fine to me.


> dmesg gives the following network card related info.
> 
> loading  device 'eth0'...
> ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED])
> NE*000 ethercard probe at 0x300: 00 00 e8 cc 28 7d
> eth0: NE2000 found at 0x300, using IRQ 3.
> loading device 'eth1'...
> 
Now why does it say loading device eth1? I have no clue. Hmmm...

> It seems to me that the card is correctly detected the problem is with the
> gateway I guess since route (not route -n) hangs
> 
Just for grins try pinging 194.81.117.1. Do not use the host name. Use
the IP address. Does it still give you problems?

If it does not, you should take a look at /etc/resolve.conf and make
sure you have your DNS server listed there. The reason why route hangs
is because your machine cannot find a host name for the IP address of
your gateway. 

If you cannot ping an IP address, the network card might not be workign
right. It could be a bad network cable or wall jack.

Hope this helps

-- 
Paul Miller
[EMAIL PROTECTED]
begin:vcard 
n:Miller;Paul
x-mozilla-html:FALSE
org:Talons
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:President
note:The Spirit of the University of North Texas
x-mozilla-cpt:;0
fn:Paul Miller
end:vcard

Reply via email to