Sounds logical, but when I try it, the affected computer can no longer
connect over the Internet. I switche back to DHCP, and everything works
again.
I'm using a Siemens SpeedStream 2624 router, for what it's worth. Works
fine, ordinarily. I went into the setup screen and told it to limit
DHCP to 192.168.254.100 through 200. Then I set a machine to
192.168.254.2. It didn't work. My network connection was gone. I
wonder what went wrong...any ideas? Thanks.
Should be easy enough - just assign static IP addresses to the PCs that
are always on the network that are outside the range the DHCP server
provides, then let "visitors" pick up an IP address from the router.
For example, my Linksys wireless router is set up to assign IP
addresses in the range 192.168.1.101 through 192.168.1.200 - so any
static assignments I make are in the range of 192.168.1.2 through
192.168.1.100, that way there are no conflicts between the static and
dynamic addresses.
--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ...
http://rgharper.mvps.org/
* HELP us help YOU ...
http://www.dts-l.org/goodpost.htm
I have several computers at home connected to a network. My DSL router
uses DHCP to assign each machine an IP address. But if I shut off the
router or the computers, they often get assigned new IP addresses,
which messes up my network mapping.
Would it make more sense for me to assign static IPs on the internal
192.168 subnet to each machine? Is there a way to do that, and still
use DHCP to set up any visiting computers that come along?
Thanks!