Login or Register to Ask a Question and Join Our Community


Ubuntu

Ubuntu 10.10 LAN connection stopped working...

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Linux Ubuntu Ubuntu 10.10 LAN connection stopped working...
# 1  
Old 04-27-2011
Ubuntu 10.10 LAN connection stopped working...
Well this is weird. I restarted my dual boot Win7/Ubuntu 10.10 from ubuntu to windows. Everything was working fine and windows is always connecting properly to my lan. After restarting back into Ubuntu, all of a sudden I can't connect to my network. It looks as if its trying to connect through ipv6, which this network is not. I used someones advice on how to disable the ipv6 cause whenever I do ifconfig on my ubuntu it gives the following:

Quote:
eth0 Link encap:Ethernet HWaddr: f0: blah blah
inet6 addres: fe80: blah blah
Sorry I can't write the whole thing but but its too long to copy it over from that computer. You can see that it addresses ipv6 still. I even have it disabled in network preferences.

I don't know what is going on!

Any help would be appreciated.

Thanks
# 2  
Old 04-27-2011
That ipv6 stuff is always there, it doesn't mean its actually working.
This User Gave Thanks to Corona688 For This Post:
zixzix01
# 3  
Old 04-28-2011
Oh okay...

Any ideas on how to check where the problem is coming from. I mean Windows has no problem connecting on the same computer so i know it's not a hardware or cable issue. Ubuntu was working fine up until days ago. The only thing that could affect it was that I installed a fresh version of the system recently. However, it worked fine for days since the reinstall.

Thanks,
# 4  
Old 04-28-2011
Any suspicious entries in dmesg, /var/log/messages or /var/log/daemon.log?
This User Gave Thanks to Loic Domaigne For This Post:
zixzix01
# 5  
Old 05-02-2011
Daemon logs are a little strange. I was looking at them and the one that was zipped and rotated by the system has info about networking until April 24th. The next one that was rotated but not zipped yet has something saying:
Quote:
May 2 NetworkManager[1232]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) failed (no IP configuration found)
I don't really know how to identify problems that good as of yet in the logs so if you can tell me what to look for it would be beneficial.

Thanks
# 6  
Old 05-02-2011
Servus,

Please start the following command in a separate console:
Code:
$ sudo tail -f /var/log/daemon.log

Then activate the network interface.

Could you please paste the output seen in the console?

TIA, Loïc
# 7  
Old 05-02-2011
Sorry silly question,

How do I activate the network interface?

---------- Post updated at 04:30 PM ---------- Previous update was at 04:24 PM ----------

Sorry figured it out,

Apologies

One second to transfer log output...

---------- Post updated at 04:48 PM ---------- Previous update was at 04:30 PM ----------

Here it is. I had to stop the interface and then I restarted it:


Quote:
sudo tail -f /var/log/daemon.log
[sudo] password for izivanov:
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) complete.
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) failed (no IP configuration found)
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 7 -> 9 (reason 5)
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Marking connection 'root01.org' invalid.
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <warn> Activation (eth0) failed.
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 9 -> 3 (reason 0)
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> (eth0): deactivating device (reason: 0).
May 2 16:28:17 rti-is019-con dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 1676
May 2 16:28:17 rti-is019-con dhclient: killed old client process, removed PID file
May 2 16:28:17 rti-is019-con dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 2 16:28:17 rti-is019-con dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 2 16:28:17 rti-is019-con dhclient: All rights reserved.
May 2 16:28:17 rti-is019-con dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 2 16:28:17 rti-is019-con dhclient:
May 2 16:28:17 rti-is019-con dhclient: Listening on LPF/eth0/f0:4d:a2:db:e1:d2
May 2 16:28:17 rti-is019-con dhclient: Sending on LPF/eth0/f0:4d:a2:db:e1:d2
May 2 16:28:17 rti-is019-con dhclient: Sending on Socket/fallback
May 2 16:28:18 rti-is019-con dhclient: DHCPRELEASE on eth0 to 10.70.25.25 port 67
May 2 16:28:18 rti-is019-con dhclient: send_packet: Network is unreachable
May 2 16:28:18 rti-is019-con dhclient: send_packet: please consult README file regarding broadcast address.
May 2 16:28:18 rti-is019-con avahi-daemon[1136]: Interface eth0.IPv6 no longer relevant for mDNS.
May 2 16:28:18 rti-is019-con avahi-daemon[1136]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::f24d:a2ff:fedb:e1d2.
May 2 16:28:18 rti-is019-con avahi-daemon[1136]: Withdrawing address record for fe80::f24d:a2ff:fedb:e1d2 on eth0.
May 2 16:28:18 rti-is019-con NetworkManager[1237]: <info> (eth0): carrier now OFF (device state 3)
May 2 16:28:18 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 3 -> 2 (reason 40)
May 2 16:28:18 rti-is019-con NetworkManager[1237]: <info> (eth0): deactivating device (reason: 40).
May 2 16:28:29 rti-is019-con dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 2 16:28:29 rti-is019-con dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 2 16:28:29 rti-is019-con dhclient: All rights reserved.
May 2 16:28:29 rti-is019-con dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 2 16:28:29 rti-is019-con dhclient:
May 2 16:28:29 rti-is019-con dhclient: Listening on LPF/eth0/f0:4d:a2:db:e1:d2
May 2 16:28:29 rti-is019-con dhclient: Sending on LPF/eth0/f0:4d:a2:db:e1:d2
May 2 16:28:29 rti-is019-con dhclient: Sending on Socket/fallback
May 2 16:28:29 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
May 2 16:28:32 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
May 2 16:28:32 rti-is019-con NetworkManager[1237]: <info> (eth0): carrier now ON (device state 2)
May 2 16:28:32 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 2 -> 3 (reason 40)
May 2 16:28:34 rti-is019-con avahi-daemon[1136]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::f24d:a2ff:fedb:e1d2.
May 2 16:28:34 rti-is019-con avahi-daemon[1136]: New relevant interface eth0.IPv6 for mDNS.
May 2 16:28:34 rti-is019-con avahi-daemon[1136]: Registering new address record for fe80::f24d:a2ff:fedb:e1d2 on eth0.*.
May 2 16:28:39 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
May 2 16:28:48 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
May 2 16:28:57 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
May 2 16:29:07 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
May 2 16:29:21 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
May 2 16:29:21 rti-is019-con dhclient: DHCPOFFER of 10.70.29.178 from 10.70.31.252
May 2 16:29:21 rti-is019-con dhclient: DHCPREQUEST of 10.70.29.178 on eth0 to 255.255.255.255 port 67
May 2 16:29:21 rti-is019-con dhclient: DHCPACK of 10.70.29.178 from 10.70.31.252
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: New relevant interface eth0.IPv4 for mDNS.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Registering new address record for 10.70.29.178 on eth0.IPv4.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Withdrawing address record for 10.70.29.178 on eth0.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Interface eth0.IPv4 no longer relevant for mDNS.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: New relevant interface eth0.IPv4 for mDNS.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Registering new address record for 10.70.29.178 on eth0.IPv4.
May 2 16:29:21 rti-is019-con dhclient: bound to 10.70.29.178 -- renewal in 263731 seconds.
May 2 16:29:29 rti-is019-con ntpdate[1886]: adjust time server 91.189.94.4 offset -0.051539 sec
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Mailx stopped working

after a new patch set on the 14th. I noticed that mailx stopped working, as far a I can tell that is the only thing that changed. solaris 10 OS it seems everything is the same, sendmail seems to be running root@server # ps -ef | grep -i sendmail smmsp 687 1 0 10:42:25 ? ... (0 Replies)
Discussion started by: goya
0 Replies

2. AIX

Printer stopped working

I have a serial printer connected to a 16 port ran. All of a sudden my printer stopped working and not sure how to get it back. Can anyone help pint me in the write direction? lsdev -Cc printer gives me the following. lp0 Defined 0A-08-11-00 Other serial printer lp1 Defined 0A-08-11-03... (3 Replies)
Discussion started by: Gmanx
3 Replies

3. Shell Programming and Scripting

Perl script stopped working

Hi, I have the following segment of a script which is supposed to prompt a user for password and then capture the password entered by the user. The function is called in by another script and used to work without issue, the problem is that recently the script is not waiting for the user to... (3 Replies)
Discussion started by: belalr
3 Replies

4. IP Networking

Wireless stopped working- Fedora 12

I installed F12 around the time it was released and it picked up my wireless card and worked like a charm.....Suddenly last week everything stopped working and I receive what appears to be a driver error when wlan0 tries to load. Error for wireless request "Set Mode" (8B06) : SET failed on... (1 Reply)
Discussion started by: woodson2
1 Replies

5. Shell Programming and Scripting

cronjobs stopped working

Hello people, I had these cronjobs scheduled in some Unix boxes which were running fine until yesterday.But then the password was changed for that user id and then the jobs stopped working. As far as i know cron jobs run from super user. I am completely lost over here now. Thanks. (2 Replies)
Discussion started by: King Nothing
2 Replies

6. Linux

Cronjobs stopped working

Hi All, I am user of a Linux machine and I have approximatly 15 cronjobs scheduled in my crontab. Yesterday my administrator made LDAP active on my userid and all the things are doing fine after that. But all cronjobs for my user id stored in my crontab have stopped working after that. Could... (1 Reply)
Discussion started by: bisla.yogender
1 Replies

7. Shell Programming and Scripting

#!/bin/bash has stopped working

Hi I'm writing a script and I've put #!/bin/bash as the first line so that I can just type my scripts name 'whodate' at PS1 instead of ./whodate. This has suddenly stopped working for me. It used to be the case that I could start a script with #!/bin/bash and it would work, but for this script... (2 Replies)
Discussion started by: zorrokan
2 Replies

8. UNIX for Dummies Questions & Answers

VMPlayer stopped working after ubuntu updated kernel

A month or so ago Ubuntu Dapper did its auto-update thing and installed the new kernel (intrd.img-2.6.15-28-386, upgraded from intrd.img-2.6.15-27-386). I rebooted after install and immediately the xserver would not load. I quickly figured out that I could boot the old kernel from GRUB however,... (1 Reply)
Discussion started by: forchessonly
1 Replies

9. Solaris

Internet Connection via Lan

I have a sun wokstation running solaris 9 , I want to configuring my lan card to access internet . my IP address : 192.168.144.20 ISP gateway : 192.168.144.1 DNS address : 202.56.250.5 all helps will be appreciated thanks (2 Replies)
Discussion started by: una
2 Replies
Login or Register to Ask a Question