Date: Mon, 12 Jul 2004 11:55:38 -0500 From: "James A. Coulter" <james.coulter@cox.net> To: <freebsd-questions@freebsd.org> Cc: 'Roop Nanuwa' <roop.nanuwa@gmail.com> Subject: SOLVED: NEWBIE: Logging into Cox Cable service Message-ID: <000001c46831$0ef749b0$0300a8c0@sabrina> In-Reply-To: <8c98f4de04071200003a1ed9da@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
That's it Matt. Cycling the power on the modem did the trick. I guess =
the
modem itself is registered with the ISP - that's how they know if it's =
legit
or not.
Thanks to all who helped this newbie out!
Jim C.
On Mon 7/12/2004 2:01 AM Matt Haley wrote:
>I have Cox.net here. What seems to happen is that the cable modem
>itself latches on (so to speak) to the MAC address of the nic you're
>using. Usually, all that is required is to power cycle the cable modem
>and it should see the new nic and you'll be able to get your DHCP
>response.
>HTH.
>>On Sun, 11 Jul 2004 10:10:41 -0500, James A. Coulter
>><james.coulter@cox.net> wrote:
>> I am running FreeBSD 4.10 and am trying to connect to my Cox ISP via =
a an
>> Ethernet nic and cable modem.
>>=20
>> I have DHCP for the nic enabled in /etc/rc.conf and can obtain an IP
address
>> from my Windows 98 gateway, but when I connect the nic to the cable =
modem
>> and reboot I do not get a response from the cox DHCP server.
>>=20
>> The nic shows active in ifconfig, but no IP is assigned to it.
>>=20
>> I suspect the Cox DHCP server is expecting a username and password =
from
>> dhclient.conf
>>=20
>> I googled and the closest answer I found was a short article in the
FreeBSD
>> Diary published in 2000 that gave this as an example dhclient.conf:
>>=20
>> interface "de0" {
>> send host-name "cr123456-a";
>> request subnet-mask, broadcast-address, routers, domain-name-servers,
>> domain-name, time-servers;
>> require domain-name-servers;
>> }
>>=20
>> I tried substituting my own interface and looked up the hostname info =
cox
>> provided to my Windows 98 box and swapped the computer names, but no
luck.
>>=20
>> Is my hunch correct? When I set up my Windows boxes to connect to =
Cox
with
>> their CD, it always asked for the main account username and password =
=96 so
>> I'm guessing when the dhcp client sends out its request for an =
address,
the
>> Cox DHCP server is expecting a username and password.
>>=20
>> Can anyone tell me how to send the username and password?
>>=20
>> TIA,
>>=20
>> Jim C.
>>=20
=20
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.718 / Virus Database: 474 - Release Date: 7/9/2004
=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000001c46831$0ef749b0$0300a8c0>