I am attempting to get my Dell desktop connected to the internet running Vector Linux. It is connected via CAT-5 cable, but when I attempt to connect using Wicd Network Manager, I get "Connection Failed: Unable to Get IP Address."

I have also checked my Windows laptop ability to connect via CAT-5 and it works, so I know the problem is not the router or the cable.

In addition, the Kernel IP routing table does not show any entries aside from the loopback address.

ifconfig shows eth0 and lo, but eth0 shows no packets sent, received or dropped.

Sorry it took me so long to reply. I had to transfer the text files from VL to my Windows machine (which is connected to the internet) and I had to edit all the dead space out of the original files. Here is the output info you requested.

I feel I should also mention this is the SECOND Linux based OS I have tried running on this box. The previous was Ubuntu Server 11.10. I also had difficulty with that, which is part of the reason that I switched to Vector. I thought having a GUI would make troubleshooting the network a little easier. Shows what I know.

I wanted to say thanks again for the help, and sorry its taking me so long to reply to each of these posts. I'm not running Linux on my regular computer so I have to set it up and tear it down every time I use it until I figure things out.

This reminds me of a problem I used to have in a hotel. For some reason, I had to bring up eth0 without dhcp, wait a minute or so, then request an IP address. I wrote a little script that killed wicd, brought eth0 down, then back up, waited 90 seconds, then launched dhcpcd. It's a long shot, but who knows?

It must be related to your use of windows and linux on the same machine. I have loaded linux (only) (lilo boot loader) on hundreds of machines without experiencing any such problem so long as the hardware, including the wire, is ok. Just load VL, plug in wire, boot, and its connected. I also find that I don't miss windows.

It must be related to your use of windows and linux on the same machine. I have loaded linux (only) (lilo boot loader) on hundreds of machines without experiencing any such problem so long as the hardware, including the wire, is ok. Just load VL, plug in wire, boot, and its connected. I also find that I don't miss windows.

I'm not running Windows on the Linux Box. It is a dedicated tower - no VM at all.

It must be related to your use of windows and linux on the same machine. I have loaded linux (only) (lilo boot loader) on hundreds of machines without experiencing any such problem so long as the hardware, including the wire, is ok. Just load VL, plug in wire, boot, and its connected. I also find that I don't miss windows.

There's absolutely no way that a Windows installation would affect the NIC use on a Linux install. None.

Anoceskey, can you post the contents of your /etc/resolv.conf file please.

It must be related to your use of windows and linux on the same machine. I have loaded linux (only) (lilo boot loader) on hundreds of machines without experiencing any such problem so long as the hardware, including the wire, is ok. Just load VL, plug in wire, boot, and its connected. I also find that I don't miss windows.

There's absolutely no way that a Windows installation would affect the NIC use on a Linux install. None.

Anoceskey, can you post the contents of your /etc/resolv.conf file please.

Not much to report sadly:

Code:

# Generated by dhcpcd# /etc/resolv.conf.head can replace this line# /etc/resolv.conf.tail can replace this line