File Server and DHCP

arrived @ new job. Org is using acive directory Domain controller @ another
location but have file server @ my location. The file server is using DHCP
and I have never seen enterprise system w/file servers on DHCP. Looking for
infor to convince everyone here to add static ip along w/ the other needed
info that goes with a static IP

By "using DHCP" you mean that it's getting it's IP address from a DHCP
server? Correct?

Are you sure there isn't a reservation defined in a scope on the DHCP
server, for that file server? If so, that is good.
If there isn't, you probably already know the biggest reasons for using
static IP on that server. Reliability and consistency. If for some reason
there's a problem with a company DNS server, you could still get to that
file server by IP address. Or I should say, the users can get to it. You
already know that, they don't. Redundancy is good for everyone :-)



"sowbug" <(E-Mail Removed)> wrote in message
news:789DF372-D8EA-4EE8-A1DD-(E-Mail Removed)...
> arrived @ new job. Org is using acive directory Domain controller @
> another
> location but have file server @ my location. The file server is using DHCP
> and I have never seen enterprise system w/file servers on DHCP. Looking
> for
> infor to convince everyone here to add static ip along w/ the other needed
> info that goes with a static IP
>

stability and consistency. It is without a doubt best practice and generally
taken as gospel that file servers have static ip addresses, a reservation in
dhcp is just as good though usually used for printers in my experience as an
easy way to change multiple ip's from the same location if necessary.
James.
--
James Yeomans, BSc, MCSE
Ask me directly at: http://www.justaskjames.co.uk


"sowbug" wrote:

> arrived @ new job. Org is using acive directory Domain controller @ another
> location but have file server @ my location. The file server is using DHCP
> and I have never seen enterprise system w/file servers on DHCP. Looking for
> infor to convince everyone here to add static ip along w/ the other needed
> info that goes with a static IP
>

After configuring w/static IP, would some configuration be needed on the DNS
server?

"JohnB" wrote:

> By "using DHCP" you mean that it's getting it's IP address from a DHCP
> server? Correct?
>
> Are you sure there isn't a reservation defined in a scope on the DHCP
> server, for that file server? If so, that is good.
> If there isn't, you probably already know the biggest reasons for using
> static IP on that server. Reliability and consistency. If for some reason
> there's a problem with a company DNS server, you could still get to that
> file server by IP address. Or I should say, the users can get to it. You
> already know that, they don't. Redundancy is good for everyone :-)
>
>
>
> "sowbug" <(E-Mail Removed)> wrote in message
> news:789DF372-D8EA-4EE8-A1DD-(E-Mail Removed)...
> > arrived @ new job. Org is using acive directory Domain controller @
> > another
> > location but have file server @ my location. The file server is using DHCP
> > and I have never seen enterprise system w/file servers on DHCP. Looking
> > for
> > infor to convince everyone here to add static ip along w/ the other needed
> > info that goes with a static IP
> >
>
>
>

You would have to check DNS to see if it registers automatically, which it
should. If not you could try to force it from the file server like so:
ipconfig /registerdns

And if it still doesn't show up you could go to the DNS server and create a
Host (A) record for that IP address.

But I would make sure there's no reservation on the DHCP server first. And,
when you do change it to static, I'd do it after hours.



"sowbug" <(E-Mail Removed)> wrote in message
news:856D4C10-6751-41F9-9A92-(E-Mail Removed)...
> After configuring w/static IP, would some configuration be needed on the
> DNS
> server?
>
> "JohnB" wrote:
>
>> By "using DHCP" you mean that it's getting it's IP address from a DHCP
>> server? Correct?
>>
>> Are you sure there isn't a reservation defined in a scope on the DHCP
>> server, for that file server? If so, that is good.
>> If there isn't, you probably already know the biggest reasons for using
>> static IP on that server. Reliability and consistency. If for some
>> reason
>> there's a problem with a company DNS server, you could still get to that
>> file server by IP address. Or I should say, the users can get to it.
>> You
>> already know that, they don't. Redundancy is good for everyone :-)
>>
>>
>>
>> "sowbug" <(E-Mail Removed)> wrote in message
>> news:789DF372-D8EA-4EE8-A1DD-(E-Mail Removed)...
>> > arrived @ new job. Org is using acive directory Domain controller @
>> > another
>> > location but have file server @ my location. The file server is using
>> > DHCP
>> > and I have never seen enterprise system w/file servers on DHCP. Looking
>> > for
>> > infor to convince everyone here to add static ip along w/ the other
>> > needed
>> > info that goes with a static IP
>> >
>>
>>
>>

exclude the number from dchp server range
jk

Bill Kearney <(E-Mail Removed)> wrote:
> "sowbug" <(E-Mail Removed)> wrote in message
> news:789DF372-D8EA-4EE8-A1DD-(E-Mail Removed)...
>> arrived @ new job. Org is using acive directory Domain controller @
>> another
>> location but have file server @ my location. The file server is
>> using DHCP and I have never seen enterprise system w/file servers on
>> DHCP. Looking for
>> infor to convince everyone here to add static ip along w/ the other
>> needed info that goes with a static IP
>
> For 'fixed' resource like a file server and the domain controlers it's
> generally a best practice to give them static addresses. Everything
> else can be effectively satisfied using DHCP and lease reservations. There
> may eventually be some devices that balk at properly using
> DHCP. But those devices are becoming few and far between these days.
> Better to start by using DHCP for everything but the servers FIRST
> and only convert to static because of known bugs. That way if/when
> you need to rearrange IP addressing you won't have to go out and
> touch all the devices manually (or through some scripting nonsense).
>
> -Bill Kearney

I agree. I don't give DHCP reservations to servers. If the DHCP server is
unavailable (or a rogue DHCP server is up) when the server boots up, you're
s__d. I use reservations for printers and workstations that require
non-changing addresses - I use statics for network equipment & servers.