I'm on a similar campus, but DHCP works fine for me :-D
But that doesn't help you out ; )
I suggest taking the things your Help Desk people told you about (subnet
mask, IP address, etc.) and hard-coding them rather than trying to get
DHCP to automatically configure your settings for you. Offhand I'm not
sure what graphical utility does this, but I'm sure it's either the main
"Control Center" or something similar. All you have to do is click on
your ethernet card and then manually set these values. This *should*
work.
Good luck
Sincerely,
Eric
________________________________________________________________
Eric Krout
Email: [EMAIL PROTECTED]
Web: http://www.eg.bucknell.edu/~ekrout (Soon, EricKrout.com)
Bucknell Computer Science & Engineering '03
Chairman, Bucknell's Assoc. for Computing Machinery (ACM)
On Fri, 27 Apr 2001, Aleksey Naumov wrote:
> Hi, Mandrake experts!
>
> I've just installed Mandrake 8.0 on my PII 400MHz HP at work. My
> computer is on a
> college network and connection is done with DHCP. The problem is that I
> can't get
> DHCP connection to work in Linux, while it works just fine in Win98.
>
> At boot time I get:
>
> Setting network parameters: [ OK ]
> Bringing up interface lo: [ OK ]
> Bringing up interface eth0: Determining IP information for eth0...
> failed.
> [FAILED]
>
> I've tried to play with dhcpcd parameters, but with no result:
>
> > dhcpcd -v
> DHCP Client Daemon v.1.3.19-pl4
>
> > dhcpcd
> > dhcpcd -r
> as well as playing woth the -h (host) option:
> > dhcpcd -h foohost
> > dhcpcd -h <machine_name> # name my machine is known as under Win
> > dhcpcd -h <machine_name.<domainname>
>
> I get the same message (in log):
>
> Apr 27 19:41:41 HAP429 dhcpcd[1355]: broadcasting DHCP_DISCOVER
> Apr 27 19:42:41 HAP429 dhcpcd[1355]: timed out waiting for a valid DHCP
> server response
>
>
> I also tried to use the pump daemon instead of dhcpcd:
>
> > pump
> Operation failed.
> > pump --win-client-ident
> Operation failed.
>
> as well as all -h options, but with the same result.
>
> At least pump daemon logs more info, but I don't know if it's useful.
> Does anyone?
> Here it is:
>
> Apr 27 19:37:23 HAP429 pumpd[1348]: PUMP: sending discover
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: opcode: 1
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: hw: 1
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: hwlength: 6
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: hopcount: 0
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: xid: 0xf5fba69c
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: secs: 0
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: flags: 0x0000
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: ciaddr: 0.0.0.0
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: yiaddr: 0.0.0.0
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: server_ip: 0.0.0.0
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: bootp_gw_ip: 0.0.0.0
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: hwaddr:
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: servername:
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: bootfile:
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: vendor: 0x63 0x53 0x82 0x63
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: vendor: 53 1 0x01
> Apr 27 19:37:23 HAP429 pumpd[1348]: breq: vendor: 0xff
> Apr 27 19:37:23 HAP429 kernel: eth0: using NWAY device table, not 8
>
>
> People in tech support were not very helpful (it's a Windows only
> campus). They
> gave me IP addresses for subnet, gateway and DHCP server, but what do I
> do with them?
> The DHCP server is probably run on NT.
>
>
> I've read the DHCP mini-howto, as well as other network howtos and I
> can't get
> this moving. I also went through network setup in Mandrake control
> center (as well as
> linuxconf), the Mandrake control center uses wizard and determines
> correctly that
> I am on a LAN and using DHCP, then reports that the network is set...
> and it isn't!
>
> Any ideas would be very much appreciated!
>
> Aleksey
>
>
> P.S.
>
> Could this be a problem with my Ethernet card rather than DHCP? It
> doesn't look
> like it to me (especially since it works perfectly under Win98), but
> just in case,
> here the info on my Ethernet card:
>
> ---------
> I have a 3Com 3c905B-Combo [Deluxe EtherLink XL 10/100] card. Of the 3
> connectors
> the one that's is used is 10Base2 (thinnet with metal
> push-and-turn-to-lock).
>
> The driver used is 3c59x that came with the system. I tried to compile
> the newer
> 3c90x, but couldn't get it to compile. However, this is likely not a
> problem, since
> the "Ethernet-HOWTO" says that my card (3c905B) is supported by this
> driver (3c59x).
>
> I don't know how to check if the card itself works, but the following
> messages
> (from dmesg) make me think it's ok:
>
> > dmesg
> ...
> 3c59x.c:LK1.1.13 27 Jan 2001 Donald Becker and others.
> http://www.scyld.com/network/vortex.html
> See Documentation/networking/vortex.txt
> eth0: 3Com PCI 3c905B Cyclone 10/100/BNC at 0x1400, 00:50:04:0a:fb:13,
> IRQ 11
> product code 5545 rev 00.0 date 01-21-99
> 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
> MII transceiver found at address 24, status 782d.
> Enabling bus-master transmits and whole-frame receives.
> eth0: scatter/gather enabled. h/w checksums enabled
> eth0: using NWAY device table, not 8
>
>
>
