🚀 go-pugleaf

Not that skilled help is necessarily hard to find here, but why on earth
would anyone who knows any better want to be installing cable modems for $10
an hour working in the weather year round when you could be making over
$30,000 a year to start by, in some cases, doing near nothing.

And as I said before, techs don't need to know the difference.  All they do
now is plug in and install the software, per Cox Communications Standard
Operating Procedure.

Derek




"PC Medic" <nospam@home.com> wrote in message
news:jQxa8.2975$SJ3.111671@news1.east.cox.net...
>
> "Derek M. Loseke" <spamderek@cox.net> wrote in message
> news:3%Z98.7525$zb.402885@news1.east.cox.net...
> > Sorry.  I guess I just live in a world (Windows 2000) where the Netbios
> name
> > is usually the same as the DNS, with the exception of the DNS suffix.
>
> Not so
>
> >
> > Also, your typical contractor doesn't need the know the difference
between
> > DNS and NetBIOS.  I personally guarantee that 75% of Cox Field Techs
> > installing CHSI don't.
> >
>
> Appears you are in an area where "skilled" help is hard to find!
>
> >
> >
> > "Arthur Hagen" <art@broomstick.com> wrote in message
> > news:y3U68.8160$Xk4.436368@news1.east.cox.net...
> > >
> > > "PC Medic" <nospam@home.com> wrote in message
> > > news:ggS68.7796$Xk4.425111@news1.east.cox.net...
> > > > Actually Cox@Home did use a MAC address, that of the modem, just as
> Cox
> > > > continues to do now on their own network. Also, the NetBios name and
> DNS
> > > > names are two different things, and while @Home used the computer
name
> > for
> > > > IP assigning the new Cox managed network does not.
> > > >
> > > > Cox Contractor???????
> > >
> > > It's not very assuring when they hire contractors who can't tell
NetBIOS
> > and
> > > DNS apart (and gets a few other things plain wrong too).
> > >
> > > Regards,
> > > --
> > > *Art
> > >
> > > > "Derek M. Loseke" <spamderek@cox.net> wrote in message
> > > > news:dQo68.4657$Xk4.242975@news1.east.cox.net...
> > > > > Actually, @Home didn't use MAC Addresses, at least on on the Cox
> > > network.
> > > > > For Cox, they used the NetBios (DNS) Name to reserve IP Addresses.
> > The
> > > > MAC
> > > > > address had nothing to do with it on the Cox network, and I
imagine
> > that
> > > > is
> > > > > also true for Comcast and AT&T.
> > > > >
> > > > >
> > > > > Also, the software doesn't detect all NIC's.  It has nothing to do
> > with
> > > > the
> > > > > Modem.  However, we do have some problems with the old CyberSurf
> > modems.
> > > > > They should work however.  As long as your modem comes online,
> > > everything
> > > > is
> > > > > cool.  As for the software, it doesn't make a diference....you
don't
> > > need
> > > > > it.
> > > > >
> > > > > Derek
> > > > > Cox Contractor
> > > > >
> > > > >
> > > > >
> > > > > "Suellen" <Suellen_Stewart@msn.com> wrote in message
> > > > > news:bc5b60f8.0201272107.82cbac8@posting.google.com...
> > > > > > I'm fairly certain that the migration had taken place, because I
> > > > > > initially did receive an IP address in the 68.xxx.xxx.xxx range,
> > > > > > before it reverted back to the old one in the 65.xxx.xxx.xxx
> range.
> > > > > > Whatever the explanation was, I have reverted to the correct
> > settings
> > > > > > (using DHCP)and everything is working for now. I am interested
in
> > your
> > > > > > statement that they "had to do something on their end." I know
> that
> > > > > > @home had a setup that required you to register the mac address
of
> a
> > > > > > new adapter if you changed your hardware, but that cox is not
> > supposed
> > > > > > to be set up that way. That seems to be confirmed by the fact
that
> I
> > > > > > can switch my laptop for the desktop that's normally attached to
> the
> > > > > > cable modem, and it will work. HOWEVER - tonight I tried to help
a
> > > > > > friend set up the same way. I did the conversion on her old
> > computer,
> > > > > > and that went fine. Then I tried to substitute her new Dell
> Inspiron
> > > > > > laptop for the old desktop, and the Cox software kept insisting
> that
> > > > > > it couldn't detect a NIC. This in spite of the fact that all the
> > modem
> > > > > > lights were flashing, ipconfig showed a good IP address and
> gateway,
> > > > > > and the status box for her NIC (in Windows XP) showed a good bit
> of
> > > > > > data being sent and received. I never did the browser and email
> > > > > > working. Tried to call tech support and see if they needed to
> change
> > > > > > something, but no luck getting through. I'm also wondering
whether
> > the
> > > > > > surfboard modem she's renting from Cox is compatible with
Windows
> > XP.
> > > > > > It looks pretty old - you can't even read a model number on it.
> Any
> > > > > > suggestions would be appreciated, since getting through to Cox
> Tech
> > > > > > Support seems about impossible right now.
> > > > > >
> > > > > > "Martin J Piraino" <martinjp@cox.net> wrote in message
> > > > > news:<m_V48.3805$zR3.251588@news2.east.cox.net>...
> > > > > > > I wonder if your area had converted over to the new network
yet,
> > if
> > > > not
> > > > > then
> > > > > > > there wasn't a problem. Just  because you install the software
> > > doesn't
> > > > > mean
> > > > > > > your IP address will change immediately, mine didn't. I
wondered
> > the
> > > > > same
> > > > > > > thing after I installed the software and called to ask about
it,
> > > they
> > > > > told
> > > > > > > me that the migration to the cox.net backbone wouldn't take
> place
> > > till
> > > > > that
> > > > > > > friday night in my area. I'd recieved the conversion kit and
> > > installed
> > > > > it
> > > > > > > that monday. If you keep the settings the way you have them
now
> > you
> > > > may
> > > > > have
> > > > > > > problems in the future.  I'd just leave it to DHCP, and obtain
> IP
> > > > > address
> > > > > > > automatically and remove proxys from the web browser.  You
said
> > you
> > > > got
> > > > > a
> > > > > > > new IP address after converting, was it on the 68.XXX.XXX.XXX
or
> > > > > > > 24.XXX.XXX.XXX? I had problems where for about a day I kept
> > getting
> > > an
> > > > > IP
> > > > > > > address in the private IP range of 169.XXX.XXX.XXX or
> > 10.XXX.XXX.XXX
> > > > > which
> > > > > > > annoyed me because I was getting the DNS numbers for cox.net
> right
> > > but
> > > > > the
> > > > > > > IP refused to change to one where I would have a net
connection.
> I
> > > > > finally
> > > > > > > called them and they did something to fix it on their end
> because
> > > when
> > > > I
> > > > > > > rebooted it was again a 68.XXX.XXX.XXX address.. one that I've
> had
> > > > since
> > > > > > > that time.
> > > > > > >
> > > > > > >
> > > > > > > "Suellen" <Suellen_Stewart@msn.com> wrote in message
> > > > > > > news:bc5b60f8.0201170659.1fb61766@posting.google.com...
> > > > > > > > Lloyd,
> > > > > > > > I wonder if you can give me a clue as to what happened in
this
> > > case:
> > > > I
> > > > > > > > followed Cox's "migration" instructions, used the CD and
> loaded
> > > the
> > > > > > > > software. Once everything was working, I uninstalled all the
> Cox
> > > > > > > > software. The next time I rebooted there was no connection,
> and
> > > > > > > > ipconfig revealed that I was set back to my old @home ip
> > address.
> > > I
> > > > > > > > manually entered the new ip address and gateway (that I had
> > > received
> > > > > > > > after converting) in the "alternate" tab in tcp/ip
properties,
> > and
> > > > > > > > regained the connection. It's been good for about 12 hours
> now,
> > > but
> > > > > > > > I'm wondering how long this will last considering ip
addresses
> > are
> > > > > > > > supposed to expire every four hours with the Cox system. . .
> > > (using
> > > > > > > > Windows XP).
> > > > > > > > Thanks in advance for any info. you can provide!
> > > > > > > > Suellen
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>