iMac ethernet connection quit - help?

Wayne Sudol wsudol at scng.com
Mon Jun 26 16:33:38 CDT 2017


Mark,  try opening a terminal window.  ifconfig -a will show you all
interfaces and their status. If en0: is down you can try ifconfig  en0: up
and see if it get an ethernet address. I.E. sudo ifconfig en0 up
If it comes up, trying pinging your router or any other addresses on your
local network as a verification.

The man page from a terminal window will help with the options to the
ifconfig command. I.E. man ifconfig

Here's an example from my mac.
fconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_HWTAGGING>
ether 10:9a:dd:46:17:fc
inet6 fe80::139c:ddff:fe56:18fc%en0 prefixlen 64 scopeid 0x4
inet 10.82.110.47 netmask 0xfffffe00 broadcast 10.82.110.255
nd6 options=1<PERFORMNUD>
media: autoselect (100baseTX <full-duplex,flow-control>)
status: active
en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether c8:ac:c8:c8:43:d4
nd6 options=1<PERFORMNUD>
media: autoselect (<unknown type>)
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 70:cc:60:ff:fe:35:ec:26
nd6 options=1<PERFORMNUD>
media: autoselect <full-duplex>
status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
ether 0a:bc:c8:c8:43:d4
media: autoselect
status: inactive




On Mon, Jun 26, 2017 at 12:53 PM, Tapley, Mark via cctech <
cctech at classiccmp.org> wrote:

> On Jun 26, 2017, at 10:01 AM, Liam Proven via cctalk <
> cctalk at classiccmp.org> wrote:
>
> > On 26 June 2017 at 16:44, Tapley, Mark via cctech <cctech at classiccmp.org>
> wrote:
> >> All,
> >>         having problems with my iMac G3. Ethernet stopped working, but
> still shows some signs of life. Any suggestions welcome!
>
> Liam,
>         thanks for the response! Note, ethernet *was* working and then
> stopped, with no obvious action on my part. That said, answers in-line
> below.
>
> > Some superficially odd questions...
> >
> > What OS is it running?
>
> Mac OS 10.4.11, classic installed.
>
> > Is the firmware up to date?
>
> I don’t know the answer to that. I got it used, and don’t think I have
> updated it.Is there a good way to tell?
>
> > If the firmware isn't, you *will* experience problems with OS X. If it
> > is running OS X, you can't update the firmware -- you need Classic
> > MacOS 9 to do that. :-(
>
> I probably can still have my 9.x install dask - I’ll look - and my 10.4
> disk. I”m pretty sure there are things I’ll lose doing 2 re-installs, but
> maybe I can back them up to a USB memory to restore.
>
> > Have you tried a different hub?
>
> Not yet, but will do, hopefully tonight. Does direct (ethernet) connection
> to another Mac, sharing its wi-fi to computers using ethernet, count in
> this context? But I also have a hub built into a retired (DSL) modem which
> I’m thinking about installing there to free up the 8-port hub; this can
> motivate me to do that sooner.
>
> One other thing I forgot to mention: iPv6 broke this machine’s internet a
> few months back; so I disabled it through the System Preferences check-box,
> and it came back up immediately on ipV4. Same thing happened at the same
> time to the PowerBook G4 (also on 10.4.11) so I attributed that to the
> service provider (and they actually notified us that they were changing to
> v6).


More information about the cctech mailing list