can't connect with wired ethernet

[bagatelles]

Everything was working fine so far, never had trouble. I switched to wireless for a few days and now that i'm back to wired ethernet i can't browse or do anything. KNetworkManager gives me a message "Wired ethernet connection active: eth0" but i can't possibly open a browser and get on-line. Anyone know what's going on? I also have wassistant installed. Don't know if that's causing any problems. Thanks.

[bagatelles]

Re: can't connect with wired ethernet

here's the output from ifconfig -a if anyone is willing to help out. I also tried booting into the the previous kernel before the updates were made but no luck there either.

eth0 Link encap:Ethernet HWaddr 00:01:4A:CA:60:0C
inet addr:192.168.1.66 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::201:4aff:feca:600c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:186 errors:0 dropped:0 overruns:0 frame:0
TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23744 (23.1 KiB) TX bytes:11882 (11.6 KiB)
Interrupt:217 Base address:0xe000

eth1 Link encap:Ethernet HWaddr 00:13:CE:58:4D:20
inet addr:192.168.1.111 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:ceff:fe58:4d20/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2004 errors:0 dropped:0 overruns:0 frame:0
TX packets:1897 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:1680660 (1.6 MiB) TX bytes:628508 (613.7 KiB)
Interrupt:225 Base address:0x6000 Memory:b0107000-b0107fff

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:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7410 (7.2 KiB) TX bytes:7410 (7.2 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[Azrael]

Re: can't connect with wired ethernet

Simple suggestion, but does turning off the wireless adapter have any effect?

[bagatelles]

Re: can't connect with wired ethernet

nope. no diference.

I've also tried turning everything off, both computer and router and then restarting with wires plugged and wireless off but still no change. and i haven't made any changes whatsoever to dns servers or profiles since everything was running fine.

[jamesr]

Re: can't connect with wired ethernet

Hi,

The ifconfig output indicates that eth0 and eth1 have addresses. Do you have router and if so can you ping the router.

If that works can you ping google.com ?

Please post the outputs.

[bagatelles]

Re: can't connect with wired ethernet

Hello there too

I thought the problem might have been the ips, cause it was showing that packets were coming from 192.168.1.111 when pinging the router, and which was the IP on eth1. I changed eth0 to 192.168.1.111 to see if any difference but nothing. Then i've changed both to 192.168.1.66 but nothing again.

Thanks guys for showing up here.

eth0   Link encap:Ethernet HWaddr 00:01:4A:CA:60:0C 
     inet addr:192.168.1.66 Bcast:192.168.1.255 Mask:255.255.255.0
     inet6 addr: fe80::201:4aff:feca:600c/64 Scope:Link
     UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
     RX packets:57 errors:0 dropped:0 overruns:0 frame:0
     TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:1000 
     RX bytes:3989 (3.8 KiB) TX bytes:2680 (2.6 KiB)
     Interrupt:217 Base address:0x2000 

eth1   Link encap:Ethernet HWaddr 00:13:CE:58:4D:20 
     inet addr:192.168.1.111 Bcast:192.168.1.255 Mask:255.255.255.0
     inet6 addr: fe80::213:ceff:fe58:4d20/64 Scope:Link
     UP BROADCAST MULTICAST MTU:1500 Metric:1
     RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     TX packets:0 errors:0 dropped:0 overruns:0 carrier:1
     collisions:0 txqueuelen:1000 
     RX bytes:4587998 (4.3 MiB) TX bytes:537967 (525.3 KiB)
     Interrupt:225 Base address:0x6000 Memory:b0107000-b0107fff 

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:31 errors:0 dropped:0 overruns:0 frame:0
     TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:0 
     RX bytes:2712 (2.6 KiB) TX bytes:2712 (2.6 KiB)

chris@host:~$ sudo ifconfig eth1 192.168.1.66
chris@host:~$ sudo ifconfig eth0 192.168.1.66
chris@host:~$ ping -c 3 [url]www.google.com[/url]
ping: unknown host [url]www.google.com[/url]

chris@host:~$ ping -c 3 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
From 192.168.1.66 icmp_seq=1 Destination Host Unreachable
From 192.168.1.66 icmp_seq=2 Destination Host Unreachable
From 192.168.1.66 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.254 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2012ms
, pipe 3

and the new one:

eth0   Link encap:Ethernet HWaddr 00:01:4A:CA:60:0C
     inet addr:192.168.1.66 Bcast:192.168.1.255 Mask:255.255.255.0
     inet6 addr: fe80::201:4aff:feca:600c/64 Scope:Link
     UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
     RX packets:753 errors:0 dropped:0 overruns:0 frame:0
     TX packets:118 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:1000
     RX bytes:46182 (45.0 KiB) TX bytes:8344 (8.1 KiB)
     Interrupt:217 Base address:0x2000

eth1   Link encap:Ethernet HWaddr 00:13:CE:58:4D:20
     inet addr:192.168.1.66 Bcast:192.168.1.255 Mask:255.255.255.0
     inet6 addr: fe80::213:ceff:fe58:4d20/64 Scope:Link
     UP BROADCAST MULTICAST MTU:1500 Metric:1
     RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     TX packets:0 errors:0 dropped:0 overruns:0 carrier:1
     collisions:0 txqueuelen:1000
     RX bytes:4594010 (4.3 MiB) TX bytes:539214 (526.5 KiB)
     Interrupt:225 Base address:0x6000 Memory:b0107000-b0107fff

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:54 errors:0 dropped:0 overruns:0 frame:0
     TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:0
     RX bytes:5020 (4.9 KiB) TX bytes:5020 (4.9 KiB)

[jamesr]

Re: can't connect with wired ethernet

Hi,

Can I assume that the router address is 192.168.1.254

chris@host:~$ ping -c 3 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
From 192.168.1.66 icmp_seq=1 Destination Host Unreachable
From 192.168.1.66 icmp_seq=2 Destination Host Unreachable
From 192.168.1.66 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.254 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2012ms
, pipe 3

If the answer is yes can you can you do the following and post the results.

ping localhost
ping 192.168.1.xxx where xxx is your local address

[bagatelles]

Re: can't connect with wired ethernet

yes, that's my router.

here's localhost and 192.168.1.66

PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.042 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.041 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.051 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.041 ms
64 bytes from localhost (127.0.0.1): icmp_seq=5 ttl=64 time=0.043 ms

--- localhost ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4013ms
rtt min/avg/max/mdev = 0.041/0.043/0.051/0.008 ms

PING 192.168.1.66 (192.168.1.66) 56(84) bytes of data.
64 bytes from 192.168.1.66: icmp_seq=1 ttl=64 time=0.042 ms
64 bytes from 192.168.1.66: icmp_seq=2 ttl=64 time=0.038 ms
64 bytes from 192.168.1.66: icmp_seq=3 ttl=64 time=0.038 ms
64 bytes from 192.168.1.66: icmp_seq=4 ttl=64 time=0.038 ms
64 bytes from 192.168.1.66: icmp_seq=5 ttl=64 time=0.038 ms

--- 192.168.1.66 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 0.038/0.038/0.042/0.008 ms

[sky]

Re: can't connect with wired ethernet

Hi,

I don't really get why you're setting twice the same ip on two different interfaces... It shouldn't be like this, but anyway you can get to the router.
Now you should just enter your dns server in the file /etc/resolv.conf like this :
nameserver xxx.xxx.xxx.xxx
These ips should be given by your isp.

Hope it helps.

[bagatelles]

Re: can't connect with wired ethernet

Hi

well the reason i did that was because when i was pinging with the wireless off and my eth0 set to 192.168.1.66 the reports were showing that packets were leaving from 192.168.1.111 which was eth1. I thought that might have been causing trouble somehow. I tried both ways setting everything to x.x.x.66 and x.x.x.111 but no change. Now it's back to 192.168.1.66 for eth0 and 192.168.1.111 for eth1.

here's the output from cat /etc/resolv.conf :
search gateway.2wire.net
nameserver 192.168.1.254

Both point to my gateway. As i said, I did not do any changes to the servers after i switched to wireless.

Thanks guys, i'll call my isp about the dns servers and see what they give me. I'll let you know if that fixes my problem.

[sky]

Re: can't connect with wired ethernet

Hi,

If you can ping the router it's good at least
Anyway, if you don't want to call your isp or can't wait to connect to internet and that you have a windows somewhere on this network connected to this router, you can issue the command : "ipconfig /all" on the windows box and you will get this dns servers.

Cheers

[lec2004]

Re: can't connect with wired ethernet

try disconnecting one of the cables. There is no reason to have two active NICs on the same network. Your computer probally sees it as two active DHCP servers . There should be no reason to manually enter your DNS info as Linux is plug and play. try running a live cd (preferably damn small linux as it loads within a couple of minutes) with one NIC plugged and see what happens.

[bagatelles]

Re: can't connect with wired ethernet

well i've tried both ways. i did manage to get eth0 to work when i booted into the live cd. I just used Kubuntu. When i rebooted into my installed version, it worked fine (!!), even though i checked the configurations on the live distro and they were the same to what i had before. Now the wireless won't work again. If i reboot with wireless on and reconfigure it in Network Settings...add DNS..it will work if i keep trying on wassisstant a few times. But then switching back to eth0, wired ethernet won't work again. Not even if i reboot with wireless off and let the system recognize eth0. Same problem. I guess rebooting back into the live cd will make it magically work again.

Anyway, i don't know what's going on. At least somehow it worked when i booted into the live cd...it came in handy. I wish both eth0 eth1 could work fine though, at least with a reboot each time i switch it would still be perfect.

Thank you very very much guys for your help and support. I trully appreciate it. Million Thanks.

BTW I have windows on the same machine as well, the one it came with. Executing ipconfig /all brings me the output below. Nothing different from what i get on Linux it seems.

Windows IP Configuration



    Host Name . . . . . . . . . . . . : localhost

    Primary Dns Suffix . . . . . . . : 

    Node Type . . . . . . . . . . . . : Broadcast

    IP Routing Enabled. . . . . . . . : No

    WINS Proxy Enabled. . . . . . . . : No

    DNS Suffix Search List. . . . . . : gateway.2wire.net



Ethernet adapter Local Area Connection:



    Connection-specific DNS Suffix . : gateway.2wire.net

    Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC

    Physical Address. . . . . . . . . : 00-01-4A-CA-60-0C

    Dhcp Enabled. . . . . . . . . . . : Yes

    Autoconfiguration Enabled . . . . : Yes

    IP Address. . . . . . . . . . . . : 192.168.1.66

    Subnet Mask . . . . . . . . . . . : 255.255.255.0

    Default Gateway . . . . . . . . . : 192.168.1.254

    DHCP Server . . . . . . . . . . . : 192.168.1.254

    DNS Servers . . . . . . . . . . . : 192.168.1.254

    Lease Obtained. . . . . . . . . . : Tuesday, October 17, 2006 2:54:26 AM

    Lease Expires . . . . . . . . . . : Wednesday, October 18, 2006 2:54:26 AM



Ethernet adapter Wireless Network Connection:



    Media State . . . . . . . . . . . : Media disconnected

    Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Network Connection

    Physical Address. . . . . . . . . : 00-13-CE-58-4D-20

[bagatelles]

Re: can't connect with wired ethernet

Hey

i guess the live cd really did some magic after all. Woke up this morning, turned on the computer with wires plugged in and everything works again.


Thanks again guys.