static IP environment

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

HI all,
Please advise me on managing and maintaining Static ip network. We have around 120 desktops and laptops , the biggest issue we are facing is with the Static IP. If i move to DHCP with ISA will there be any problem?...please advise.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

DHCP will ease your management of your clients a lot. You only need assign static IPs to your servers.

 

As long as a NAT firewall is used shouldn't be a problem along with making sure the addresses fall withing the network mask.

 

There isn't enough information to go on here.

Why are you using static IP addressing now? There may be perfectly valid reasons for it (an application requires it, or licensing reasons for instance). The police force I worked for required all machines to have a static address for accountability purposes.

Do you have multiple internal subnets? If so, then do you know how to route dhcp traffic across them?

Exactly what 'issues' are you facing with static addressing? Provided your netmask provides enough space, and the majority of clients are already staticly assigned, you've got no administrative burden other than keeping track of what's already been assigned, and recording when addresses get retired. In addition, since you dont have any dhcp servers, route already a little more secure than most networks.

Of course, all this is assuming your clients sit on an internal (non publicly routable) address range. If they don't, then you've got a whole network redesign to do - and putting in a dhcp server is the least of your worries.

Don't be too quick to dismiss static addressing. It gives you a lot more control over your environment. The paranoid amongst us (me!) likes that!

 

the problem is we dont have the database of ips being used. is there anyway of pulling it out?

 

Use a network scanner to probe the address range.

 

i use ip angry to pull out the address , but we are working in shift basis so no follow up

 

err why don't you document what you do and get the other people to document what they do?

it aint rocket science.

 

If you need to keep some static addresses but also want to use DHCP be sure that the range your DHCP uses does not overlap any static addresses or you could get complaints....