[180] in winnt
Re: Local DHCP Server?
daemon@ATHENA.MIT.EDU (Bob Kaynor)
Wed Jul 1 13:36:48 1998
Date: Wed, 01 Jul 1998 13:35:32 -0400
To: Jonathan McIndoe Hunt <jmhunt@MIT.EDU>
From: Bob Kaynor <bkaynor@MIT.EDU>
Cc: ntpartners@MIT.EDU, IT-Partners <itpartners@MIT.EDU>
In-Reply-To: <3.0.2.32.19980701131114.0093faa0@hesiod>
Jonathan: Thank you, this is very helpful. The problem from my standpoint
as a user/dept manager is that IP addresses cost me $20 per month out of my
computing budget. If I have four or five machines which need Internet
access only occasionally, that's a big difference to me over the course of
a year (though a trivial sum from a NetOps persepctive).
The current system makes sense from a central management view of the world
- which I can appreciate it as a user - but it doesn't really respond my
concern. Given the lack of flexibility in NT's implementation of DHCP, do
you have any other advice? Perhaps I/S could make central DHCP services
available for on-campus use as they are for Tether? I would be willing to
pay a more modest monthly fee for access up to, say, 80-100 hrs per month
from certain machines (instead of the unlimited access I get currently with
a private IP address).
This probably sounds like a PITA from a central management perspective, but
I think you would find a lot of support in the user community for a more
responsive on-demand system which helped reduce end-user costs in certain
cases. Cheers.
-RKK
At 01:11 PM 7/1/98 -0400, Jonathan McIndoe Hunt wrote:
>Hi Bob,
>
>I just spoke to Network Operations and you should NOT setup a local DHCP
>server. If you really need to use a private DHCP server, then I can assist
>facilitating a contract for a private network.
>
>From Network Operations:
>We expect all hosts on MIT.net which require IP
>services to have assigned addresses.
>
>In addition, our model for DHCP service for registered
>users requires MIT's main servers to respond to all
>DHCP queries on public networks (which B12 is). This
>would mean they'd have to contract for a private network
>to run their own DHCP service as we already provide
>DHCP for the B12 network.
>End of information from Network Operations.
>
>The MIT DHCP servers will at least a portion of the time beat out any local
>DHCP server that is setup on the subnet. In this case, if these machines
>are not registered for MIT's DHCP, they will not work on the network and
>will require a restart. DHCP does not allow for a specific DHCP server to
>be specified, so it is random chance of which server responds first and how
>many times the machines will need to be restarted.
>
>I would recommend that a specific IP is assigned for each of these machines
>so that they can work on the network.
>
>Thanks,
>Jonathan Hunt
>
>At 11:38 AM 7/1/98 -0400, you wrote:
>>Any tips for implementing a local DHCP server in our (dept) domain? We
>>have a few stations which need IP services only on occasion and I'd like to
>>have them share address resources.
>>
>>-RKK
>>
>____________________________________
>Jonathan M. Hunt
>Departmental Computing Support
>E40-335 x3-0172
>http://web/is/dept-comp/
>
