DHCP & Static IP Address conflict?

[Pete Bucy]

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?

TIA - Pete

 

[Doug Sherman [MVP]]

Thsi is commonly done for various reasons and should not have any adverse
effects on your network. Adjust the DHCP scope on the router to exclude the
IP address you are going to statically assign. When you statically assign
an IP address, you must also assign the subnet mask, default gateway and DNS
server address.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Pete Bucy]

I did what you said, but I must have missed something because it
didn't work. I assigned a static IP to my pc,192.1681.1.200. with a
subnet mask of 255.255.255.0. I set the default gateway as:
192.168.1.1.

For the DNS server, I specified the routers address of 192.168.1.1.
The DNS server was set up to start at 192.168.1.100 and end at
192.168.1.115.

What did I miss?

Pete

 

[Doug Sherman [MVP]]

Does anything work? If the problem is just Internet browsing, try using
your ISP's DNS server address. Also, you may have to disconnect/reconnect
the power supply to the router or otherwise reset it if the statically
configured PC previously had an address lease.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Leythos]

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.

 

[Pete Bucy]

Thanks guys, its working now. I had screwed up the DNS server(s)
addresses the first time.

Pete

 

[phoenix]

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?

TIA - Pete

Yes, you can assign a static IP to some of the PCs on your LAN. Have a look
at the settings for your routers DHCP server, you should see a range of IP
addresses that it allocates - just allocate your static IP addresses
outside that range and you'll be OK.

HTH

Regards

Bill