I am new to linux and just installed Kubuntu. I have windows XP on my master primary hard drive
and Kubuntu is installed on my slave drive. Everything seems to work great except that I cannot
connect to the internet when I boot into Kubuntu (I also tried Ubuntu). I am thinking maybe it has
something to do with ethernet adapter driver. I can connect just fine in windows, so I know that
the actual hardware isn't messed up. Windows uses the driver for Realtek RTL8139/810x Family
Ethernet NIC. I looked through google and help forum threads and it seems others have had this
problem with similar adapters and many of them never came to a resolution and others got it
working and were not quite sure what got it working. Kubuntu is supposed to install the hardware
automatically and I really don't know how to install linux drivers. Does this sound like a driver issue?
I would really like to get this resolved, because I really can't enjoy an OS without an internet connection.

When I open the web browser and attempt a google search I get something like this:
"An error occurred while loading http://www.google.com/search?q=linux&i...8&oe=UTF-8:
Unknown host www.google.com"


I tried reinstalling kubuntu to see if that helped and then after booting back into linux
I checked the system log and these were the only entries:

02/07/2007 02:32:33 PM computername anacron[4478] Job `cron.daily' terminated

02/07/2007 02:32:33 PM computername syslogd 1.4.1#18ubuntu6 restart.


I tried opening network places and get this alert:
error - konqueror
The Zeroconf daemon (mdnsd) is not running


I followed some steps from different posts in other forums and I don't really know if they
apply to me or not but I will post the results I got to maybe assist in diagnosing the problem:

I guess this is my kernel version
uname -r
2.6.17-10-generic


contents of /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp


ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:4C:CD:D9:28
inet6 addr: fe80::2e0:4cff:fecd:d928/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5519 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:388500 (379.3 KiB) TX bytes:6282 (6.1 KiB)
Interrupt:209 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:112 errors:0 dropped:0 overruns:0 frame:0
TX packets:112 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8592 (8.3 KiB) TX bytes:8592 (8.3 KiB)


sudo ifdown eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 4778
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:e0:4c:cd:d9:28
Sending on LPF/eth0/00:e0:4c:cd:d9:28
Sending on Socket/fallback



sudo ifup eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:e0:4c:cd:d9:28
Sending on LPF/eth0/00:e0:4c:cd:d9:28
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

If there is any other info that might help just ask (you might have to tell me how to get the information).
Does anyone have any suggestions? Any help would be very appreciated.

This post has been edited by foolakadugie: Feb 8 2007, 08:25 AM

Hi,



This means the eth0 couldnt get any ip address.
Do you have a DHCP server on the LAN ?

or you can do one thing.. have a static IP for the eth0 (assuming eth0 is the network card hooked on to your LAN). Open '/etc/network/interfaces'

and have something like this...

======
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# The first network card - this entry was created during the Debian installation
# (network, broadcast and gateway are optional)

auto eth0
iface eth0 inet static
address 192.168.0.50
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.10
======

Remove all the other interfaces ie. eth1, eth2... till wlan0..
Now check...

Cheers

Well in windows under LAN properties it gives me an IP for the DHCP Server.
Does this carry over to Linux? Oh and if it matters, I am not behind a router.

I will boot into linux and if I can do what you suggested.

My Windows installation on my desktop uses Realtek RTL8139/810x NIC and the drivers get installed smoothly. On My laptop i use Intel Integrated 10/100 NIC.

Normally I assign an IP address to the Desktop and when i connect my laptop that has OpenSuSE 10.2, it gets detected automatically and all i have to do is fire up the browser and start working.

Instead of connecting via LAN, u could also try connecting your linux machine individually to the internet.Try this link >>LINK<<. Being a newbie myself this is all i could help you out with. But personally i would suggest anyone new to start with opensuse, cause it was easy and user friendly for me when i started.

Regards
Dhanesh.

I am now connected to the internet in kubuntu. I would like to thank both of you for your help. It seems kubuntu has a weird bug in recognizing an internet connection. It will tell you that it is enabled when it is not. I unplugged the ethernet cable, rebooted, disabled the eth0, plugged the ethernet cable back in, then re-enabled eth0,

Your eth0 couldn't connect.Srry I didn't read all of it.

hi,

that was not a bug. in reality, all system that are linux based requires you to setup the eth0 IP since it was the primary network connection. that autodetection was just an added feature.. =)

What saneax has said is the exact problem here. In case you find his instructions a little tough to follow, then try exploring the System menu in Kubuntu and goto Network Settings. You will find a tool that lists all the network interfaces including eth0. Select eth0 and then select properties and then make the configurations of IP, Subnet mask etc just same as in Windows. That will help.