Solved

Active Directory to NT cross domain DHCP authentication...?

Posted on 2009-04-14
2
481 Views
Last Modified: 2012-05-06
This is probably an easy question for the Microsoft supergurus here, but it's uncharted territory for me...

Here's the scenario- we have an antiquated NT domain that we're finally migrating away from, and are moving to a MS 2003 Active Directory domain.  So far the migration of the services has been straightforward, but now, I'm migrating over the DCHP service.  It isn't any problem to migrate the scopes, leases, etc via DHCPEXIM/NETSH, *but* the DHCP on the AD is showing that little red arrow stating that it's not going to hand out any IP addresses until it's authenticated. It's clear I'll need to authenticate it to the AD domain to make it live.

For the time being, becuase we're still in servitute to our major bread and butter applications, we are still having users sign onto the network using their old NT usernames, and they request the services on the AD (email, print queues, etc) via cross-domain trust as well as setting their AD usernames to give full access to their NT usernames.  Up until now, these have been services that are given out after the user has already signed on and have already been authenticated.  

Question- If I authenticate the DHCP to the AD domain, will it refuse to hand out leases to users signing onto the old NT domain becuase it will only allow DHCP requests from users signing onto the AD domain?  Or, will the DHCP give leases to the NT domain usernames becuase of the cross-domain trust?  OR, is there an additional step I need to do after I authenticate the DHCP to get it to give leases to users signing onto the NT domain?

It just occurred to me that I should probably ask before flipping the switch, so that the users won't beat me up for inadvertedly locking them out...thanks for your help!
0
Comment
Question by:goodoldave
2 Comments
 
LVL 83

Accepted Solution

by:
oBdA earned 400 total points
ID: 24139538
You don't authenticate the DHCP service, you *authorize* it in AD to start. All the authorization does is allowing the DHCP service in the AD domain to start handing out DHCP addresses.
Once the service is authorized, it will hand out IP addresses to anyone.
0
 

Author Comment

by:goodoldave
ID: 24139562
THANK YOU!  Exactly the answer that I was looking (and hoping) for!

For your super speedy response, I'm upping the point value for this question.  Thanks again!
0

Featured Post

Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

Join & Write a Comment

Suggested Solutions

I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now