DHCP or Static IPs?

[woody]

We have manually assigned Static IP addresses for a while now. Of course, changing to DHCP would make things a little easier, but would we have the same amount of control over our network?

[CyberNerd]

get dhcp to issue static IP's. Best of both worlds.

[webman]

DHCP for all workstations but with exclusion ranges and static reservations for switches, access points and printers etc.

[sidewinder]

With over 700 machines, not using DHCP would be a nightmare if not impossible

 

Use statics for servers, printers and IT staff. Statics also for access points and switches but in a totally different IP range

[tom_newton]

mainly statics over dhcp. Some dynamic. But then I have less users than most of you guys, but as some are sales people, their mental ages are lower

[Ric_]

DHCP gives you the flexibility to change scopes as and when you need. I then favour using reservations for printers so that I know where they will be and then static IPs for switches because ifI am messing with the switches they might not have a route to the DHCP server.

[john]

I do the Ric method, DHCP but give Printers, Copiers, Scanners etc a Reserved DHCP address and switches, APs etc a fixed Static in them.

[ajbritton]

Same as Ric, John. If think it roughly breaks down to client type stuff (workstations) on DHCP and server type stuff (servers, printers, switches etc) on static.

[StewartKnight]

Go for DHCP Mark, it's a heck of a lot easier in the long run, I bet you don't really need to know the static IP address of a computer that often anyway, and Securus tells you the name of the computer and it's IP address when someone "offends"

[dezt]

We have had static ip's in place since I started here. The main reason this is implemented here is because of a proxy server tat is running that works on allowing or denying internet access to computers by their ip address.

 

The software is qbik wingate proxy and is really good for disabling half a classroom from using the internet while the other half of the room are surfing away.

[SpuffMonkey]

Go for DHCP Mark, it's a heck of a lot easier in the long run, I bet you don't really need to know the static IP address of a computer that often anyway, and Securus tells you the name of the computer and it's IP address when someone "offends"

 

Funny that - coz I reckon the opposite - statics (or reservations) are easier long term - DHCP is good for a quick fix.

[SpuffMonkey]

Go for DHCP Mark, it's a heck of a lot easier in the long run, I bet you don't really need to know the static IP address of a computer that often anyway, and Securus tells you the name of the computer and it's IP address when someone "offends"

 

Funny that - coz I reckon the opposite - statics (or reservations) are easier long term - DHCP is good for a quick fix.

[GrumbleDook]

Static for servers, switches, printers and a few other specific machines ... but most are done via reservations on DHCP.

[Norphy]

Static IPs for every PC, thin client, PDA, printer server, server, wireless access point and managed switch in the school? Unless you only have six machines or something, you'd have to be a real sadist

 

DNS names are far easier to remember than IP addresses. DHCP does a fairly good job of keeping the DNS up to date. Unless it is something that absolutely requires a static IP (server, access point, whatever), clients get their IP addresses to DHCP