Re: New cox cable managed network

Article View: comp.dcom.modems.cable

Article #524

Back to comp.dcom.modems.cable Previous Next

#524

From: Arthur Hagen
Date: Fri, 01 Feb 2002 21:37

29 lines
2924 bytes

"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.

NetBIOS name and DNS name are two different things.  They used the FQDN
(Fully Qualified Domain Name) assigned to your network card, which I guess
is what you call the DNS name (they don't have to be the same, though).  The
NetBIOS name is a Windows/Novell invention that has nothing to do with real
Internet.
On some Windows versions under default setup, the netbios name is the same
as the hostname and the same as the interface name, but not on all.
My machine had a NetBIOS name of "KETHER", a hostname of "flying", and a
FQDN for the ethernet interface set to cxNNNNNN-N.mnchs1.ct.home.com, and
Cox@home used the latter.
They would never see the NetBIOS name (they even block the port that would
allow them to do so).

> Also, the software doesn't detect all NIC's.

It shouldn't have to - in fact, that's a very backwards way of finding out
things.  Check the list of network adapters instead, and their capabilities,
without even checking what card it is.  If it handles ethernet and ms_tcpip,
there you go.

Regards,
--
*Art

Technical Details

Message-ID: <5UD68.6187$Xk4.343155@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>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 113850,a7865c87070b0fcc
X-Google-Attributes: gid113850,public
X-Google-Thread: 1136e3,710aa4d82544bdbb
X-Google-Attributes: gid1136e3,public
X-Google-Thread: 10f392,a7865c87070b0fcc
X-Google-Attributes: gid10f392,public
X-Google-ArrivalTime: 2002-02-01 13:37:08 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: "Arthur Hagen" <art@broomstick.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>
Subject: Re: New cox cable managed network
Lines: 31
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: <5UD68.6187$Xk4.343155@news1.east.cox.net>
Date: Fri, 01 Feb 2002 21:37:05 GMT
NNTP-Posting-Host: 24.2.187.86
X-Complaints-To: abuse@cox.net
X-Trace: news1.east.cox.net 1012599425 24.2.187.86 (Fri, 01 Feb 2002 16:37:05 EST)
NNTP-Posting-Date: Fri, 01 Feb 2002 16:37:05 EST
Organization: Cox Communications

Reply to Parent Message