I don't believe it is a wiring issue as the machine I am testing is my normal desktop which seems to be working fine when I reboot into Windows XP (but anything is possible).
The DHCP server is Windows 2003 Server. Looking at the relatively uninformative logs located in C:\WINDOWS\SYSTEM32\DHCP, I don't see anything that jumps out at me. I can move the machine to a different network to try against the dnsmasq install I have running on my Sheevaplug (running Debian Squeeze), but currently that is configured in Proxy mode as the Cisco router on that segment is providing DHCP. Should I just setup a completely generic standalone environment to remove all other variables? The card is a Intel 82566DM-2 Gigabit NIC identified with vendor ID 8086 and device ID 10bd This machine does boot properly via DHCP with XP and has access to my local network resources. Please don't apologize for asking me to try the simple things. I make mistakes more often than I would like, and the help everyone is offering is most appreciated. Again, thanks for your time. Bob On Tue, Jan 26, 2010 at 3:17 PM, Marty Connor <[email protected]> wrote: > It is acting as if it didn't get a response from your DHCP server. > > It could be a driver issue, but it could also just be a > server/wiring/switch issue. > > A few questions: > > What kind of DHCP server do you have? Does it have a log (like > /var/log/messages) that you can look at to see if the MAC address of > your machine is asking for an address? > > What are the PCI IDs of your card? (if you don't know how to find them, > we can help you) > > Does this exact machine boot with network access in other OSes? > > Sorry for the basic debugging questions, but this could be a bad cable > or server misconfiguration. > > / Marty / > > On 1/26/10 7:05 PM, Robert Boerner wrote: >> Using the boot floppy referenced below, gPXE (although this version >> identifies itself as 0.9.9+ and not the rc1) seems to detect the NIC. >> Running an ifstat at the command prompt seems to confirm this, but >> running a dhcp net0 results in an error: >> >> gPXE> dhcp net0 >> DHCP (net0 00:1e:4f:d3:28:a1)................Connection timed out >> (0x4c106035) >> Could not configure net0: Connection timed out (0x4c106035) >> >> Anything else I should/could try? Will trying the *.iso make any >> difference? It's easy to reuse the floppies as I am running out of >> CD-Rs :-) >> >> Thanks again for the help. >> >> Bob >> >> On Tue, Jan 26, 2010 at 2:43 PM, Marty Connor <[email protected]> wrote: >>> Bob, >>> >>> You can try a test version of the new e1000e driver here: >>> >>> http://etherboot.org/share/mdc/e1000e-only.dsk >>> >>> or here: >>> >>> http://etherboot.org/share/mdc/e1000e-only.iso >>> >>> Please let us know how things go. >>> >>> / Marty / >>> >>> On 1/26/10 6:42 PM, Robert Boerner wrote: >>>> Thanks for the update. I guess I'll just wait since I have no ability >>>> to write code :-) I just finished watching the videos of Marty Connor >>>> giving talks that are on the gPXE website. Very helpful and >>>> informative. >>>> >>>> Thanks again everyone for your help, >>>> >>>> Bob >>>> >>>> On Tue, Jan 26, 2010 at 2:27 PM, Joshua Oreman <[email protected]> wrote: >>>>> On Tue, Jan 26, 2010 at 6:23 PM, Robert Boerner >>>>> <[email protected]> wrote: >>>>>> Hi Neil, >>>>>> >>>>>> That was fast :-) >>>>>> >>>>>> I am not receiving any error. It just seems as if no NIC is detected. >>>>>> Am I correct in assuming that when booting it should identify the NIC >>>>>> in the boot messages, and that when accessing the gPXE command line >>>>>> issuing an iftstat command should list all found interfaces? During >>>>>> the boot it simply states No more network devices. I tried ifstat and >>>>>> nothing was returned, and then tried an ifstat net0 (I believe the >>>>>> syntax was correct) and I get net0: no such interface. >>>>> >>>>> I believe that PCI ID corresponds to a NIC implemented by the Intel >>>>> e1000e driver, which has not yet been ported to gPXE. Our project >>>>> leader, Marty Connor, is working on it. >>>>> >>>>> -- Josh >>>>> >>>> _______________________________________________ >>>> gPXE mailing list >>>> [email protected] >>>> http://etherboot.org/mailman/listinfo/gpxe >>> >>> > > _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
