🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.mac.apps
Article #12769

Re: Mac-Comcast-Internet connection diagnostic?

#12769
From: Barry Margolin
Date: Sun, 18 Jul 2010 04:21
36 lines
2908 bytes
In article <siegman-9BFF1F.15371317072010@sciid-srv02.med.tufts.edu>,
 AES <siegman@stanford.edu> wrote:

> I normally connect to the Internet via a Comcast residential service 
> with the following physical devices in the chain:
> 
>    MacBook (10.4.11) --- Airport Extreme base station ====
>    Comcast-provided modem (a Motorola "Surfboard") +++ (outside world)
> 
> where --- is an Airport WiFI link; === is Cat 45 Ethernet cable; and +++ 
> is a Comcast cable coming from the street.  We also have Comcast VOIP 
> service for 4 or 5 telephone lines which I believe connected into the 
> +++ cable somewhere upstream from the Comcast modem.
> 
> All of this work great the majority of the time, but there have been two 
> service outages during the past month when Internet and phone service 
> went down for 4 to 8 hours.  In  the most recent case,  the phone came 
> back up after a few hours, but the Internet connectivity remained out 
> for several more hours.
> 
> The JPEGs at <http://www.stanford.edu/~siegman/Comcast1.jpg> 
> and <http://www.stanford.edu/~siegman/Comcast2.jpg> show what I see at 
> different times, using the Network pane in the Mac's System Preferences 
> as a way of attempting to diagnose whether the outage means something is 
> wrong in my local settings or hardware, or Comcast is really down.

The Mac can only tell whether its WiFi connection to the AEBS is up.  

You can go to 192.168.100.1 to see the status of the modem.  If you can 
get to this address, then the Mac and AEBS are fine.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
Technical Details
Message-ID: <barmar-F56611.00213018072010@62-183-169-81.bb.dnainternet.fi>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
References: <siegman-9BFF1F.15371317072010@sciid-srv02.med.tufts.edu>

Show Full Headers
Complete Article Headers
X-Google-Thread: feb82,fe0716acc430a125
X-Google-NewGroupId: yes
X-Google-Thread: fa874,fe0716acc430a125
X-Google-NewGroupId: yes
X-Google-Attributes: gid2291d6f89e,gidaa617e85ca,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Barry Margolin <barmar@alum.mit.edu>
Newsgroups: comp.sys.mac.apps,ba.internet
Subject: Re: Mac-Comcast-Internet connection diagnostic?
Date: Sun, 18 Jul 2010 00:21:30 -0400
Organization: A noiseless patient Spider
Lines: 36
Message-ID: <barmar-F56611.00213018072010@62-183-169-81.bb.dnainternet.fi>
References: <siegman-9BFF1F.15371317072010@sciid-srv02.med.tufts.edu>
Injection-Date: Sun, 18 Jul 2010 04:21:30 +0000 (UTC)
Injection-Info: barmar.motzarella.org; posting-host="+bxBiZT/p0ZLLuDb5H+JCw";
 logging-data="7270"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/LE/KCfF4AMusGZ+zA4sOb"
User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)
Cancel-Lock: sha1:mWT1zCC7tMxi6L40pGG3kydg7UU=