🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.dcom.modems.cable
Article #55

Re: Bad Cable Modem/AC Adapter?

#55
From: Miguel Sanchez
Date: Tue, 16 Jul 2002 20:19
36 lines
2964 bytes
I would doubt the dhcp server is causing these power issues, but I'm not
a big fan of coincidence either.  Something about all these DCM105
failures, all in the same area and at about the same time, worries me.

Speaking of coicidence -- I too had the same IP address for a long
time... until July 1.  Then it changed to .103.  Interestingly, This
address scanned me several times on June 25.  Not really sure
what that means, but it definitely got me thinking.  Probably just
paranoid.

As far as blocking ports?  I chatted with a ATT helpdesk person last
night.  He told me that ATT was not blocking any ports -- which doesn't
really explain my inability to connect to port 22 from outside.  Not that
it matters, since I can't keep the modem on for more that 45 minutes.
Maybe the IP change or the patching binge I went on last week contributed
to this though -- I haven't looked at my FW rules in a while.  

Probably not the right group for this, but if anyone has any
troubleshooting tips, I'd be glad to know.

Thanks,

Marc

> On Mon, 15 Jul 2002 21:04:14 -0700, Bruce G. Karnacki wrote:
Will a buggy dhcp server cause the modem's power to go out?
> 
> I received yet another note from a Foster City user with a RCA DCM105
> that experienced similar problems.
> 
> BTW, I've had same ip since long before this problem as I do right now.
> Everything has been fine here since Saturday am.  The IM problem that I
> mentioned below cleared up this afternoon.
> 
> Bruce
>
Technical Details
Message-ID: <pan.2002.07.16.13.18.21.300809.17561@noneofyourbusiness.org>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!ucberkeley!logbridge.uoregon.edu!news.maxwell.syr.edu!wn1feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc52.ops.asp.att.net.POSTED!not-for-mail
References: <WtrX8.156334$Uu2.35135@sccrnsc03> <pan.2002.07.13.21.28.39.944679.8216@noneofyourbusiness.org> <aguqrt$5so$1@news.parc.xerox.com> <pan.2002.07.15.18.57.47.31703.17561@noneofyourbusiness.org> <2XMY8.54841$uw.30675@rwcrnsc51.ops.asp.att.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fa874,64f6d60e02a5ec2c
X-Google-Attributes: gidfa874,public
X-Google-Thread: 113850,64f6d60e02a5ec2c
X-Google-Attributes: gid113850,public
X-Google-ArrivalTime: 2002-07-16 13:19:36 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!ucberkeley!logbridge.uoregon.edu!news.maxwell.syr.edu!wn1feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc52.ops.asp.att.net.POSTED!not-for-mail
From: Miguel Sanchez <msanchez@noneofyourbusiness.org>
Subject: Re: Bad Cable Modem/AC Adapter?
Newsgroups: comp.dcom.modems.cable,ba.internet
Message-ID: <pan.2002.07.16.13.18.21.300809.17561@noneofyourbusiness.org>
References: <WtrX8.156334$Uu2.35135@sccrnsc03> <pan.2002.07.13.21.28.39.944679.8216@noneofyourbusiness.org> <aguqrt$5so$1@news.parc.xerox.com> <pan.2002.07.15.18.57.47.31703.17561@noneofyourbusiness.org> <2XMY8.54841$uw.30675@rwcrnsc51.ops.asp.att.net>
User-Agent: Pan/0.11.2 (Unix)
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Comment-To: "Bruce G. Karnacki" <karnacki@invalid.com>
Lines: 36
NNTP-Posting-Host: 12.236.11.103
X-Complaints-To: abuse@attbi.com
X-Trace: rwcrnsc52.ops.asp.att.net 1026850775 12.236.11.103 (Tue, 16 Jul 2002 20:19:35 GMT)
NNTP-Posting-Date: Tue, 16 Jul 2002 20:19:35 GMT
Organization: AT&T Broadband
Date: Tue, 16 Jul 2002 20:19:35 GMT