Question about Dell Ethernet Card Network Adapter

1 Answer

Error:Starting Network 363: can't open/etc/dhcpc/

Hi Guys,

I am trying to boot from the network but it give this error Starting Network 363: can't open/etc/dhcpc/ after completing all the DHCP process. It seems to be Network card error to me. I am using Dell Optiplex 760.

looking for some help and tips of how to fix it.


Posted by on


1 Answer

  • Level 2:

    An expert who has achieved level 2 by getting 100 points


    An expert that got 5 achievements.


    An expert who has written 3 tips or uploaded 2 video tips.


    An expert whose answer got voted for 20 times.

  • Expert
  • 167 Answers

Have you tried to reload the software for the Network Adapter? If not! Have it first.

Posted on Mar 09, 2009


1 Suggested Answer

  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi there,
Save hours of searching online or wasting money on unnecessary repairs by talking to a 6YA Expert who can help you resolve this issue over the phone in a minute or two.

Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.

Here's a link to this great service

Good luck!

Posted on Jan 02, 2017


Add Your Answer

Uploading: 0%


Complete. Click "Add" to insert your video. Add



Related Questions:

2 Answers

Hi there, I recently bought new Acer Aspire 5553 laptop and was setting up partition hard drive when it asked me to restart to save changes. When restarted following continuous error was displayed on...

Go to the BIOS setup screen. Watch the info at boot time and hit the right key (F1, space bar, delete key, etc. depending)

In the BIOS, look in the boot options and take the "other devices" or "other" out of the boot sequence. Also check to see if boot from LAN is enabled. If it is, disable it. PXE is a protocol that will enable you to boot from a network drive or server. When it says that it failed, it is because it could not find an OS on the network.

If this answers your question, I'd appreciate 4 thumbs. I do this for fun and do not get paid.

Oct 02, 2010 | Computers & Internet

1 Answer

My Hp probook 4510s cannot boot it gives error of PXE failure after startup screen it says media cable check error.

Your computer tries to "boot" from several devices:

* floppy disk
* CD/DVD drive
* internal disk-drive
* USB memory-stick
* over the network, if it can find a "boot-server" on the local network.

So, the 'PXE failure' and 'check cable' errors occur either because there is no cable connected to the network-port, or because there is no "boot-server" on your network.

Enter BIOS setup, and check the "order" of possible boot-devices,
to ensure that the "network-boot" device is set to the _lowest_ priority.

What this could mean is that the computer *TRIED* to boot from the disk-drive, but *FAILED* to do so, i.e., you have a problem with the disk-drive in your computer. Ouch!

Aug 28, 2010 | HP 4510S C2D226 156 4GB 320GB DVDR BT CAM...

1 Answer

What is this error mean that i get during boot up? 312.198 Eth0:(185488) System Error Occurred (0) 312.199 Eth0:(185489) System Error Occurred (0) 312.200 Eth0:(185490) System Error Occurred...


I think this is related to to the NIC (Ethernet port).

Go into the BIOS and set it to default settings, see if that resolves the problem.

Let me know how you get on.


Jun 30, 2010 | MSI P4MAM2-V Motherboard

2 Answers

My laptop won't boot! What should I do?

No power? Blue Screen Of Death? Blinking cursor? Black screen?
Need more info.
For anything other than a BSOD or error message:
Try unplugging from power, remove the battery, hold the power button 30 seconds. Then reinstall battery, plug in, and turn on.
If you are getting something like 'NTLDR not found' or 'Boot Sector not found', Hard disk blah blah blah etc. you might need a new hard drive or to repair errors on your existing one.
For BSOD, try starting in safe mode. If that fails, try using a bootable antivirus disk to remove any viruses or other junk and reboot.
Reply back with more info or results!

Apr 24, 2010 | Compaq Presario 700 470024-192 Notebook

1 Answer

How to connect to internet to Linux 5 server enterprise edition in my dual boot desktop

type in these commands I assume you are using a Debian flavor
sudo nano /etc/network/interfaces auto eth0 iface eth0 inet dhcp (this is for DHCP, skip to CTRL commands below if DHCP) iface eth0 inet static (this is for a static IP) address x.x.x.x netmask x.x.x.x gateway x.x.x.x
sudo nano /etc/resolv.conf nameserver x.x.x.x (DNS here) nameserver x.x.x.x CTRL-O CTRL-X
sudo /etc/init.d/networking restart

Dec 18, 2009 | Computers & Internet

1 Answer

Not able to use internet in Red Hat Linux (RHEL 5)

- What make/model of NIC?

- Cable or DSL Internet access?

- Is there a router in the picture, or does the computer connect directly to your cable/dsl modem?

- Are you using DHCP or static IP assignment?

If you're using static IP addressing, check out some of the suggestions in this article:

Created: 9/05/02 Revised: 4/6/04

Basic PCI Network Interface Card (NIC) Configuration and Troubleshooting:

As different distros use different GUI (graphical) network configuration programs, the following instructions are
command-line based, and as such should work for most distros. If you boot directly into the GUI (KDE, Gnome, etc.)
as opposed to booting into a non-graphical runlevel, open a terminal window and type the given commands from there.
Much of the following can only be done as root, so either log in as root, or "su" to root if logged in as a non-root user.

*Note: some commands can only be run from root's login shell. When the su command is used by itself, it allows a non-root
user to become root, but only from within the user's own login shell. To gain a full root login shell without having to log out
and log back in as root, use the "-" option when issuing the su command: su - .

If you have only 1 NIC installed, it will be designated "eth0"; additional NICs will be designated eth1, eth2, etc.

Before doing any of the following, *please* check the Hardware Compatibility List at your distro's support site.
If your particular make/model of NIC is not listed as being compatible with your distro, there is good chance that
it may not work at all, or that you may have to take extra steps (such as downloading a special driver/module) in
order to get it working. Considering the fact that NICs are fairly inexpensive, it is often just not worth spending
time and energy trying to "force" an unsupported card to work.

1. If, on bootup, you see a message similar to "Bringing up interface eth0: FAILED", it is very possible that you have
a resource (IRQ or I/O address) conflict. Turn off Plug-N-Play support in your BIOS before proceeding further; BIOS PNP
can often cause problems with PCI devices under a non-Windows OS. If you dual-boot Windows and Linux, don't worry- your
PCI devices should still work in Windows with BIOS PNP disabled, as the PNP functionality of the Windows OS itself will
perform the necessary resource allocation.

*Note: If you are connecting to a network or ISP via DHCP, and you see a message on bootup similar to "Determining IP
information for device eth0: FAILED", that can indicate a problem with your DHCP configuration (or the DHCP server)
This article doesn't deal with DHCP issues, but I hope to be able to post one that does in the future.

2. Use one of the following commands to verify that your card is at least basically identifying itself to the system:

lspci -vv |less
less /proc/pci
cat /proc/pci

In the resulting output, look for the "Ethernet Controller" entry. It should contain information about your model of card
and/or its chipset, as well as IRQ, I/O port, and memory address values.

3. Run the ifconfig command; information concerning your NIC should appear in the resulting output. You should also
see stats for the loopback (lo) device If you've already tried to enter your IP info (inet addr, Bcast, Mask)
through a GUI network configuration utility, verify that those values are correctly reflected in ifconfig's output. Also
check for RX/TX errors and collisions. If eth0 is not listed when you run ifconfig, try "ifconfig -a"; the "-a" option forces
ifconfig to report all network interfaces, active or not. If eth0 appears only when you run ifconfig with the -a option, it is
definitely not correctly configured.

4. Verify that the correct module is being loaded for your ethernet card by issuing the "lsmod" command; you should see the module
name in the resulting list of loaded modules. If not, issue the following two commands and try again:

depmod -ae
modprobe <name of your NIC's module>

*Note- documentation concerning module loading will often refer to the "insmod" command, but use modprobe instead if it's available.
Basically, insmod is not as "intelligent" as modprobe in the fact that it doesn't try to resolve module dependencies (where the
successful loading of a given module "depends" on another module being loaded first).

If the module appears as loaded after that, check your /etc/modules.conf (/etc/conf.modules in some distros)file to make sure that it has
an entry for the module; this will load the module automagically each time you boot. The line will look like this:

alias eth0 <name of your NIC's module>

If the line doesn't exist, add it by editing the file with your favorite text editor.

5. Run the following two commands:

less /proc/interrupts
less /proc/ioports

For the first command, note the IRQ assigned to eth0; verify that it matches the Interrupt value listed when you ran the ifconfig
command, and note if the assigned interrupt is being shared with another device. If so, this doesn't necessarily indicate a problem,
but it can.
For the second command, make sure that the address range of your Ethernet controller doesn't conflict with/overlap that of another
device. Also make sure that the start of the address range corresponds to the Base address value shown for eth0 when you ran ifconfig.

6. If any of the above steps yield errors or indicate conflicts even after you've turned off PNP support in the BIOS, try physically
rearranging the slot order of your PCI cards; doing so can force a reallocation of resources to devices on the PCI bus.

7. Once you're sure that the NIC is correctly configured and the module is properly loaded, you can try to bring the card up with
the following command:

ifconfig eth0 <the NIC's IP address> netmask <the appropriate netmask> up

If you get no errors, you should at least then be able to ping the IP address of the NIC.


Distro-specific configuration files:


Redhat, Mandrake, and a few other distros use the following two basic network interface configuration files:


The format of the files may vary slightly across distros/versions, but the the pertinent contents of the files should be very similar to:


DOMAINNAME="your_domain_name" ("localhost" is valid here)
GATEWAY="IP_address_of_your_gateway_machine/device" (if applicable)




An explanation of IP addressing as a whole (including terms such as "netmask", "network address", "broadcast address",etc.) is well beyond
the scope of this Help File. However, the following sites provide some good background information:


- Further resources, including NIC driver source code and diagnostic utilities can be found at
* Note that as of 3/04 the Scyld site appears to have undergone changes; some links on the above page are broken.


#include <disclaimer.h>

This is, as a whole, a work in progress. It might (and probably does) contain omissions and/or slight inaccuracies.
However, none of the suggestions given here will do any harm to your system if performed correctly.

Being a work in progress, any suggestions/corrections/critcisms are more than welcome. If you've noticed any errors in the above,
or just have something constructive to suggest, feel free to email me:

Jul 02, 2009 | Red Hat Enterprise Linux ES Basic Edition

1 Answer

Wirless driver for linux

hi linksys doenot have the wireless drivers for linux but you can try the following steps:
-download the windows drivers. Extract them to c:\temp\linksys
- Now burn them or put them on a media or somthing so you can transfer these files over to linux (note: linux wont beable to extract the exe file)
- Download ndiswrapper for linux located at
- Now make sure you have all the development tools installed in fedora
- Now download dhcpcd from
- log into your linux box as root
- Now make make sure all the files (*gz files, and linksys driver files) are in the root partition on the linux machine (/root/wireless_driver) if "wireless_driver" is not there make the directory (which u will have to do) "mkdir /root/wireless_driver"
- now at the command prompt (terminal) go into the "wireless_driver" directory "cd /root/wireless_driver"
- now type "tar xvfpz ndiswrapper-0.12.tar.gz"
- "cd ndiswrapper-0.12"
- "make install"
- "cd .."
- "tar xvfpz dhcpcd-1.3.22-pl4.tar.gz"
- "cd dhcpcd-1.3.22"
- "./configure"
- "make && make install"
- "cd .."
- "source /etc/profile" (note: you might want to edit root's .bashrc and add source /etc/profile there, some how fc3 doesnt have root source /etc/profile for some reason)
- "cd /root/wireless_driver/WMP54GS_20040423/Drivers"
- "ndiswrapper -i BCMWL5.inf"
- "ls /etc/ndiswrapper/bcmwl5" u should get a list of alot file in here
- "modprobe ndiswrapper"
- "dmesg wlan0" show see wlan0 if its there your good if not then somthings wrong - please post everything thats comes out of dmesg "dmesg > demout"
- now for a little script open your favorite text editor and copy the following code:
#Sample ndiswrapper script - By: Derrick Rose
#Load ndiswrapper module
echo "Starting Ndiswrapper Driver..."
/sbin/modprobe ndiswrapper
#Setup Essid
echo "Setting up ESSID..."
iwconfig wlan0 essid "your essid here"
#Setup WEP Key if you have one
#Uncomment below for WEP
#echo "Setting up KEY..."
#iwconfig wlan0 key yourkeyhere
#Setting up DHCP on wlan0
echo "Starting DHCP on wlan0 [ 10 sec timeout ]"
dhcpcd -t 10 wlan0

- the script above will setup your wireless card for. Now save this to a file in roots directory (/root) called wireless
- "chmod +x wireless"
- to run manually type "./wireless" as root
- If you want to automaticly load on startup do the following
- "cat wireless >> /etc/rc.d/rc.local"
restart the computer..adn then check


Jan 08, 2009 | Linksys (WMP54GS) 802.11g/b Wireless...

3 Answers

About linux

what type of linux are you using? is it kubuntu, edubuntu, or ubuntu?

Jun 04, 2008 | Computers & Internet

1 Answer

2 Eth Cards one for Internet & one for LAN

First of all, I would really recommend you to buy a Cable/DSL router. It is quite cheap, usualy more secure, much easier to configure and troubleshoot. Also, it does not require to have one PC up and running all the time, hense saving energy. Do you know that a PC running 24/7 may cost between 60$ and 100$ in electricity annually? This is more than the cost of a basic router!

But, since your question is about sharing your Internet connection with a PC, here are some guidelines. I will assume here that you are using Windows XP.

On PC1:
1. Connect the modem to Eth0 in the PC. Do not connect anything in the USB port of the modem.
2. Make sure that the link lights are lit both side. If they are not, you may need a cross-over cable (this is usualy not the case)
3. Configure Eth0 to get IP address DNS automatically
4. Disable (uncheck) all protocols except TCP/IP on Eth0.
5. Run the Network Setup Wizard (Start > All Programs > Accessories > Communications > Network Setup Wizard) and follow the steps.

On PC2:
Simply run the Network Setup Wizard (Start > All Programs > Accessories > Communications > Network Setup Wizard) and follow the steps. Specify and you Internet connection is through a Home or LAN network.

That should do it.

Apr 25, 2008 | Computers & Internet

1 Answer

Error Message on boot

IBM requires using a "branded" network adapter, meaning one that has IBM's name on it, no matter if it's broadcom,etc. There is a couple of workarounds for this problem which would enable you to use whatever wireless adapter you wish. I would google IBM R40, and error 1802 and you'll find the application you need. Unfortunately, I'm not able to offer it to you here.
Good luck

Dec 02, 2007 | IBM ThinkPad R40 2897 Notebook

Not finding what you are looking for?
Dell Ethernet Card Network Adapter Logo

Related Topics:

172 people viewed this question

Ask a Question

Usually answered in minutes!

Top Dell Computers & Internet Experts

Les Dickinson
Les Dickinson

Level 3 Expert

18424 Answers

Alun Cox

Level 3 Expert

2678 Answers

Doctor PC
Doctor PC

Level 3 Expert

7733 Answers

Are you a Dell Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides