🚀 go-pugleaf

Actually, I believe you may be correct.  I think all the modems, when
inventoried, have the MAC and corresponding Serial Number entered into the
Cox system.  When a dispatcher provisions a modem, it is done so with the
serial number on the majority of modems.  However, it wouldn't suprise me if
that serial number isn't linked to a database the finds the Serial number
and corresponding MAC, and is provisioned that way.  For the user interface,
the Serial number is used, but the MAC my be used on the machine level.

Derek


"Brian" <bswindle@charter.net> wrote in message
news:3C68ACEB.D7846525@charter.net...
>    The MAC address is what the modem is provisioned by, not the serial
number.
> The server never sees any indication of a modem's serial number at any
time.
> Serial numbers may be recorded on work orders, but I would imagine they
are tied
> back to the MAC when put on an account.
>
> "Derek M. Loseke" wrote:
>
> > They didn't use the MAC address, except on certain modems.  This doesn't
> > include Motorola and Toshiba.  They instead use the serial number.
> >
> > Why do you question the "Cox Contractor" part?  I am a contractor for
Cox.
> >
> > Derek
> >
> > "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???????
> > >
> > >
> > > "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
> > > >
> > > >
> > >
> > >
>