Subject: | |
From: | |
Reply To: | |
Date: | Wed, 7 Sep 2005 08:16:52 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
The 169.254.x.x address range is used by machines that are set up to
receive an address assignment via DHCP, but are not getting any response
from a DHCP server. It's possible to run a single local segment this way,
but for the work you'd have to do to have any hope of talking to the router
(and the world beyond), you might as well enable the DHCP server
functionality of the router (probably enabled by default...) and do things
properly.
The router will probably default to using a block within the private range
at 192.168.x.x, and that will work fine. (There are a couple of other
private ranges, but they're intended for much larger networks.)
David Gillett
On 6 Sep 2005 at 11:17, Tony M. wrote:
> The problem is that you can't share the cable modem itself. You need
> to invest in a router. That will basically set up a small network
> inside your home (with the 169.x.x.x addresses most likely) but the
> "gateway" setting will be the router. Then, the router will connect
> to the cable modem and be the only device that the cable modem "sees"
> directly attached.
> Routers are cheap - and relatively simple to set up.
>
> Tony Mayer
>
>
>
>
> >My win98 system keeps coming up with a 169.x.x.x address and
> >does not seem to see the cable modem even though all the
> >lights on the hub are lighting properly. I have tried the
> >following commands:
> >Ipconfig /release
> >Ipconfig /renew
> >
> >Do you have any further guidance?
> >
> >Thanks,
> >Bruce Foss
>
> PCBUILD's List Owners:
> Bob Wright<[log in to unmask]>
> Drew Dunn<[log in to unmask]>
Do you want to signoff PCBUILD or just change to
Digest mode - visit our web site:
http://freepctech.com/pcbuild.shtml
|
|
|