How can I make one Comp Static, while the rest use DHCP

[DeadSeaSquirrels]

I have the Linksys 8-port router, and i would like to make one computer on my network a static IP so that I can try running a web server on it more reliably. I was wondering if it is possible to make one computer static and have the rest remain dynamic.

I remember doing it a long time ago, and, though my memory may be bad, I remember some things working and some things not. Like the LAN was working but the WAN wasn't or something like that.

Basically, can I just give my static IP computer any old static IP? And after I set that computer, how do I notify the router to recognize that? Thanks for the help.

 

[mboy]

Set the tcp/ip config on the PC to an ip in the same subnet as your DHCP scope. Remember, you will also need to set the gateway IP (LAN IP OF ROUTER) and also your DNS servers (look in your WAN config on the router for those or do an ipconfig /all on of you your DHCP'd PC's) in the IP settings on the PC.
The router should know that the IP has already been assigned as it will already be in it's routing table once you change it. A lot of routers enable you to hardcode an IP based on MAC Addy, but I do not believe the Linksys can. I wouldn't worry about it tho, it shouldn't try to give that IP to another PC on the LAN.

 

[gunrunnerjohn]

FWIW, most SOHO routers will allow you to configure a fixed IP address locked to a MAC address. This accomplishes what you desire without having to change any configuration on the clients. I have all of the full-time computers on my network configured that way, works just fine.

 

[DarkJuJu]

You should be able to setup a 1-to-1 nat (network address translation) or just do port forwarding on port 80 to the PC you want to host http

 

[skyking]

I have had routers "give away" a server IP if it is within the range of served IP's. FreeBSD had a cow, it was pretty funny.
Here is what I do:
I make the range of DHCP IP's 192.168.x.10 to .20 it is a rare home network that needs more than 10.
I use the .2 to .9 for servers, printservers, etc.
This way, there is not even a possibility of conflict, and it is easy <for me> to remember which server is where, with those single digit IP's.

 

[gunrunnerjohn]

Hell, I leave the DHCP pool at x.x.x.2 through x.x.x.100, and I still have 150 addresses to hand out for static assignments. FWIW, I'm up to x.x.x.14 for connected devices, so limiting myself to 8 or 9 simply wouldn't do. 😀

 

[skyking]

come on man, you have 14 DHCP Clients?
😛

 

[chsh1ca]

No, obviously 13 -- The router would use .1.

Static DHCP, while it may seem to defeat the purpose, is incredibly useful from an administration standpoint. This is especially true if you've ever had to reconfigure DNS entries on an all-static network of about 100 machines or more (no, not my design).

 

[skyking]

Originally posted by: chsh1ca
No, obviously 13 -- The router would use .1.

Static DHCP, while it may seem to defeat the purpose, is incredibly useful from an administration standpoint. This is especially true if you've ever had to reconfigure DNS entries on an all-static network of about 100 machines or more (no, not my design).

See the 😛?
I was joking with John.......

I agree, I use DHCP for all the workstations, but leave the servers all static. It is usually not that many to update, no more than three, and I like to find them in the same "place"

 

[gunrunnerjohn]

Oh, I agree 100% that servers should be configured truly static IP, I didn't see that we were discussing servers here, just a simple peer network. 🙂

As far as the 14 IP devices, there are 7 computers in the office/lab here, one in my wife's office, one in the kitchen, one in my daughter's room, a TiVo and an X-Box. I also have two laptops that get connected occasionally, and I've assigned them IP's based on the MAC address.

When I'm testing the networked factory automation systems I develop, I dig out three more old computers and lash them to the network to provide more "dummy loads" to keep the server busy. 😀