[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: network/name resolution problems



Can you type "ifconfig" into a konsole and paste the results here please? It appears as though you haven't supplied a valid DNS server address.

Replying to the message sent by Dan Davison  on Mon, 17 Nov 2003 11:07:07 -0600 (CST), received at 09:53:41 on 18/11/2003. Dan Davison wrote:
>Dear debian users, could someone put me out of my trying-to-get-online
>misery please?
>
>I am trying to make an ethernet connection to a university network.
>
>The network settings I am using work under windows on my other partition,
>and worked on another machine running debian with a 2.2.xx kernel.
>
>I am running kernel 2.4.22. If this is unwise for someone as
>linux-incompetent as me, my excuse is that it seemed like I needed it to
>have support for my ATI radeon 9600 graphics card (of which more on
>another post i'm afraid) and my SiS 900 fast ethernet card.
>
>dmesg includes
>SiS 900 PCI Fast Ethernet at 0xx800
>ifup eth0 gives
>eth0: Media Link On 10mbps half-duplex
>as does going through dpkg-reconfigure etherconf (whether I choose dhcp or
>not) which all sounded quite positive to me.
>
>However, all my attempts to ssh or ping or lynx fail with complaints about
>name resolution, even using an IP address rather than host.domain, e.g:
>
>> ping arizona.princeton.edu [in my domain]
>ping: unknown host arizona.princeton.edu
>
>> ping harper.uchicago.edu
>ping: unknown host harper.uchicago.edu
>
>> ping 128.135.12.7 [harper's IP address]
>PING 128.135.12.7 (128.135.12.7): 56 data bytes
>ping: sendto: Network is unreachable
>ping: write 128.135.12.7 64 chars, ret = -1
>.............
>.............
>
>I tried
>> route add default gw 140.180.128.1 which gave
>SIOCADDRT: Network is unreachable
>
>and by the way
>> ifdown eth0
>cat: /var/run/dhclient.pid: No such file or directory
>Does that matter?
>
>There seemed to be some posts in the archives from people having similar
>problems with recent kernels, but no obvious resolution that I came
>accross. However I expect it's much more my fault than the kernel's.
>
>cheers,
>
>Dan
>
>
>----------------------------------
>Dan Davison
>davisonATuchicago.edu
>http://home.uchicago.edu/~davison/




Reply to: