I just installed Mandrake 9.1. I have RoadRunner service in Western Ohio, and on my Windoze boot I just use DHCP to boot up and I'm live.

Mandrake comes with this nifty little wizard that's supposed to autodetect everything, but when I try to connect to the 'Net it just says the connection failed. When Mandrake is booting up I even see the line that says eth0 is getting an IP address from DHCP, and it gets an address that looks similar to addresses I've been assigned by RoadRunner before, so Mandrake is definitely DHCP-aware.

Please help! Bear in mind, I am a complete newbie to the Linux world. If you're going to tell me to do anything complex, please tell me _exactly_ what I need to do. I'm not a newbie to networking or software and can follow instructions, but any Linux lingo is likely to lose me unless it's explained.

Perhaps this might help

http://www.linuxquestions.org/questi...threadid=87731

Well, I tried it, but still have the same problem. I ran the DrakConnect wizard, deselected "LAN," selected "Cable," and so on like the post in the link says. It still says it's getting an IP address on bootup, but I still can't connect.

bring up a console window and su to root, do ifconfig, it will tell you if you have an address, if you get a responce with something like eth0.9 then you didn't get a ip address from dhcp.

you can try to reset your interface with "ifdown eth0" and "ifup eth0"

and check it again. you can also check this link .

Hope this helped.

I tried that, no luck.

A little background: I have two NICs, one eth0 that is connected to my cable modem, the other that runs to a hub to connect to my other computer. It all works fine under Win2K. When I ran the MCC wizard I told it to put DHCP on eth0 and a static IP address on eth1.

When I type ifconfig, it shows an "eth0" that says UP, RUNNING and so on, but no IP address.

It also shows an "eth0:9" (not "eth0.9" but is this what you meant?) with UP, RUNNING and so on, and an IP address of 169.254.215.253.

ok, the eth0:9 with address 169.254.215.253 indicates that it did not get an IP from hdcp. I have found a couple of threads that might help you.

1st

2nd one but I don't think there is a solution on this one.

3rd don't know may be the issue.

hope these help

Well, I tried setting a static IP equal to the one my DHCP has been assigning me for months now. It boots a lot faster. It used to hang for a long while while trying to bring up interface eth0, but now zips right through it. Unfortunately I still can't connect to the Internet. Just to make sure, I rebooted and tried again, then I rebooted yet again into Windows to make sure that I still have the IP address that I set statically, and I do.

I went into BIOS to check out the plug-and-pray stuff. My BIOS setup just lets me pick, on an interrupt-by-interrupt basis, whether each interrupt is controlled by "PNP/PCI" or "ISA Legacy." I set all of them to ISA Legacy, and this made absolutely no difference when I booted to Linux. It did make for some really cool video effects when I then booted to Windows, so I set it back the way it was before.

have you tried removing one of the NIC's? I had some problems a while back while setting up a router box (which sounds like what you're doing) with remembering which card was which. Open up the box and remove the one that you want connected to your hub. Try to get it to work with just the one in there (it'll pop up a screen asking if you meant to remove the other card and say yes). After you get that one working, pop the card back in (it will pop up a screen asking if you want to configure the new card, but should autoconfig correctly) and work on getting the network up. Hopefully this will work for you.

Oh, and the reason why the static IP is faster than the DHCP on boot is that the DHCP client has to time out before it continues because it can't get an IP addy from where it's expecting one. The static IP just assumes it's correct.

Okay, removed the extra NIC. Booted. Ran MCC and ran the wizard. Set up eth0 for dhcp assignment of IP. Rebooted. Still doesn't get an IP address from dhcp.

I'm out of ideas.

Have you tried:

tail -f /var/log/messages

This will should you the errors that dhcpd is receiving and it might be helpful to look at the whole /var/log/messages file.

Cheers.

It says (in part):

localhost ifup: Determining IP information for eth0...
localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
localhost dhclient: No DHCPOFFERS received.
localhost zcip[5090]: interface: eth0 (00:04:5A:77:0C:29)

Try this:

Put the hostname that your isp gave you in the ifcfg-eth0 file

# cd /etc/sysconfig/network-scripts
# vi ifcfg-eth0
DHCP_HOSTNAME=HOSTNAMETHEYGAVEYOU

You may also need to add it here:

# cd /etc/sysconfig
# vi network
HOSTNAME=HOSTNAMETHEYGAVEYOU
GATEWAYDEV=eth0

These are older instructions I found but I think I had to do this with my Comcast cable system when I was on holiday.

Cheers.

What host name do you mean? If I boot in Win2K where would I find it?

This is mostly unrelated to DHCP, but here's one simple test that I know of. First, try this from a terminal window:

ping www.yahoo.com

If it says something about being unable to lookup www.yahoo.com's IP address, then possibly your nameserver isn't set up correctly. Try:

ping 65.24.0.168

If it gets successful responses, then you're actually connected, but your box doesn't know how to reach the nameserver. (Hit control-C to stop the pinging). If that's the case, add the following lines to your /etc/resolv.conf file:

nameserver 65.24.0.168
nameserver 65.24.0.169
search woh.rr.com

(I had Roadrunner in Western Ohio until about a month ago, and those were the nameservers I used)

If pinging gives other errors about the network being unreachable, then I'm not too sure what to tell ya... it might have something to do with setting up a gateway.

If you're getting DHCP errors, perhaps Roadrunner's DHCP servers aren't set up correctly. I don't know if I ever directly had that issue when I was using Roadrunner, but many times (maybe once a week or so), my cable modem would spontaneously lose its internet connection, and I had to restart network services to get it to come back. Also, just before I moved out of Ohio, they were having frequent service problems. Every few days or so, our cable service would go out for several hours. Calls to customer service were usually met with "We are currently experiencing service outages in all these areas. Sorry about the inconvenience."

You should call Time Warner and complain that they didn't help you set up your internet connection They will probably tell you that they don't support Linux, but at least you'll be letting them know that there's a demand for it.

It would have been given to you by the person who installed your system. Did they install any software when you were initially setup?

Cheers.