In news:422574BD-AA85-4C11-A130-(E-Mail Removed),
AJ <(E-Mail Removed)> stated, which I commented on below:
> I have a W2K3 server with 2 NICS which are teamed, that is trying to
> contact a DC before the NICs are initialised.... the server
> eventually authenticates and gets its policies, but is there anything
> i can do to prevent server trying to contact DC before the NICS are
> initialised?
You mean before the team intialization, and not the actual NIC drivers
"initializing"? You can set the teaming service (whatever manuf it is) as a
dependency for netlogon.
Otherwise, (and just a reiteration of the basics of AD and DNS that all AD
machines MUST ONLY use the internal DNS server(s) in their IP properties),
it may be a simpler issue because anytime there are more than two NICs
(assuming not teamed), the one at the top of the binding order will be the
default used. Now if any of the NICs have an outside DNS configured (eg not
an internal DNS that hosts thge AD zone name), it may be trying to contact
an outside DNS asking it where the internal DC is and of course, it doesn';t
have that answer. The rule of thumb is only internal DNS and configure a
forwarder if you desire, otherwise, the Roots will be used for outside
resolution.
I had to state this because it is a very common configuration error that
will cause long logon times, among numerous other problems when it comes to
AD authentication, domain functionality and other problems with it's
members.
--
Ace Fekay, MCSA & MCSE 2003, MCT, Microsoft MVP
Microsoft Certified Trainer
Microsoft MVP in Directory Services (Active Directory)
Infinite Diversities in Infinite Combinations.
Assimilation Imminent. Resistance is Futile.
610-247-0700
"Very funny Scotty. Now, beam down my clothes."
The information in this email (including any attachments and any files
transmitted with it) is confidential and may be legally privileged and
otherwise protected from disclosure. It is intended solely for the
addressee. Access to this email by anyone else is unauthorized. If the
reader of this message is not the intended recipient, you are hereby
notified that any use for any purpose (including dissemination,
distribution or copying) of this communication is strictly prohibited.
If you have received this communication in error, please notify us
immediately by replying by phone or email to this message, and then
delete the original message from your computer without making copies.
Thank you.
|