More Info: Cannot Connect to Ethernet (Colin Law)

[doug]

On 03/21/2013 09:40 PM, Mine Last wrote:
>>     2. Re: More Info: Cannot Connect to Ethernet (Colin Law)
>> Message: 2
>> Date: Thu, 14 Mar 2013 19:57:08 +0000
>> From: Colin Law <clanlaw at googlemail.com>
>> To: "Ubuntu user technical support, not for general discussions"
>>          <ubuntu-users at lists.ubuntu.com>
>> Subject: Re: More Info: Cannot Connect to Ethernet
>> Message-ID:
>>          <CAL=0gLufwxKEx5WqiXw-8KPsmuOvZVk8nVUxqj6w2huSw3yFiA at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> On 13 March 2013 00:37, Mine Last <information.security.admin at gmail.com> wrote:
>>> Rebooted with no changes at all. Rebooted with and without Ethernet plugged
>>> in. Nothing worked.
>>>
>>> *With the ethernet plugged in (get *that working first, then sort out *the
>>> wireless) what do you see if *you click on the network icon in *the top
>>> right (the icon may be *two arrows or it may be a fan *shape)?
>>> *Also is it the two arrows or the *fan?
>>>
>>> The icon is fan shaped; all I see is the open fan icon with nothing inside
>>> it. If I click on it I see:
>>> No network connection(greyed out)
>>> VPN Connections (in white)
>>> Enable Networking (in white with a checkmark next to it)
>>>
>>> *If you click on Connection *Information in the dropdown *from the network
>>> icon what does *it say *in the ipv4 section?
>>>
>>> I cannot click on Connection information because it is greyed out.
>> Since you have broken the thread and also not quoted the previous
>> message it is not clear what this message is about.  However, what do
>> you see if, in a terminal, you do
>>
>> sudo lshw -C network
>>
>> This should show you your network interfaces.  Copy/paste the result here.
>>
>> Colin
>>
> Colin and All,
>
> Sorry for breaking the thread, I hope I didn't do the same thing by
> replying to the digest message I got and then editing the Subject
> field. List watching is not new at all to me; messaging a list is very
> new. Sorry for the break down of etiquette. Following is a copy and
> paste of the information when I typed in sudo lshw -C network at a
> terminal window:
>
>   *-network
>         description: Network controller
>         product: BCM4311 802.11b/g WLAN
>         vendor: Broadcom Corporation
>         physical id: 0
>         bus info: pci at 0000:0b:00.0
>         version: 01
>         width: 32 bits
>         clock: 33MHz
>         capabilities: pm msi pciexpress bus_master cap_list
>         configuration: driver=wl latency=0
>         resources: irq:16 memory:efdfc000-efdfffff
>    *-network UNCLAIMED
>         description: Ethernet controller
>         product: BCM4401-B0 100Base-TX
>         vendor: Broadcom Corporation
>         physical id: 0
>         bus info: pci at 0000:03:00.0
>         version: 02
>         width: 32 bits
>         clock: 33MHz
>         capabilities: pm bus_master cap_list
>         configuration: latency=64
>         resources: memory:ef9fe000-ef9fffff
>
> Hopefully that is what your after. Hopefully it will translate without
> losing the formatting. Thanks for the help.
>
> -Steve
>
I am having a somewhat similar problem on a new Windows 8 install (which 
I tried just to see what all the fuss is about).
What it boils down to in my case is that the DNS resolver is not being 
activated. I can ping the ip address of the server,\and that works. So, 
just for the heck of it, try that. It might give you a clue as to where 
the problem is.

--doug

-- 
Blessed are the peacemakers...for they shall be shot at from both sides. --A. M. Greeley