We have two overseas offices. The one under discussion is an exception. I was wondering what was being hidden as well, but at this point there's not enough smoke. He's fought me on a lot of issues. I'm gradually winning. :)
On Sun, Feb 21, 2010 at 14:20, James Hill <james.h...@superamart.com.au> wrote: > Is this office an exception? Or do you have other offices that also have > linux dhcp servers? > > Are there other techs that may need to remotely manage this site? Do they > have the access/skills/knowledge to work with a linux dhcp server? Do they > know to even look for it or are they expecting windows dhcp? > > To me there are a two main issues here:- > > Possible lack of standardisation > An Admin that wants to control something for no real reason. There is smoke > here in my opinion. What's he hiding? > > Technical solutions(which may or not be possible) is to take control at the > network level. Block dhcp broadcasts on the switch for the relevant ports > (67,68 from memory) for the linux dhcp server. If there are other subnets > involved set your ip helper configuration to forward requests to the windows > dhcp server. > > But really this guy needs to understand the benefits of standardisation. > Unless he can provide an outstanding benefit of running the dhcp server on > linux then it makes no sense to have an exception from the norm. > > > > -----Original Message----- > From: Kurt Buff [mailto:kurt.b...@gmail.com] > Sent: Monday, 22 February 2010 4:34 AM > To: NT System Admin Issues > Subject: DHCP in Win2k3 R2 domain > > All, > > Actually, the issue isn't really that, it's the part time admin in one > of our overseas offices. He's running DHCP on a linux box, and handing > out DNS/WINS entries pointing to the AD servers. > > I've got DHCP set up on the DC in their office, but haven't turned it on yet. > > He's balking because he want to control the handing out of addresses > in his environment. Yes, I've taken away a large portion of his former > set of control, but he can set up new users (including their > mailboxes, etc.) and workstations, and he is an admin on the file > server and the ERP box in their office, but little else - he doesn't > have access to the DC with WINS/DNS, nor the firewall (though he has > pulled the plug on it when "it wasn't working right", without calling > me, which really pissed me off.) > > I could just turn on DHCP on the DC, and let those two machines fight > it out, with the resulting chaos that would ensue, but I don't think > that's terribly smart. > > I could just use the management hammer and tell him to turn the linux > service off "because I said so" but that seems less than optimal as > well. > > The servers are set up with static addresses, so that bit is not an issue. > > Can anyone point me to KB articles or other documentation on running > DHCP that bolsters the case for centralizing it with AD? > > OTOH, if there's no compelling reason for doing so, I'd like to hear > that as well, though I think that having network infrastructure > services served out of the same platform, and manageable by the HQ > would be a good thing. > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
