Re: DHCP & Static IP Address conflict?
From: Leythos (void_at_nowhere.lan)
Date: 01/22/05
- Next message: howduck: "Re: Can you make a windows 2000 server a bridge...?"
- Previous message: Doug Sherman [MVP]: "Re: DHCP & Static IP Address conflict?"
- In reply to: Pete Bucy: "DHCP & Static IP Address conflict?"
- Next in thread: Pete Bucy: "Re: DHCP & Static IP Address conflict?"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 22 Jan 2005 22:59:57 GMT
In article <9fo4v0ts7f7k7fs9iuf62nbb10ge643ac9@4ax.com>,
petebucy@charter.net says...
> I have a small home network that connects six computers and allows
> them all to access the net via a cable modem. Four of the machines
> connect through a Linksys BEFSX41 router (and a switch). The other two
> machines connect to the router through a Linksys WAP54G wireless
> access point.
>
> The network works great. The only issue is that the IP address that
> are assigned by the router through DHCP to each computer change from
> time to time as computers are turned off and on.
>
> This means that I often have to reconfigure the router to send the
> results its log to different IP addresses so that I can monitor the
> log on "Wall-Watcher" on my PC.
>
> Can I assign a static IP to my main computer and let the router DHCP
> server assign the IP addresses to the other computers on the network?
>
> The WAP54G wireless access point has a static IP address of
> 192.168.1.245 and it works flawlessly. Will assigning a static IP
> address to my PC cause any problems with the network?
If you set it up properly WallWatcher will show the NAME of the computer
in addition to the IP Address.
As for setting fixed IP addresses, that's easy.
On computer 1 - your wall watcher computer, while it's still getting an
IP Address via DHCP, open a CMD window and type IPCONFIG /ALL. This will
give you the following important items:
IP Address - we don't really need this
Subnet Mask - use for Every Computer.
Default Gateway - use for Every Computer.
DNS 1 - Use for Every Computer
DNS 2 - Use for Every Computer
Now, the internal Linksys DHCP server is setup to start at 192.168.1.100
and end at 150, so we want to stay out of this range.
Make computer 1 (wall watcher)
IP Address 192.168.1.40
and use the above info for the rest of the config
Make computer 2
IP Address 192.168.1.200
and use the above info for the rest of the config
Make computer 3
IP Address 192.168.1.201
and use the above info for the rest of the config
Make computer 4
IP Address 192.168.1.202
and use the above info for the rest of the config
The reason for the jump from .40 to .200 is that your computer, the one
you trust and running WW, should be easy to single out in the logs since
it will have less digits than the others.
For the wireless connections, you do the same config, do not use the
.245 as their gateway.
So, as long as it was working before moving to fixed IP's, it will work
now.
-- -- spamfree999@rrohio.com (Remove 999 to reply to me)
- Next message: howduck: "Re: Can you make a windows 2000 server a bridge...?"
- Previous message: Doug Sherman [MVP]: "Re: DHCP & Static IP Address conflict?"
- In reply to: Pete Bucy: "DHCP & Static IP Address conflict?"
- Next in thread: Pete Bucy: "Re: DHCP & Static IP Address conflict?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
