🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

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

Re: New cox cable managed network

#547
From: PC Medic
Date: Sat, 16 Feb 2002 14:10
45 lines
3906 bytes
"atakicker" <nospam@nospam.net> wrote in message
news:gXib8.10520$SJ3.387856@news1.east.cox.net...
>
> "PC Medic" wrote in message
> > The person dropping the cable should not be the same person installing
the
> > cable modem.
> > If you do not have a drop already in the room where the PC will be, it
> > should have been scheduled separate from the PC and modem configuration.
>
>     Not in my world. I had cable TV and internet installed on the same
day.
> One guy came out and ran the drop from the pole to the house and hooked up
> the TV. Later that day another one came out and ran from the box under the
> eave of the house (which was installed by the first guy) to the computer,
> which is in a different room. The only thing he didn't do was drill
through
> the cinder block wall. I did it for him because I have a 100 pound mean
a__
> dog in the yard. (But I did use his tools). And he did have a problem, he
> screwed up my irq settings and couldn't get my sound card to work. After
45
> minutes of watching him scratch his head and three calls to someone (?), I
> ran him off and reset everything myself.

Sounds like they are having trouble getting broadband installers in your
area and may be cross-training cable techs. This is not the desired (or SOP)
method but unfortunately done in some areas. I must say that you were brave
in the fact that you even let him touch your PC! I would not do this and
would have stopped them at the modem. Anything beyond there becomes, "excuse
me while I make the required settings".

By the way, Why didn't he just use the magic CD?   :)
These types of  problems are exactly why I was telling the "Cox Contractor"
that YES, they do need networking knowledge, because contrary to his claims,
the CD is not a fix all and only configures you IE and Outlook Express not
your network or hardware settings.





>
>
Technical Details
Message-ID: <rLtb8.11334$SJ3.445265@news1.east.cox.net>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!hub1.nntpserver.com!peer1-sjc1.usenetserver.com!usenetserver.com!newsfeeds-atl1.usenetserver.com!cox.net!news1.east.cox.net.POSTED!53ab2750!not-for-mail
References: <I0VX7.10375$B61.4953680@news1.rsm1.occa.home.com> <3C314C9C.DEDF0FCC@reece.net> <82lY7.33203$K36.11443500@news1.rdc1.va.home.com> <3C334AC0.7C6370B@reece.net> <bc5b60f8.0201170659.1fb61766@posting.google.com> <m_V48.3805$zR3.251588@news2.east.cox.net> <bc5b60f8.0201272107.82cbac8@posting.google.com> <dQo68.4657$Xk4.242975@news1.east.cox.net> <ggS68.7796$Xk4.425111@news1.east.cox.net> <y3U68.8160$Xk4.436368@news1.east.cox.net> <3%Z98.7525$zb.402885@news1.east.cox.net> <jQxa8.2975$SJ3.111671@news1.east.cox.net> <ShIa8.4164$SJ3.170583@news1.east.cox.net> <nnPa8.6168$SJ3.212179@news1.east.cox.net> <S4Ra8.6327$SJ3.221438@news1.east.cox.net> <Cagb8.10394$SJ3.374222@news1.east.cox.net> <gXib8.10520$SJ3.387856@news1.east.cox.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10f392,a7865c87070b0fcc
X-Google-Attributes: gid10f392,public
X-Google-Thread: 1136e3,710aa4d82544bdbb
X-Google-Attributes: gid1136e3,public
X-Google-Thread: 113850,a7865c87070b0fcc
X-Google-Attributes: gid113850,public
X-Google-ArrivalTime: 2002-02-16 06:10:36 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!hub1.nntpserver.com!peer1-sjc1.usenetserver.com!usenetserver.com!newsfeeds-atl1.usenetserver.com!cox.net!news1.east.cox.net.POSTED!53ab2750!not-for-mail
From: "PC Medic" <nospam@home.com>
Newsgroups: comp.dcom.modems.cable,cableinet.cable_modems,cox.internet.discussion.athomeconversion
References: <I0VX7.10375$B61.4953680@news1.rsm1.occa.home.com> <3C314C9C.DEDF0FCC@reece.net> <82lY7.33203$K36.11443500@news1.rdc1.va.home.com> <3C334AC0.7C6370B@reece.net> <bc5b60f8.0201170659.1fb61766@posting.google.com> <m_V48.3805$zR3.251588@news2.east.cox.net> <bc5b60f8.0201272107.82cbac8@posting.google.com> <dQo68.4657$Xk4.242975@news1.east.cox.net> <ggS68.7796$Xk4.425111@news1.east.cox.net> <y3U68.8160$Xk4.436368@news1.east.cox.net> <3%Z98.7525$zb.402885@news1.east.cox.net> <jQxa8.2975$SJ3.111671@news1.east.cox.net> <ShIa8.4164$SJ3.170583@news1.east.cox.net> <nnPa8.6168$SJ3.212179@news1.east.cox.net> <S4Ra8.6327$SJ3.221438@news1.east.cox.net> <Cagb8.10394$SJ3.374222@news1.east.cox.net> <gXib8.10520$SJ3.387856@news1.east.cox.net>
Subject: Re: New cox cable managed network
Lines: 47
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <rLtb8.11334$SJ3.445265@news1.east.cox.net>
Date: Sat, 16 Feb 2002 14:10:31 GMT
NNTP-Posting-Host: 68.10.144.175
X-Complaints-To: abuse@cox.net
X-Trace: news1.east.cox.net 1013868631 68.10.144.175 (Sat, 16 Feb 2002 09:10:31 EST)
NNTP-Posting-Date: Sat, 16 Feb 2002 09:10:31 EST
Organization: Cox Communications