I can't connect to a wired connection

Asked by Maria

Hello,
We've been having a wireless connection problem in our house lately, so I tried to connect through the wired connection. It just doesn't work. I really know very little about computers so I have no clue what to do. I am using Ubuntiu 8.10 and my machine is a HP ADM 64. If i go to edit connection it shows
Auto ethernet
connect automatically is checked, system setting is not.
There is nothing in the MAC box and the MTU says automatic.
the 802.1 tab nothings selected
and IPV4 say automatic DHCp, but teh box where it says DHCP client, has nothing.

If you need any other info please let me know.
Thanks a lot for all your help
Maria

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Tom
Solved:
Last query:
Last reply:
Revision history for this message
Tom (tom6) said :
#1

Hi, i usually get asked to open a terminal console and type in "ifconfig" ( on Windows machines that'd be ipconfig) and copy the info into here.

So, go up to the Applications menu on the top taskbar, down to Accessories and choose terminal. Into the Terminal/command window/console type

ifconfig

and copy & paste the info here.

Good luck with this
Regards from
Tom

Revision history for this message
Maria (mjvargas1971) said :
#2

This is what I got, but it is funny because I just have one port for cable conection, so why are there 2 ethernets?

eth0 Link encap:Ethernet HWaddr 00:1d:72:59:0a:00
          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:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:252 Base address:0x4000

eth1 Link encap:Ethernet HWaddr 00:21:00:12:7c:fc
          inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::221:ff:fe12:7cfc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:14416 errors:0 dropped:0 overruns:0 frame:49951
          TX packets:11937 errors:115 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3256499 (3.2 MB) TX bytes:1476290 (1.4 MB)
          Interrupt:20

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:1001 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1001 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:29809 (29.8 KB) TX bytes:29809 (29.8 KB)

vnet0 Link encap:Ethernet HWaddr ae:d5:59:70:f5:01
          inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
          inet6 addr: fe80::acd5:59ff:fe70:f501/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:5760 (5.7 KB)

Revision history for this message
Maria (mjvargas1971) said :
#3

Tom wrote:
> Your question #58892 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/58892
>
> Status: Open => Answered
>
> Tom proposed the following answer:
> Hi, i usually get asked to open a terminal console and type in
> "ifconfig" ( on Windows machines that'd be ipconfig) and copy the info
> into here.
>
> So, go up to the Applications menu on the top taskbar, down to
> Accessories and choose terminal. Into the Terminal/command
> window/console type
>
> ifconfig
>
> and copy & paste the info here.
>
> Good luck with this
> Regards from
> Tom
>
>

Thanks a lot Tom I just that.

Revision history for this message
nhasian (nhasian) said :
#4

you have two different MAC addresses, you must have two network adaptors? take a look with the terminal command:

lshw -C network

also it looks like eth1 is getting an ip address. lets see if it can communicate with the router with the command:

ping -c 6 192.168.1.1

Revision history for this message
Tom (tom6) said :
#5

I tried the

lshw -C network

command in a terminal console on my machine and got shed-loads of information. It wasnt happy about e running it without sudoing it. I guess we're more interested in the results of the ping command for Maria's machine so please open a terminal window (same way as before) and type in

sudo lshw -C network

the password it might ask for is your user password rather than a Root/SuperUser password. Hmm, i guess we do want the output, particularly for the eth1 device. Then in the terminal window/console type or paste in

ping -c 6 192.168.1.1

and give it a few minutes to try and find something it can get a response. I'd say 5mins is about as long as i would wait, ie enough time to grab a cuppa ;)

Good luck with this
Regards from
Tom

Revision history for this message
Maria (mjvargas1971) said :
#6

nhasian wrote:
> Your question #58892 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/58892
>
> Status: Open => Answered
>
> nhasian proposed the following answer:
> you have two different MAC addresses, you must have two network
> adaptors? take a look with the terminal command:
>
> lshw -C network
>
> also it looks like eth1 is getting an ip address. lets see if it can
> communicate with the router with the command:
>
> ping -c 6 192.168.1.1
>
>
This is what I got when I put into the terminal the command you sent me.
WARNING: you should run this program as super-user.
  *-network
       description: Ethernet interface
       product: MCP67 Ethernet
       vendor: nVidia Corporation
       physical id: a
       bus info: pci@0000:00:0a.0
       logical name: eth0
       version: a2
       serial: 00:1d:72:59:0a:00
       width: 32 bits
       clock: 66MHz
       capabilities: bus_master cap_list ethernet physical
       configuration: broadcast=yes driver=forcedeth driverversion=0.61
latency=0 maxlatency=20 mingnt=1 module=forcedeth multicast=yes
  *-network
       description: Wireless interface
       product: BCM4312 802.11b/g
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: eth1
       version: 01
       serial: 00:21:00:12:7c:fc
       width: 64 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=wl0 driverversion=5.10.27.12
ip=192.168.1.2 latency=0 module=wl multicast=yes wireless=IEEE 802.11
  *-network:0
       description: Ethernet interface
       physical id: 1
       logical name: vnet0
       serial: ae:d5:59:70:f5:01
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3
firmware=N/A ip=192.168.122.1 multicast=yes
  *-network:1 DISABLED
       description: Ethernet interface
       physical id: 2
       logical name: pan0
       serial: 12:15:43:c0:38:4e
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3
firmware=N/A multicast=yes

And when I run the other command $ ping -c 6 192.168.1.1 I got this.

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=3.05 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.05 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.36 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=3.04 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=3.05 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=3.06 ms

--- 192.168.1.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5028ms
rtt min/avg/max/mdev = 2.366/2.941/3.065/0.266 ms
what does this means?

Revision history for this message
Best Tom (tom6) said :
#7

If you are still having trouble with this then please post it as a new question. Only the most recent questions tend to get looked at so posting/reposting a question just before america arrives online gives the best chance of getting a good few answers.

If the problem has been resolved then please follow the link to the forum thread and mark it as Solved.

Good luck and many regards from
Tom :)

Revision history for this message
Maria (mjvargas1971) said :
#8

Thanks Tom, that solved my question.

Revision history for this message
Tom (tom6) said :
#9

Re-posting a new question seems to work well.

Good luck and regards from
Tom