Re: Cannot connect to network now...

From: Maurits van Rees (maurits_at_vanrees.org)
Date: 11/22/04

  • Next message: Sergio Basurto Juarez: "RE: Cannot connect to network now..." 
    Date: Mon, 22 Nov 2004 21:19:43 +0100
To: debian-user@lists.debian.org

    On Mon, Nov 22, 2004 at 07:13:59PM -0000, Brian Coiley wrote:
    > "Brian Coiley" <bcap@clara.co.uk> wrote in message
    > news:33rql-1rI-19@gated-at.bofh.it...
    > > 9. After much fiddling around with configuration, managed to get startx
    > > to do something using VESA, but just shows a grey screen with a black
    > cross
    > > in the middle, and entire system is locked up.

    Is it really locked up? Try CTRL-ALT-F1 to go to the first text
    console. (CTRL-ALT-F7 to go back usually.) Or right click with your
    mouse to see if a context menu comes up. I may be wildly off with my
    guess here, but it reminds me of a simple window manager. If that's
    the case you may want to install kde or gnome to get some more
    extensive graphics.

    I got a rather empty screen like yours once when I somehow failed to
    notice that I had uninstalled kde... ;-)

    > OK, here's some more info: considerable rummaging around revealed the
    > command "dhclient". Executing this resulted in the somewhat discouraging
    > message "Unrecognized Kernel Version" or something like that. More
    > rummaging around revealed that dhclient is in fact a script, wrapping 2.0
    > and 2.2 versions of the dhclient thingy. No sign of a 2.6 version! Anyway,
    > I ran the 2.2 version and guess what? I immediately got a DHCP lease and
    > started nattering to the network!

    2.0 and 2.2 should be the version numbers of dhclient and have nothing
    to do with a kernel version. The error message seems strange. Googling
    may possibly give some hints. BTW, on the Debian servers I only see
    version 2.0. What does the following command show?

    dpkg-query -l dhc* | grep ii

    In my case:
    ii dhcp-client 2.0pl5-19.1 DHCP Client

    > So what's gone wrong? Presumably the 2.6 kernel broke something re DHCP,
    > but what, and how do I fix it (other than by doing the above whenever I
    > boot)?

    I also don't always get a dhcp lease when I boot up. I just have one
    computer connected to a DSL router. The router needs some time to
    start up. The computer is faster and starts to request a dhcp lease
    before the router is fully up and running, so it doesn't work. When
    that's the case I have to run the dhclient command manually as
    well. Could this be your problem? 

    -- 
Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands]
"Let your advance worrying become advance thinking and planning."
 - Winston Churchill
-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Sergio Basurto Juarez: "RE: Cannot connect to network now..."

    Relevant Pages

    • Re: Cannot connect to network now...
      ... > I also don't always get a dhcp lease when I boot up. ... > computer connected to a DSL router. ... The computer is faster and starts to request a dhcp lease ... Windoze clients connecting with no problem for many, ...
      (Debian-User)
    • Re: Wireless router losing Internet connection (DHCP problem)
      ... problem with DHCP lease renewal. ... has fixed the problem and where/who did you get the new firmware from. ... I either need to fix this router or send it back and get something else. ... again when the DHCP lease runs out again -- the wireless router is ...
      (alt.internet.wireless)
    • Re: Wireless router losing Internet connection (DHCP problem)
      ... hours with new firmware for the router. ... *doesn't* solve the ongoing problem of DHCP lease renewal, ... Installed a wireless router on Comcast Cable Internet service ... I reconnected the original PC to the cable modem ...
      (alt.internet.wireless)
    • Re: POSIX error: Permission denied (NSPOSIXErrorDomain:13)
      ... router, and give my computer a static ip adress (configuring IPv4 ... demand a new DHCP Lease, I always get the very same ip address I ... Likely a firewall issue - are you running NetBarrier or some other ... you can look them up (use the network utility on your Mac in the ...
      (comp.sys.mac.system)
    • Re: wpi doesnt associate :(
      ... I tested the new tarball on my laptop but dhclient still refuses to associate (it keeps ... Laptop: Asus A6JE. ... ifconfig shows that the driver finds the router. ...
      (freebsd-current)