Article View: comp.dcom.modems.cable
Article #532Re: New cox cable managed network
From: PC Medic
Date: Wed, 13 Feb 2002 17:58
Date: Wed, 13 Feb 2002 17:58
173 lines
8209 bytes
8209 bytes
"Derek M. Loseke" <spamderek@cox.net> wrote in message news:MUZ98.7520$zb.402377@news1.east.cox.net... > 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 > Perhaps it has to do with your lack of knowledge with regards to MAC usage and DNS/NetBIOS names. > "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 > > > > > > > > > > > >
Technical Details
Message-ID:
<qPxa8.2968$SJ3.111454@news1.east.cox.net>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.uchicago.edu!yellow.newsread.com!bad-news.newsread.com!netaxs.com!newsread.com!newsfeeds-atl2!newsfeeds-atl1.usenetserver.com!cox.net!news1.east.cox.net.POSTED!53ab2750!not-for-mailReferences:
<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> <MUZ98.7520$zb.402377@news1.east.cox.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1136e3,710aa4d82544bdbb X-Google-Attributes: gid1136e3,public X-Google-Thread: 10f392,a7865c87070b0fcc X-Google-Attributes: gid10f392,public X-Google-Thread: 113850,a7865c87070b0fcc X-Google-Attributes: gid113850,public X-Google-ArrivalTime: 2002-02-13 09:58:49 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.uchicago.edu!yellow.newsread.com!bad-news.newsread.com!netaxs.com!newsread.com!newsfeeds-atl2!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> <MUZ98.7520$zb.402377@news1.east.cox.net> Subject: Re: New cox cable managed network Lines: 175 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: <qPxa8.2968$SJ3.111454@news1.east.cox.net> Date: Wed, 13 Feb 2002 17:58:46 GMT NNTP-Posting-Host: 68.10.144.175 X-Complaints-To: abuse@cox.net X-Trace: news1.east.cox.net 1013623126 68.10.144.175 (Wed, 13 Feb 2002 12:58:46 EST) NNTP-Posting-Date: Wed, 13 Feb 2002 12:58:46 EST Organization: Cox Communications