From owner-freebsd-questions@FreeBSD.ORG Mon Jul 12 16:55:43 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35B1416A4CE for ; Mon, 12 Jul 2004 16:55:43 +0000 (GMT) Received: from lakermmtao01.cox.net (lakermmtao01.cox.net [68.230.240.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6D9F43D1F for ; Mon, 12 Jul 2004 16:55:42 +0000 (GMT) (envelope-from james.coulter@cox.net) Received: from sabrina ([68.1.41.123]) by lakermmtao01.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040712165542.NRPE29186.lakermmtao01.cox.net@sabrina>; Mon, 12 Jul 2004 12:55:42 -0400 From: "James A. Coulter" To: Date: Mon, 12 Jul 2004 11:55:38 -0500 Message-ID: <000001c46831$0ef749b0$0300a8c0@sabrina> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <8c98f4de04071200003a1ed9da@mail.gmail.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: 'Eric Crist' cc: 'Matt H' cc: 'Roop Nanuwa' Subject: SOLVED: NEWBIE: Logging into Cox Cable service X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2004 16:55:43 -0000 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 >> 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