Kurt,
For remote offices, we have always made sure that we have 2 DC's both with
DHCP, although only if they are in a secure location with restricted physical
access, we have done this mainly for redundancy, we have looked at running DHCP
from a centralised location, but even in this day and
Nobody from IT has been to this overseas office in my 8 years at this
company. We've shipped servers and this admin has set them in the rack
and hooked them up.
By now, the political situation has gotten to be such that it would be
thoroughly resented if I went to correct things, such as locking
Do you really want someone to control what and where the clients look to for
information? Do you trust this person to keep their hands off of the
network? If you say yes leave them be if you don't or if this person just
is one to the type that all things Linux is good and all things Microsoft is
There is no intrinsic reason for DHCP to be based on Windows.
There are some easy of admin features that I think are nice - such as when
you build the subnet the wizard prompts you for the site-aware DNS and WINS
server and the automatic DNS and rDNS registrations.
But any modern (i.e., the
+1.
Kind of makes me sad the guy thinks he admining DHCP. I mean really,
how often do you touch it?
I would just say that if you have a corp standard, follow it. Be it
Windows or any other flavor. Pick one and standardize (which you have
done). That's a hard argument for someone when 90% of the
He didn't reboot the DC, he rebooted the firewall - in spite of the
fact that I asked him to call our on-call extension here in the
States, which generates a page to the on-call cell phone.
I'm not sure of his stance on MSFT vs. Linux, except that he
definitely prefers the latter.
Still, you
On Sun, Feb 21, 2010 at 13:11, Michael B. Smith mich...@smithcons.com wrote:
There is no intrinsic reason for DHCP to be based on Windows.
No technical reason then. As I suspected.
There are some easy of admin features that I think are nice - such as when
you
build the subnet the wizard
2010 13:48:05
To: NT System Admin Issuesntsysadmin@lyris.sunbelt-software.com
Subject: Re: DHCP in Win2k3 R2 domain
He didn't reboot the DC, he rebooted the firewall - in spite of the
fact that I asked him to call our on-call extension here in the
States, which generates a page to the on-call
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
Buff [mailto:kurt.b...@gmail.com]
Sent: Monday, 22 February 2010 7:57 AM
To: NT System Admin Issues
Subject: Re: DHCP in Win2k3 R2 domain
On Sun, Feb 21, 2010 at 13:11, Michael B. Smith mich...@smithcons.com wrote:
There is no intrinsic reason for DHCP to be based on Windows.
No technical
Message-
From: Kurt Buff [mailto:kurt.b...@gmail.com]
Sent: Sunday, February 21, 2010 3:57 PM
To: NT System Admin Issues
Subject: Re: DHCP in Win2k3 R2 domain
On Sun, Feb 21, 2010 at 13:11, Michael B. Smith mich...@smithcons.com
wrote:
There is no intrinsic reason for DHCP to be based
On Sun, Feb 21, 2010 at 13:22, Martin Blackstone mblackst...@gmail.com wrote:
+1.
Kind of makes me sad the guy thinks he admining DHCP. I mean really,
how often do you touch it?
I would just say that if you have a corp standard, follow it. Be it
Windows or any other flavor. Pick one and
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
Admin Issues
Subject: Re: DHCP in Win2k3 R2 domain
On Sun, Feb 21, 2010 at 13:11, Michael B. Smith mich...@smithcons.com
wrote:
There is no intrinsic reason for DHCP to be based on Windows.
No technical reason then. As I suspected.
There are some easy of admin features that I think
To: NT System Admin Issues
Subject: Re: DHCP in Win2k3 R2 domain
Yes, but it seems a bit shortsighted in the face I what I've had to deal with
-
on at least two occasions I've had people drag personal (linksys, dlink)
firewalls/routers into work because they needed
them, and really screwed
, February 21, 2010 3:57 PM
To: NT System Admin Issues
Subject: Re: DHCP in Win2k3 R2 domain
On Sun, Feb 21, 2010 at 13:11, Michael B. Smith
mich...@smithcons.com
wrote:
There is no intrinsic reason for DHCP to be based on Windows.
No technical reason then. As I suspected
16 matches
Mail list logo
