🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

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

Re: New cox cable managed network

#558
From: PC Medic
Date: Sun, 17 Feb 2002 19:39
213 lines
10960 bytes
"Brian" <bswindle@charter.net> wrote in message
news:3C6E9AC8.41A0EAB4@charter.net...
>    The CD Charter Pipeline uses configures network settings such as DHCP
and
> DNS, as well as e-mail servers and newsgroup server settings. It does
install a
> branded version of Internet Explorer, but those who know their system can
remove
> the logo of it bothers them that much. The Charter CD also checks some
registry
> values, such as the DefaultRcvWindow, to make sure they are still at
default.
> Many dial-up internet optimizer programs scale those settings back to
improve
> performance over a slow network, putting a poor cap on your speed. That is
just
> one advantage to using the supplied software when setting up a cable modem
> connection. If a person is comfortable with doing those things manually
there is
> no need to use the CD, but not everyone is.
>
>    I see on the Cox  home page that their CD is advertised to do the same
thing.
> Are you saying that is not correct, or have you actually used the CD
yourself?
> Obviously, there would be little sense to sending out the CD if it didn't
do
> anything at all; which is what you seem to be implying. It doesn't
configure
> Netscape settings, but it does get IE and Outlook Express up and running.

Please provide the URL where it states the CD configures all your network
settings.

The CD installs and configures a Cox branded version of IE/OE along with
other various troubleshooting utilities. They send it out because contrary
to your beliefs, the majority of internet users coming on line to day are
clueless when it comes to completing what others may consider a simple task.
This is a result of the PC being pushed in every store from Wal-Mart to Best
buy as a home appliance.
Everybody's gotta have one, but once they get them, they don't know what
they are going to do with it.

>
>    Installation of the NIC card and connection to the modem is actually a
> painless process and there is no reason a cable installer with basic
computer
> knowledge shouldn't be able to complete the entire job, without an
additional
> trip being necessary. That is not 'cross-training';  just training an
installer
> to do the entire job.

It's "cross-training" if you are using a cable TV installer to install
broadband.
I have seen cable techs that could not tell you the difference between a ISA
and a PCI slot. And why should they, it was never their job and they may not
have any personal interest in PC's outside of work either. If the NIC is not
already installed, is the "Cable Guy" going to know enough to verify the
customer has an available IRQ "BEFORE" he starts reconfiguring their system.
Is the cable guy going to be familiar enough with PC's to know that simply
shutting down the PC is not sufficient when installing an expansion card?,
or is he going to plug the card in while there is still voltage on the slots
as is the case in ATX boards.
So yes, cross training is needed.

From my experience, the only time there is a problem is if
> the computer already has a problem or doesn't have the resources needed to
work
> with the ethernet card (ie... lack of IRQ's, due to peripherals, or hard
drive
> space).  It is the customers' responsibility to make sure they have a
properly
> functioning machine for the NIC to be installed in.

A machine that has no open IRQ for an additional card to be installed is
indeed functioning properly.
But again, the average Joe doesn't have a clue as to what an IRQ is, let
alone if they have one available.
At this point it becomes the installers job to determine this BEFORE he
fudges the system by creating resource conclicts.

 Registry and hardware
> problems are not the responsibility of the installer to correct. SOP is
for the
> installer to have the customer shut down and reboot the PC before any work
is
> done; if it has any errors on start-up, the installer should politely
inform the
> customer they need to have the problem corrected and call back to
reschedule the
> installation. Many times I've seen an install attempted where a person
said "Oh
> it's always done that, I just click through it", only to hear claims later
that
> the installer messed up the PC because the sound card or printer didn't
work
> after the card was installed. Often it turns out there were not enough
IRQ's
> available, the PC had dead slots on the board, or the registry was
corrupted.
> That's why it's better to prevent bad feelings ahead of time and politely
inform
> the customer that we can't proceed with the installation until the
computer
> issue has been resolved.

Of course if the system has errors on boot then you would possibly not
proceed (depending on the type of error), but, rebooting a PC is NOT going
to tell the installer that there is an available IRQ. And if he is not
trained to verify there is one, the customer probably will be calling after
he leaves to complain about lost sound, or other issues.

>
>    Basically, the installer isn't there to fix the computer; just to add a
NIC
> to a properly functioning PC. Anything beyond that is not his job. If the
> machine won't accept a NIC it has a problem, and the customer needs to
have that
> problem corrected themselves.

You obviously aren't aware that the system will almost always accept the NIC
even if it attempts to share the IRQ with another device. What two devices
should never share resources with another device, yet Windows will report
they are functioning properly?

> What you are saying, is that you want the cable
> company to send out a computer technician who is able to correct problems
with
> your PC that existed before they attempted to install the cable modem
service.

No, actually I said I do not let outside techs in my system at all. I am
saying that the technicians being sent out should know how to resolve things
like a simple IRQ conflict in the PC should one occur after the install of
the NIC. Even in a system with an available IRQ (and in the proper range for
a NIC) can have a conflict occur after the card is installed. Or do you feel
that the tech should say "Hey, broadband is working great!, sorry we screwed
up your printing services though".


> The installation of a NIC in a 'properly functioning' PC is almost
automatic and
> just about anybody could do it if they aren't afraid to open their
computer up.

"almost", and "just about", only count in Horse Shoes and Hand Gernades!
And you continue to verify what I am saying. It is not a perfect world when
it comes to PC's. That is why plug-n-play is often called plug-n-pray, AND
why the tech does need to be cross-trained with basic PC knowledge.


>
> PC Medic wrote:
>
> > "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: <oFTb8.2586$7Q6.139409@news1.east.cox.net>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.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> <rLtb8.11334$SJ3.445265@news1.east.cox.net> <3C6E9AC8.41A0EAB4@charter.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: 113850,a7865c87070b0fcc
X-Google-Attributes: gid113850,public
X-Google-Thread: 1136e3,710aa4d82544bdbb
X-Google-Attributes: gid1136e3,public
X-Google-ArrivalTime: 2002-02-17 11:39:06 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.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> <rLtb8.11334$SJ3.445265@news1.east.cox.net> <3C6E9AC8.41A0EAB4@charter.net>
Subject: Re: New cox cable managed network
Lines: 215
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: <oFTb8.2586$7Q6.139409@news1.east.cox.net>
Date: Sun, 17 Feb 2002 19:39:00 GMT
NNTP-Posting-Host: 68.10.144.175
X-Complaints-To: abuse@cox.net
X-Trace: news1.east.cox.net 1013974740 68.10.144.175 (Sun, 17 Feb 2002 14:39:00 EST)
NNTP-Posting-Date: Sun, 17 Feb 2002 14:39:00 EST
Organization: Cox Communications