[olug] Cox is demanding DHCP
Jeff Hinrichs
jlh at home.com
Fri Oct 19 04:30:18 UTC 2001
YMMV = Your Mileage May Vary
----- Original Message -----
From: "LP" <linuxposse at home.com>
To: <olug at bstc.net>
Sent: Thursday, October 18, 2001 11:25 PM
Subject: Re: [olug] Cox is demanding DHCP
> YMMV????
>
> At 10:43 PM 10/18/2001 -0500, you wrote:
> >I was forced to DHCP earlier this year. No way to fight it that I know.
It
> >hasn't been that big of a problem for me. YMMV.
> >
> >-Jeff
> >----- Original Message -----
> >From: "LP" <linuxposse at home.com>
> >To: <olug at bstc.net>
> >Sent: Thursday, October 18, 2001 10:36 PM
> >Subject: [olug] Cox is demanding DHCP
> >
> >
> > > Who else got this email and is there a way to fight this?
> > > I called and refused DHCP, but was pretty much told to "Go f#$%
myself".
> > > DSL isn't a option at this time.
> > >
> > >
> > > Dear Cox @Home customer,
> > > Our number one priority is to ensure that all of our Cox @Home
customers
> > > enjoy fast, reliable high-speed Internet service. To help us deliver
on
> >this
> > > goal, the Cox @Home Network Team is performing network maintenance in
your
> > > area, which includes balancing network traffic needs and consolidating
IP
> > > address space.
> > > Your computer has been identified as not using the DHCP protocol, a
system
> > > designed to automatically update your Internet address information. To
> > > ensure optimum network performance for all of our Cox @Home customers,
it
> >is
> > > important that everyone use DHCP protocol to connect to the Internet.
> >Below
> > > you will find several options to help you convert your computer from a
> >static
> > > connection to a dynamic connection (DHCP protocol). Please make the
> > > necessary changes (as outlined below) to all computers connected to
your
> >Cox
> > > @Home service. After any network maintenance, any computers not using
the
> > > DHCP protocol will not be able to connect to the Internet. The options
> >below
> > > will guide you through these changes. You will receive this e-mail for
> >each
> > > and every IP/DNS name that is assigned to you but not using DHCP.
> > > Your Computer Name (DNS) is: CX383423-G
> > > OPTION 1:
> > > If you would like to take advantage of an automated tool, please visit
> > > http://dhcpconv.home.net/. Before visiting this tool, please print out
the
> > > instructions in this document to assist you if you have any questions.
> > > OPTION 2:
> > > For instructions on configuring your computer, please choose the
> > > corresponding link for your operating system. Before visiting these
links,
> > > please print out the instructions in this document to assist you if
you
> >have
> > > any questions.
> > > Instructions for Windows 95/98/ME:
> > > http://www.cox.com/service/CoxatHome/DOCSIS_W9x_DHCP.asp
> > > Before beginning, ensure you have your Windows 95/98/ME installation
CD or
> > > Diskettes.
> > > Step 1. Click on Start, then click Settings
> > > Step 2. Click Control Panel
> > > Step 3. Double-click Network
> > > Step 4. In Network, click Identification
> > > Step 5. Verify that you have the correct computer name (above) in
Computer
> > > Name
> > > Step 6. Click the Configuration tab
> > > Step 7. Select TCP/IP for the network card
> > > Step 8. Click Properties
> > > Step 9. In the IP Address tab, make sure that "Obtain an IP Address
> > > Automatically" is selected
> > > Step 10. Click WINS Configuration, select Disable WINS Resolution
> > > Step 11. Click the Gateway tab
> > > Step 12. Remove any numbers in Installed Gateway
> > > Step 13. Select the DNS Configuration tab
> > > Step 14. Select Disable DNS
> > > Step 15. Click OK on TCP/IP Properties
> > > Step 16. Click OK on Network
> > > Step 17. Your WIN95/98/ME CD or Diskettes may be required
> > > Step 18. Reboot your computer when prompted.
> > > Instructions for Windows NT:
> > > http://www.cox.com/service/CoxatHome/DOCSIS_WinNT_DHCP.asp
> > > Step 1. Go to Start
> > > Step 2. Click Settings
> > > Step 3. Click Control Panel
> > > Step 4. Double-click Network
> > > Step 5. In Identification, make sure your Computer Name (above) is in
the
> > > Computer Name field. If not, click Change and type in your Computer
Name
> > > (above)
> > > Step 6. Click Protocols
> > > Step 7. Highlight TCP/IP for your Network card
> > > Step 8. Click Properties
> > > Step 9. Select Obtain an IP address from a DHCP Server
> > > Step 10. Click the DNS tab
> > > Step 11. Make sure your Host Name is your Computer Name (above)
> > > Step 12. Click WINS Address
> > > Step 13. Deselect Enable DNS for Windows Resolution, if selected
> > > Step 14. Click OK for TCP/IP Properties
> > > Step 15. Click OK on Network
> > > Step 16. Restart your computer
> > > Instructions for Macintosh:
> > > http://www.cox.com/service/CoxatHome/Setup_MacTCP_OS85.asp
> > > Some Macintosh operating systems (OS 8.5 & below) do not allow for
DHCP
> > > usage. The instructions below are for Macintosh version 8.5.1 and
above.
> > > Step 1. Open the TCP/IP Control Panel. Click on the Apple Menu, move
down
> >to
> > > Control Panels and select TCP/IP.
> > > Step 2. Click on the Edit Menu and select User Mode.
> > > Step 3. Ensure that Advanced is selected and click the OK button.
> > > Step 4. From the Connect Via Menu, select Ethernet. Other valid
options
> >may
> > > be Ethernet Built-in, Alternate Ethernet, Ethernet Slot A1, etc.
> > > Step 5. Select "Using DHCP Server" from the Configure menu. Type the
> > > Computer Name (above) in the "DHCP Client ID" field
> > > Step 6. Click the Options button to bring up the TCP/IP Options
window.
> > > Step 7. Ensure Active is selected and Load Only When Needed is
unchecked,
> > > then click the OK button.
> > > Step 8. Close the TCP/IP control panel by clicking the Close box in
the
> >upper
> > > left corner of the window. When the Save dialog appears, click the
Save
> >button.
> > > Thank you for your cooperation with this conversion. If you have any
> > > questions or concerns, please feel free to email us at
dhcpnotify at cox.com.
> > > As always, thank you for being a valued Cox @Home customer.
> > > Network Management Team
> > > Cox @Home
> > >
> > >
> >
> >
> >-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> >
> >For help contact olug-help at bstc.net - run by ezmlm
> >to unsubscribe, send mail to olug-unsubscribe at bstc.net
> >or `mail olug-unsubscribe at bstc.net < /dev/null`
> >(c)2001 OLUG http://www.olug.org
> >
> >-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
>
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
For help contact olug-help at bstc.net - run by ezmlm
to unsubscribe, send mail to olug-unsubscribe at bstc.net
or `mail olug-unsubscribe at bstc.net < /dev/null`
(c)2001 OLUG http://www.olug.org
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
More information about the OLUG
mailing list